* Configuration File

** Every ProMAX system includes a configuration file located in ** $PROMAX_HOME/etc/config_file. The configuration file includes site-specific ** information that is accessed by the system at runtime. Individual users ** can override this file by setting the environmental variable ** PROMAX_ETC_CONFIG_FILE_HOME to point to a 'config_file' of their ** choosing. All entries that are "commented out" are preceded by an "*". ** To make an entry "active", simply remove the "*" that appears at the ** beginning of the line.

** NOTE: When modifying entries in the config_file be aware that the ** description,parameter or pathname following the colon (:) may not exceed ** 128 characters. The entries most likely to be affected are the paths to ** primary and secondary storage.

** The entries that may appear in the configuration file are as follows:

printer device: lp0 *printer device: /dev/tty4

** The above entry specifies the path to the printer device. It is used ** by the plotting software if the user elects to direct a plot to the ** printer.

** NOTE: the CGM+ plotting software does not access the configuration file ** for printer device information.

*ui_port_stack: no

** The above entry is used to prevent orphaned notifications from ** being displayed on the most recently started UI. If a flow is ** submitted and then the UI is exited, the notifications are ** considered orphaned. If the user then starts one or more User ** Interfaces on the same machine, the orphaned notifications will ** be displayed in the UI that was most recently started. The above ** entry will prevent the orphaned notifications from attempting to ** connect to a new UI.

*plotter device: "12-inch" /dev/vp0 bytes_per_scan=296 *plotter device: "24-inch" /dev/vp0 bytes_per_scan=592 *plotter device: "24-inch" /dev/lp0 bytes_per_scan=1184 *plotter device: "36-inch" /dev/lp0 bytes_per_scan=880 *plotter device: "OYO-400" network bytes_per_scan=1184

** The above entries specify the path to a plotter device. There can be ** more than one entry of this type. It is, however, important to note ** that the FIRST live plotter device specified in the configuration file is ** the one that is used by Screendump. The OYO-400 example is given

** for the "Plot CGM+ Plotfile option - only the plotter name (OYO-400) ** is used.

primary disk storage partition: /mnt/hgfs/data_E 200

** The above entry specifies the path to the primary data storage area: ** areas, lines, flows, datasets, parameter files, and the database. ** This entry will be overridden by the path to the data directory as ** specified by the environment variables PROMAX_HOME or PROMAX_DATA_HOME. ** If this entry is overridden, a warning will be issued at the ** start-up of the ProMAX session. The data path is followed by the number of ** megabytes that will be written to primary storage before ** attempting to spill onto a secondary disk storage partition. If ** no secondary storage partition is specified, pairs of ...HDRx and ** ...TRCx files will be created with combined file sizes equal to ** this number of megabytes until the entire seismic dataset is ** written out. If no value is entered, a default of 20 megabytes ** is used. (See "Secondary Storage" section of the chapter ** entitled "Seismic Datasets" within the User's Manual.

primary overflow: 50

** The above entry specifies the number of megabytes to reserve in ** primary storage before switching to secondary storage. It is

** used to prevent primary storage from filling up, which would ** immediate halt any further processing.

secondary disk storage partition: /mnt/hgfs/data_E1 200 OPF secondary disk storage partition: /mnt/hgfs/data_E1 2000 TRC secondary disk storage partition: /mnt/hgfs/data_E1 2000 TRC

** The above entries specify the path to secondary storage areas for ** both Trace data and OPF data. ** Support recommends separating secondary storage only for OPF files ** and secondary for TRC files. ** The first stanza is the path to the ** secondary storage filesystem. The combined size (in megabytes) of ** the ...HDRx and .. TRCx files written to a particular partition ** before "spilling" on to the next partition are determined by the ** number following the data path. If no value is specified, a default ** of 20 megabytes is used. The next two stanzas specify whether Trace ** Data (TRC) or Ordered Parameter Files (OPF) or both (TRC OPF) will ** be written to secondary storage. The number specifing the files ** sizes is only used for Trace data. The first 10 megabytes of each ** OPF parameter is always written to primary storage and then spills ** (in 10 megabyte files) to any secondary storage partitions ** designated OPF. For more information concerning the use of ** secondary storage, consult the section entitled "Seismic Datasets"

** within the User's Manual.

secondary overflow: 50

** The above entry specifies the number of megabytes to reserve in ** each secondary storage partition before switching to the next ** secondary storage partition. Due to disk caching, it is possible ** for an inquiry of available disk space to be incorrect. The ** specified number of megabytes is subtracted from the reported ** available disk space on the secondary storage partition. This ** will prevent secondary storage from totally filling up.

*secondary scratch partition: /mnt/hgfs/scratch3 *secondary scratch partition: /mnt/hgfs/folder_e/Data_Seismik/2009/BNE_MADURA/scratch3

** The secondary scratch partition entry is used ONLY when creating ** very large OPF's, in the Geometry Spreadsheet or Extract Database ** Files modules. The default ProMAX scratch partition is used prior ** to accessing any secondary scratch partition entries for these ** purposes. There can be more than one entry of this type. NOTE: This ** parameter has no effect or use in the 3D migration algorithms, ** which use environmental variables.

xygraph_zero_reference: keep

** Causes XYgraph to cache intermediate data retrievals from the ProMAX ** database, This can speed up re-display of ProMAX attributes but ** consumes memory.

showfileprint: lpr -Phplaser %s *showfileprint: enscript -dhplaser -2r -G %s

** Several menus within ProMAX permit printing an ASCII text file ** directly to a printer. When you click on the "Print" button within ** these menus, this is the command that will be executed. The "%s" ** will be replaced by the filename.

screendump: xwd -id %d | xpr -device ps | lpr -Pps1 *screendump: xwd -id %d | xpr -compact -device ps -output $HOME/screendump.ps

** The above entry is used when screendumping to a printer or to a file. ** The user can put any command string that will work for their printer. ** The above first example uses the X command "xwd" (X window dump) and ** then converts to a postscript file with "xpr" and then sends the ** postscript file to a printer queue using lpr. The second example does ** not actually print the screen, but captures the screen as a postscript ** file.

cgm_screendump: resolution=300 plot_method=sdi VertSize=12.0

** When present, the above entry creates CGM+ format output for ** screendump images to a plotter. ** resolution - Set this to the resolution of the plotter. ** plot_method - Valid methods are: ** ** sdi ** sdi_pm ** zgs_rel98 ** other ** ** VertSize - This is the vertical dimension size for screendumps using ** ** ** The script $PROMAX_HOME/sys/exe/cgm_screeendump may need to be modified ** to your system plot configurations before using Screen Dump. ** NOTE: if this entry is commented out, Screen Dump will produce a V80 raster ** file the SDI plot method. : : : : SDI ProPlot software SDI PrintMaster software Zeh Graphics using Zeh98 method User-specified

cgmplot: resolution=300 banner=nil

** The above entry is used with the "Create CGM+ Plotfile" module. ** Resolution sets the dpi or VDC coordinates used in the

** cgm+ file creation (typically 300). ** 'banner=nil' suppresses the plotting of the banner page. 'banner=t' ** causes the banner page to be plotted. For more information on this ** entry, consult the Peripheral Setup section of the ProMAX User's Manual.

*nqs_argument_type: nqe

** The above entry defines the type or version of the Network ** Queueing System being used. You have two options: ** nqs ** ** ** nqe ** ** - This is the default. All queue commands will assume the version of NQS shipped with ProMAX is being used. - All queue commands will assume that CRAY's NQE software is being used to support batch queueing.

*flow lisp: (if Account_data (setq tape_owner (car Account_data) tape_scratch (second Account_data )))

** "flow lisp" is either a lisp routine or a file containing a lisp routine ** that is run prior to editing any flow. Thus it may be used to establish ** lisp parameters to be used for communicatoin between process menus. ** Remember: config_file records are limited to 128 bytes !

packet ladeing: [a-z]*Env

** "packet ladeing" is a list of regular expressions used to match files ** manufactured in the flow directory, presumably by the menu's rules, ** that need to be stored in the packet. They will be restored by the ** running exec in the directory referenced by the environment variable ** PROMAX_RUNTIME_DIRECTORY with a suffix corresponding to PROMAX_SEQUENCE, ** i.e., if the menu writes procEnv it will be resurrected at run time ** as procEnv.${PROMAX_SEQUENCE}

*remote_exec_type: aar

** If you use the ProMAX remote execution server, ProMAX will attempt ** to use the aar_promax task as an execution server analogous to rsh. ** The ProMAX remote execution server allows you to run remote tape ** or queup without the need to enable the more general rsh services, ** which ProMAX will attempt to use by default. ** To enable the ProMAX remote execution server, add the stanza ** remote_exec_type: aar to the config_file; the default is rsh.

*accounting: t *accounting host: cluster_master_node

** To enable ProMAX accounting, add the stanza accounting: t

** to the config_file that is visible to the main body of ProMAX. ** The default stanza is accounting: nil. ** 'accounting' must be set to true for flow replication procedures. ** For cluster operations, configure aar_promax only on the master node ** and specify that hostname here to centralize the accounting.

*aar_log: /apps/ProMAX/etc/Account

** The aar_log entry defines a file that contains a log of events ** generated by the aar accounting.

*aar register event log: /apps/ProMAX/etc/RegisterEvent.log

*aar plugin library: libvmesc.so *aar escape java class: com/lgc/ProMAX/ProManager/JobTracker

*aar plugin library: libshesc.so *aar register event: /apps/ProMAX/port/bin/AAR_RegisterEvent

** The accounting deamon (aar_promax) may perform some auxillary action ** with each accounting record as well as entering it in the log. ** The ProManager flow replica status tracking requires that this be ** enabled to update the database of flows as they are executed. ** Two alternative approaches are provided.

** plugin library: libvmesc.so ** loads a Java VM and uses calls through the class named in ** escape java class: to do the update. ** plugin library: libshesc.so ** Calls out to a 'register event' script, once per record. ** These switches are read by aar_promax and the necessary environment ** must be made available via the (x)inetd controlled start up script.

*device file: device.tts

** "device file" is used as the configuration file to define the logical ** devices and their properties. If the resource manager is not in use it ** must also define explicit physical devices. ** This entry is a file name to be searched for in the ProMAX etc directory ** and the users home directory. The newer one is chosen. It should not be ** a pathname.

disk_full_exit: diskfull_exit ** If all data storage disks fill an error condition is detected that ** will kill the flow. However if specified the file or pathname ** entered in this stanza will be executed instead to pop up a window on ** the terminal from where the job was submitted notifying the user of the ** condition and allowing corrective action and continuation of the flow. ** The default is to execute the diskfull_exit script from port/bin. A

** full pathname may be specified as an alternate.

help search: pdf html help ** The various ProMAX user interface programs access documentation through ** the script PromaxHelp which accepts three arguments. The second and ** third are the documentation (file) name and a geometry hint. The first ** represents a list of documentation (file) types in which the named ** documentation is to be searched for in the ProMAX install tree. This ** type order is defined by this config file parameter. The default (as ** above) indicates that PromaxHelp will scan first for a .pdf file ** containing the named documentation, second for a .html file ** and finally for a 'help' file, the original ProMAX text documentation. ** Since PromaxHelp is a shell script it is straightforward to add additional ** types and then to indicate search preferences here.

* merge temporary directories: no ** The standard Unix TMPDIR environement variable overrides the default ** directory /tmp for temporary file creation. ProMAX coordinates ** TMPDIR, PROMAX_SCRATCH_HOME and PROMAX_RUNTIME_DIRECTORY according ** to the policy set by this configuration parameter. ** If it is not set, then the presence of TMPDIR will cause PROMAX_SCRATCH_HOME ** to be changed for each job to a subdirectory of TMPDIR with the same number ** as the PROMAX_RUNTIME_DIRECTORY. ** If set to "tmp" then PROMAX_SCRATCH_HOME is modified just the same

** as above, but TMPDIR is set to /tmp if it is not already defined. ** If set to "psh" then TMPDIR is changed for each job to a subdirectory of ** PROMAX_SCRATCH_HOME with the same number as the PROMAX_RUNTIME_DIRECTORY ** If set to "no" then TMPDIR and PROMAX_SCRATCH_HOME are not changed. ** If set to a value beginning with a $ sign, then that value is treated as ** an environment variable whose value is used to set both TMPDIR and ** PROMAX_SCRATCH_HOME. ** NB. Modifications to PROMAX_SCRATCH_HOME and TMPDIR may cause parallel ** jobs to fail because those new directories may not exist on the remote ** system.

*html job output: t * Controls the format of the job.output. When not present the output is * simple text. When supplied as T ot t the output is somewhat HTML, * suitable for a web browser. The third option is to supply a function * name that will be used to dump the input packet.job in html at the * start of the job.output. The pkt_dump tool can do this. * html job output: pkt_dump

*queue menu initialisation override: t * Controls the source of the defaults for menus used by queues defined in the * qconfig. If not set the menu will be defaulted from environment variables with * the same name as the menu parameters. If set this default look up is skipped. * Note that this test is done before looking in this config_file for entries

* named 'parameter name': 'lisp value' which will still be honoured if found.