LandMark Known Problems

Known Problems List1
ProMAX System Administration
Known Problems List
No link to a known problem found for this process.

NOTE: You are linked to this page because no known problem
for this process is listed in this document.
If you are accessing this document via Other Docs: Known
Problems, please page down to review the Known Problems
list for other processes.
This file is updated monthly and placed on our ftp server for
retrieval on an ongoing basis. For information on how to
download the most recent copy of the Known Problems list
please refer to Downloading and Uploading Files with FTP
in the Accessing the Internet as a Resource chapter of the
System Administration guide.
Other Docs
Known Problems
ProMAX 2003.3.2 Known Problems Jan. 1, 20032

When you click the Known Problems icon in your online
documentation, it will take you to an entry in this listing if
there is a corresponding known problem. If there is not a
corresponding problem, you are taken to the start of this file.
The number following the description of a problem is used as
a reference ID. It is used when contacting the technical
support group for additional information regarding the status
of the problem. This file is organized as follows:
Recently Discovered Problems lists problems found
after this listing. This list includes problems for all
ProMAX products. Each recently discovered problem will
also be repeated in the appropriate category below.
ProMAX 2D/3D Problems contains an alphabetical
listing of all problems associated with ProMAX 2D and
3D.
ProMAX VSP Problems contains an alphabetical listing
of all problems specific to ProMAX VSP.
ProMAX MVA Problems contains an alphabetical listing
of all problems specific to ProMAX MVA.
ProMAX 3D PSDM Problems contains an alphabetical
listing of all problems specific to ProMAX 3DPSDM.
Software Development Problems
FrameViewer Problems contains a list of problems
specific to the Frame Viewer software used to display the
ProMAX helpfiles.
ProManager Problems contains a listing of problems
specific to the ProManager flow replication tools. This
includes MySQL problems.
Total Tape Solution Problems contains a list of
problems associated with
TTS,OPCON,ShowCat,device.tts and resource database
problems.
Other Docs
Known Problems
Recently Discovered Problems

ProMAX 2D/3D Problems
General ProMAX
Database attributes can be lost if you run concurrent
jobs that add new attributes to the same Ordered
Parameter File (OPF) in a database file. If this occurs,
you can get a partial recovery by restoring the OPF index
file from your backup media. (502707)
Database attributes can be lost if you access an OPF file
which spans filesystems, but the active config_file does
not contain the appropriate OPF flag for the required
filesystems. (501718)
Parameter tables defined with integer values for sort
keys larger than plus or minus 2**23 (8388608) may fail
with an error such as:
Unable to find SIN given FFID xxxxxxxx
Within the geometry spreadsheets and database, integer

attributes can be entered with a precision up to plus or
minus 2**31, and trace headers are loaded correctly
during Inline Geometry Header Load. However,
parameter table access on those keys using the larger
values will fail due to truncation problems.
work-around: Repick or recreate the parameter table
based upon key values that are not similarly affected.
For example, using SIN or SOURCE rather than FFID.
(502967)
Processes accepting ASCII input lists directly into the
menu can fail with memory errors upon execution. A
typical limit for ASCII strings is 50 kbytes. (502573)
Parameter Table Editor: When selecting a parameter
table which allows for multiple time gates, select all
gates in increasing order. However, if time gates are
selected out of order, you can export and then reimport
the columns in the correct order using the parameter
table editor. For example, after you have added a gate
during a subsequent interactive session. (504247)
Display tools memory use: Interactive Data Access,
Trace Display, Interactive Spectral Analysis, and FK
Other Docs
Known Problems
Analysis can suffer degraded performance if data is

viewed outside ensemble boundaries. These problems
include: increased usage of memory, CPU, and wall clock
time as additional traces are processed within a single
flow. The problem is most apparent when passing a large
number of traces through Trace Display, and not using
the default value of 0 for Number of traces to display
per screen. Exit the flow to clear the CPU usage. You are
encouraged to maintain input ensemble boundaries
where possible when using these display tools. (505892)
Display Tools: When using Exit/Stop in any of the interactive display tools, the numeric files in the flow directory are not automatically deleted. It is best to use
Exit/Continue flow. (506109)
Licensing: The user interface may crash if you try to
switch to the VSP product and do not have a valid VSP
license. (514918)
Problem: Tape mount dialog window pops-up but you
cannot see the text. The solution is to add entries like
these to each users .Xdefaults file.
ProMAX Tape*background: MistyRose
ProMAX Tape*foreground: sienna4
Displaying on a dual monitor Solaris system, while
running on an IBM may fail with the error:
X Error of failed request: BadWindow (invalid Window
parameter)
work-arounds:
Option 1: use Exceed to log into your AIX machine and
run display jobs.
Option 2: Change your dual monitor to a single monitor
display. On a dual-headed (2 monitor) Solaris system
one of the heads can be disable via editing
/etc/dt/config/Xservers file.
NOTE*** You DO NOT edit the /usr/dt/config/Xservers
file but instead copy it to /etc/dt/config and edit that
one.
A typical dual-headed system would have the following
Other Docs
Known Problems
line at the bottom of this file:

:0 Local local_uid@console root /usr/openwin/bin/Xsun:0 -nobanner dev /dev/fb0 -dev /dev/fb1
Where "fb0" would denote the first monitor and "fb1"

would denote the second monitor. The file would need to
be edited to allow ONLY a single (i.e., fb0) monitor.
Change above line to read:
:0 Local local_uid@console root /usr/openwin/bin/Xsun:0 -nobanner dev /dev/fb0
Log off and then back on system to restart Xserver.

Linux Only: In the case when the endian order is set in
the config_file as "big" and PROMAX_LITTLE_ENDIAN is
set to true in the start up script. Result: The job runs
and the data is output as big-endian (it doesnt consider
the value that is set in the start up script,) It doesnt do
what it says in the config_file about the user being able
to override the default for a particular job by setting
either PROMAX_BIG_ENDIAN or
PROMAX_LITTLE_ENDIAN in the environment. (516151)
Linux Only: When ProMAX gets the endian order from
the config_file it doesnt report in the job.output which
endian order is outputting. (516152)
Admin
Queues:lp SGI only: Killing an executing lp-queued job,
removes it from the lp queue but does not terminate its
processes. To kill a series of queued jobs, be sure to kill
waiting jobs before any active ones, or waiting jobs will
become active and then, in turn, not die when killed.
(512936)
Queues:NQS Cannot kill an active process from NQS.
(512923)
work-around: You can use
$PROMAX_HOME/sys/bin/qdel to delete local or remote
(qdel on that remote host) NQS queues:
* running jobs (qdel -<signo> <requestid>)
* waiting jobs (qdel <requestid>)
Queues SGI Only: Users have reported difficulties
setting up lp queues on some IRIX systems. We
recommend using NQS queues instead, however if that
Other Docs
Known Problems
is not possible there is a work-around. In addition to the

steps described in the System Admin. Manual do the
following. (513676)
1. (as root)
cp $PROMAX_HOME/sys/exe/lpd/queup /usr/lib
2. cd to /usr/lib
3. (as root) chown root queup
4. (as root) chmod 4755 queup
ShowCat: The documentation does not explain that in
order to run this program $PROMAX_HOME/port/bin
and $PROMAX_HOME/sys/bin must be in the users
search path. Otherwise users will get an error saying
promaxpath not found. (513506)
Tape Devices: ProClient script does not run on 32 bit
IRIX Systems. Attempting to access a tape device on one
of these systems will generate this error (513567):
ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM. Possible
start-up script error or client program
The work-around is to edit the ProClient script:

case uname in
AIX) UnameS="rs6000";;
# IRIX*) UnameS="sgimips4";; <- change this line to
IRIX64) UnameS="sgimips4";; <- these two lines
IRIX) UnameS="sgimips";;
SunOS) UnameS="solaris";;
esac
NQS Queues: In the script

$PROMAX_HOME/sys/lib/nqs/init_nqs,
PROMAX_HOME is set to /advance change to your
correct $PROMAX_HOME. (515371)
NQS Queues: To avoid potential problems users should
set the umask to 000 in their.cshrc files. (515646)
Other Docs
Known Problems
Solaris Only: Boot scripts that are K-Shell (/bin/ksh)

will not run during the boot process. inet.d will only run
scripts that are/bin/sh. The script startrmi is an
example of one that cannot be used as is. The workaround is to make the syntax within the script conform
to /bin/sh standards. (515494) EG:
PROMAX_HOME=/xx/yy
export PROMAX_HOME
Linux Only: The 2003.3 documentation regarding
setting up Linux lp queues is not complete. Please
download the file queue_setup.pdf from the Landmark
ftp site. (516214)
product/ProMAX/v2003.0/port/help/rel_notes
LINUX Only: The TTS TAPE_REQUEST is not
communicating with opcon. ProMAX hangs with a tape
request to opcon. (127983)
Linux Only: The documentation for setting up Linux
stinit.def file. Please download the file quick.pdf from the
Landmark ftp site. (516215)
product/ProMAX/v2003.0/port/help/TTS
LP Queues: There is a limit of 22 LP queues in ProMAX.
(138847)
LINUX Only: A local device name with less than 8
characters causes additional characters to append to
name causing jobs to fail with error message: (148604)
FATAL TAPE SYSTEM RUNTIME ERROR:
A matching logical device name: [LOCAL8MMX] was not found in
the DEVICES file.
The device.tts shows:
local8mm DEVICE="matterhorn:/dev/st0"
2D/3D Land Geometry Spreadsheet*
See Also: Geometry Spreadsheet General
3D: Do not input a Receiver increment value greater
than plus or minus one into the Pattern spreadsheet. If
required, receivers can be renumbered to avoid
subsequent pattern exit or binning problems. (504078)
Other Docs
Known Problems
2D: Static column: you cannot interpolate statics in

either the SIN or SRF spreadsheet due to existing 0.0s.
These 0s cannot be deleted to make the columns blank.
If you are importing data in which statics are available
for some, but not all stations, they are written in the
static column, but the entries between the actual statics
will still be 0. This makes it impossible to interpolate
between these values.
work-arounds:
1. Import Geometry file into spreadsheet, importing statics
into the elevation column.
2. Interpolate using step 1.
3. Export geometry file into an ASCII file.
4. Import geometry file into spreadsheet, importing statics
into the static column. (507313)
Skid and Offset information may be lost if the geometry
is being built by assigning midpoints based on existing
index numbers in the TRC and the spreadsheet is sorted.
This occurs because of the re-mapping in the TRC
domain. This problem can be avoided by sorting before
entering skid and offset information. (507707)
The SPS Import option ignores any uphole information
in the SPS file. Upholes must be entered manually.
(507758)
Importing into the spreadsheet only matches by Station
not by Line and Station. This could cause uphole times
and hole depth to be assigned incorrectly. (512105)
The option to delimit while importing a UKOOA file does
not work. (303275)
Offset header is not being loaded correctly. Azimuth in
the Trace QC is correct; source and receiver locations
are correct, but the offset sign is wrong on the near
trace. (129292)
In the binning menu ProMAX allows you to enter more
than two values to the right of the decimal point. If you
bin at this point these are the values that will be used.
However if you save and re-enter this menu the values
are rounded off to two digits. To get the greater accuracy
you must re-type in the true number. (276579)
Other Docs
Known Problems
The 2D Land Geometry Spreadsheet option to bin using

existing CDP numbering and coordinate values is
redoing the values:
TRC GEOMETRY CDP_X
TRC GEOMETRY CDP_Y
CDP GEOMETRY CDP_X
CDP GEOMETRY CDP_Y
The work-around is to use Database/Header Transfer to
put the CDP_X and CDP_Y trace header values into the
TRC and CDP database manually, then use just the
Finalize Database option of the 2D Land Geometry
Spreadsheet, do not bin. (134913)
Currently the import of SPS is only partially compliant
with the documented standards. In the relational file,
column 47 is identified as the "channel increment",
which we import directly to the pattern spreadsheet as
the channel increment. However, the standards allow
this value to optionally represent the number of
sequentially numbered channels at a given receiver
station. There is no means of distinguishing which of
these two modes to honor. The work-around via an awk
script to modify the relational file to explicitly include all
channel groups. (516639)
AIX ONLY: The Cross Domain icon does not work in
XYGraph. (144466)
Test
2D/3D Marine Geometry Spreadsheet*
3D: UKOOA import does not honor cable entry and will
renumber channels if necessary. Our example problem
is a 3D marine geometry with 6 streamers, identified by
the last column in a UKOOA file, and the channel
numbers decrease from 240-1 on each streamer. The
Import definition defines a column for the cable but does
not populate column. The Import apply/append menu
offers an option to renumber channels, but it starts from
x and numbers to x+1. Decreasing channels or cables
out of order will not tie to correct data channels.
work-around 1: You can edit the TRC with DBTools to
Other Docs
Known Problems
calculate unique channels for each shot. However, you

must make a series of edits. This works, but is hugely
time-consuming for a 100MM trace database.
work-around 2: We can provide an awk script that
manipulates the UKOOA file before import. Call support
for script. (507355)
3D: Multiple streamer patterns with different number of
channels are not currently allowed in the spreadsheet. If
required, the channels must be renumbered to a
common channel numbering scheme. (502371)
2D: If a marine geometry is defined with receivers ahead
of the source, such as in a dual boat configuration, the
sign of the offset is not calculated correctly. The sign of
the offsets is created as if the cable is trailing the source.
All other entries, such as Absolute offset, X/Y and
Azimuth are correct. If a signed offset is required for any
purpose, use Trace Header Math to set the signed offset
appropriately. (503508)
2D: The Setup dialog box indicates station interval
parameters are optional. For the Auto 2D options, these
parameters must be entered. Failure to do so can result
in incorrect geometry patterns. (505103)
2D: In Auto 2D, if the channel increment is -2, the far
channel is eliminated.
work-around: Define one more channel than is needed.
(507049)
2D: You must specify the Sail Line Azimuth entry
under Setup in 2D Marine Geometry even though the
menu says, Optional. If you do not make this entry, the
default Azimuth of 1 is used, This can cause CDP fold
errors due to round off errors. The fold can be doubled
when the azimuth is not specified. (507330)
2D: The 2D Marine Spreadsheet does not honor multiple
patterns for cables and will cause the job to fail.
(507311)
When importing navigation data, there is an option in
the UKOOA receiver column definition window that
allows an attribute to have math applied. Multiplying by
0.0 has no effect. (507641)
Other Docs
Known Problems
When importing a UKOOA file with negative northings,

trace coordinates are imported correctly, but shots are
read as positive coordinates. work-around is to multiply
the column in Source spreadsheet by -1. (504235)
The SIN spreadsheet column values for QC Dist and QC
Offset may be switched depending on the specified
streamer azimuths. Values such as 0, 90, 180, 270, and
360 are OK, but all other values switch these two
columns. (507760)
The SOURCE ID column in a standard UKOOA 90 file is
not being transferred to the SOURCE column in the
sources spreadsheet. The work-around is to use an
editor or the grep command to create a separate file
containing the S Lines from the UKOOA file. Then
import these via the ASCII Import option. (508657)
If you start a 2D Land Geometry Spreadsheet in a 2D
Marine Line, you will get cdp_x and cdp_y in your TRC
database even though they do not belong there. (They
are not there if you start a new line with 2D Marine). If
you copy a 2D land line to a new line and use it for a 2D
marine line, the cdp_x and cdp_y values in the TRC OPF
will remain in the TRC unchanged from the previous line
after the 2D Marine geometry finishes. These values
should have no affect on subsequent processing.
(512220)
When performing UKOOA Import and trying to change
"Record ID" characters user is crashed out of import
windows with following error: (513404)
Error: Attempt to unmanage a child when parent is not Composite
Deleting a shot from the sources spreadsheet will cause

CDP binning to fail. The work around is to leave bad
shots in the spreadsheet and set the FFID to zero. Then
run Geom Header Load by FFID and the zero ffids will
be dropped. (303998)
In the binning menu ProMAX allows you to enter more
than two values to the right of the decimal point. If you
bin at this point these are the values that will be used.
However if you save and re-enter this menu the values
are rounded off to two digits. To get the greater accuracy
you must re-type in the true number. (276579)
Other Docs
Known Problems
The documentation states that if you are entering

binning parameters by hand, you must enter an
appropriate X and Y grid origin and an appropriate
azimuth relative to the Y axis in order to establish the
CDP, inline and crossline numbering scheme. What is
not stated is that this is the CENTER of the first bin.
(516174)
Problems have been reported in the Volume Viewer
Editor when geometries are created with initial
coordinates of X=0, Y=0. The work-around is to bias
these values by some non-zero value. (134308).
3-Component Receiver Orientation
In this process, the maximum value in a gate is a peak. If
the maximum value is a trough, and you have picked on
a peak, the output will be 180 degrees off. (503259)
In testing the results from the Hodogram Analysis I
compared them to 3C Rcvr Orientation. The 2
component works correctly, but the 3C does not rotate
correctly. (513380)
3-Component Transforms
SGI Only: The Eigen value ratio option accumulates
CPU time, but does not produce any outputs. (503919)
If you select a user defined trace header for placement of
this attribute, the trace header must contain real
numbers. If an integer header is used, a single attribute
is written to only the last trace of an ensemble. (504222)
3D Mix
If you had not built a 3D PostStack database, running
3D Mix gives the following error:
Parameter MAX_DTRZ is not of type integer! It is of type character string
work-around: Fill out Number of inlines and Number of

crosslines in the LIN database. Use DBTools, click View
-> LIN, and Database to unlock the protected fields.
(507335)
3D Poststack Geometry
Certain combinations of the implied azimuth (typically
due N-S or E-W) and crossline bin dimension (typically
Other Docs
Known Problems
a negative bin dimension) can generate X and Y values

for inline and crossline inverse to the documented
description. Quality check the database attributes after
running 3D PostStack Geometry, and the sign of the
Bin size in crossline direction parameter altered if
necessary. (502241)
3D Post Stack Regrid
In surveys where the first inline and crossline does not
equal 1 this module may zero traces on the low
numbered inlines. (513857)
There is a numerical noise problem when the input grid
is oriented at exactly 45 with respect to the output grid.
The work around is to adjust one of the coordinates so
that the relative angle is not exactly 45 degrees. The fix
involves only making the processing direction decision
once. At 45 degrees, it doesnt really matter whether the
processing direction is inline or crossline (as long as the
same direction is used throughout. (130491)
In the usage section of this help file, it is not stated that
a Post-Stack database must exist for the dataset the
user wishes to alter in 3D Post Stack Regrid. This can be
accomplished by running 3D Post-Stack Geometry.
(13489)
3D Ref Statics Model*
If SOURCES are in descending order in the geometry
database, the corresponding receiver XYs appear flipped
when describing the mode. This is a visualization
problem; it does not affect the actual model definition.
To obtain the correct shot-receiver appearance, sort
SOURCES into ascending order and refinalize the
database prior to running this process. (503455)
3D Refraction Statics Inversion*
Linux Only: The interactive mode of this program will
not converge. It will run until it reaches the maximum
number of iterations. The non-interactive mode does
converge. (149431)
3D Supergather Formation
When the minimum center crossline number is greater
than the maximum center INLINE number the program
Other Docs
Known Problems
will halt. (293557)

Work-Arounds
(1) Use a supergather grid large enough to not violate
this condition, then window later.
(2) Select the supergather by individual center-cdp
numbers instead of the grid rectangle
3D Supergather Select
If the trace header word SG_CDP already exists but has
the wrong format type, the value of SG_CDP is incorrect.
The work-around would be to put a Header Delete in the
flow before this module. (513616)
3D Velocity Viewer/Editor
If you say YES to specifying the bounds of the velocity
field and select a sub-set of the data, then toggle the
parameter to NO. You will still only get the sub-set
previously specified. The work-around is to re-set the
range back to the entire field. (301336)
Using the smoothing option in this tool to create a
velocity function at every CDP does not work. Although
viewing this velocity field looks correct the resulting table
may have missing or duplicate functions. The workaround is to use the Volume Viewer/Editor. Use INLINE
and XLINE as coordinates and re-grid to every
INLINE/XLINE then save the volume. (508289)
Additive Noise and Spikes
The ensemble/trace selection controls for where to place
impulsive noise references internal counters of ensemble
and trace within ensemble rather than any sort keys and
trace header words. Thus 3:4/ refers to the fourth trace
encountered within the third ensemble in the input
stream. (514184)
This may generate noise at the water bottom if NMO is
not applied before the noise burst edit. (142347)
Alternate Machine
This module fails with a Segmentation Violation. It is
recommended to use the new ProManager tools to
submit jobs to alternate machines. (513640)
Other Docs
Known Problems
Amoco SIS Input

This module may hang on the last trace of the input file,
never completing properly. (513538)
Apply Residual Statics
If an attribute is copied using database tools, it will not
display in the popup listing after the copy. Exit and
renter the menu to display the attribute. (502326)
Archive to Tape
The current ctar code still exhibits a 127 file name
character limit. (507370)
Cannot archive a file of more than 2 Gbytes to tape or
disk. (515505)
Solaris Only: If you run the archive to tape flow and
specify disk image with removal, the ctar session dumps
core. This is only a problem if you request that the files
be removed. (304597)
Automatic Gain Control
When the difference between the smallest and largest
absolute amplitudes in an AGC gate are extremely large
an overflow can occur in the scalar calculation causing
the entire trace to be zeroed. (512744) (305313 IRIX
Only).
This module fails using the Apply and Save option if
the trace length is less than 500 msec. The error is:
agc operator longer than trace length
The work-around is to use Trace Length to pad the trace.

(513071)
AVO Analysis Gathers
Running angle limited cdp gathers fails to 'angle limit'
the last trace of the ensemble. The current work-around
is to ignore this trace in further processing. (512116)
This module will output zero amplitude angle of
incidence gathers if the first trace of the input CDP
ensemble is a dead trace. I.e trace_type = 2. The work-
Other Docs
Known Problems
around is to eliminate these traces or change the trace

type header to = 1. (513486)
If you run separate jobs with min-max angles set to
values like 0-20,20-40,40-60 and re-mute is set to NO.,
there is more overlap between the gathers than expected.
This is currently under investigation. (125584)
AVO Attribute Stacks
Setting the correlation coefficient sets the appropriate
gradient values to zero but not the intercept. (303037)
The fluid factor stack (Attribute 9) is not being calculated
correctly. (513755)
The Gradient and Correlation calculations are incorrect.
Contact support@lgc.com for a possible fix. (150333)
AVO Interactive Crossplot
On data with non-integer sample intervals, if you pick
seismic polygons and cross-plot them, then stop and restart the flow, the polygons may be shifted deeper in
time. (507771)
This module will not run properly in conjunction with
IDA and DBTools. It is recommended to use Disk Data
Input and Insert to pass pairs of traces to this module.
(509457)
Option to save Horizon picks does not function properly.
No known work-around at this time. Also Snapping a
horizon may cause the job to abort. The work-around is
to pick and snap horizons in Trace Display then view
them in this module.(509845) (509757) (509964)
In AVO Interactive Crossplot, when you slide the bars
on Crossplot Scaling, the labeling on the axes does not
change to match the data. (303036)
Snap option flips display. This may occur when using
the horizon pick icon and then using MB3 to snap your
pick. (512272)
Adding points to the polygon may corrupt the polygon
table. (512984)
Cannot change horizon color if 2 or more horizons are
up. (512315)
Other Docs
Known Problems
Setting Label Plots with AVO_ATTR to yes does not give

any label at all. (512963)
Selecting a polygon that encompasses ALL plotted
datapoints should highlight ALL of the seismic traces, it
does not. The 1st and last trace are not highlighted.
(304141)
Using Horizon Attributes/Window Horizon can cause
time axis and seismic display to flip so time 0 is at the
bottom and time xxx is at the top of the display. This
seems to happen when your windowed gate extends to
the bottom of the display. The windowed horizon polygon
is flipped as well. Any other manually entered polygons
stay in their original location. When you turn off
Horizon Attributes/ Window Horizon, all goes back to
the correct position. (512139)
This fails to read the crossplot tables generated by IRIX
or AIX, but works in Solaris (1998.6 and 2003.0).
(131226)
AVO Volume Reconnaissance
Although the help file does not state this, the input
volume should be padded. Otherwise you will get this
error:(508409)
Build Unisec Parmfile

The following error message is generated if Panel=On,
the plot mode is color, and the total length of your plot is
expected to exceed the plotter paper length.
Error, unexpected EOF reading color trace
work-around: Make your plot fit the paper. (505023)

There is a problem using the grey option in a color
overlay. The positive side of the wiggle trace disappears
once a trace is clipped. The work-around is to replace the
values in the
$PROMAX_HOME/sys/exe/larson/lstbin/coltab.txt for
"GREY" with the values in
$PROMAX_HOME/port/misc/unii_whtblk.rgb. (513419)
Setting PARMS,SIDEL=ONLY disables EVALS,LDIR=90.
work-around is to pass small amount of data (10 traces)
Other Docs
Known Problems
and set PARMS,SIDEL=R (for right side), L (for left side)

or LR (for both). YOU MUST PASS DATA for EVALS,LDIR
to be honored. (513621)
This module will not read in horizon pairs with CDP
values greater than 32,000. (143043)
CDP Binning
It has been reported that if this module attempts to write
to an OPF partition that is 100% full, the database may
become corrupted. (138796)
CDP/Ensemble Stack
Applying Final datum statics after stack updates
TLIVE_S and TFULL_S incorrectly. TLIVE_S and
TFULL_S are altered by close to 2* fnl_stat instead of
1*fnl_stat. work-around: Use Trace Header Math to add
FNL_STAT to TLIVE_S and TFULL_S after stack.Reapply
Mutes in further programs will be fine. (513345)
CDP Trim Statics
On Marine data you will still need to bin receivers to get
this to run. An SRF OPF is required. (515166)
Color Edit
A 3D license is required if you start this process from a
flow. If no 3D license is available, start the Color Editor
from an interactive display tool. (505907)
Common Offset F-K DMO
On some datasets the remove padded traces portion of
this macro does not work. Checking the job.output file
and comparing the number of traces output from the
DMOFK_PANEL and RMPAD_TRACES steps will show if
this is occurring. The work-around is to use a module
like Disk Data Input to eliminate the traces flagged as
padded (e.g. PAD_TRC=1). (508875)
Convert 2D Table to 3D
If you try to append a 2D table to an existing 3D table
you will get the following error:
cannot find outvel2 in packet file
Other Docs
Known Problems
The work around is to edit the menu velTo3D.menu,

The line outvel2 should have type_desc instead of
select_item. (514114)
The database method for mapping 2D to 3D fails. The
other two methods work properly. (136809)
Create CGM+ Montage SDI
Users have reported that attempting to use this module
with Version 2000 SDI_MONTAGE fails with the
message:
libXm.a [shr_32.o] NOT FOUND
One work-around is to create a script called sdi_montage

that un-sets the variable LIBPATH before executing the
sdi_montage executable. (512895) NOTE: Fixed in
2003.0
Create CGM+ Plotfile
A signal 10 sigbus error occurs if you try to overplot a
header value created in the same flow. You should
output a file with the new header, and bring the new file
into Create CGM+ Plotfile with Disk Data Input.
(500653)
The process dies with a memory fault when creating an
automatic sidelabel on an input file lacking a CIND file,
such as a SeisWorks Input or Synthetic Trace
Creation. You should output a ProMAX file prior to
creating the CGM+ file. (500449)
If plots are not at 400 or 200 dpi, label text fonts cannot
scale exactly. You should scale your plots to 400 or 200
dpi, to get an exact scaling. (501007)
3D timeslice only: When plotting timeslice traces, CDP
values are null. To plot timeslice traces in CGM+ format,
use Trace Header Math to set CDP = xline_no or
inline_no, depending on timeslice orientation. (501790)
Turn off the label for overplot attributes does not
work correctly. When overplotting attributes, turn off
labeling by selecting Yes to Include Label, and creating
a blank entry for the Label Text field. (501771)
Other Docs
Known Problems
This process currently handles up to 8000 monochrome

samples and 4000 color samples per trace. Using a
greater number of samples results in the errors:
scaling mode 8224 illegal
scaling mode 8192 illegal
Illegal Element Id in Class 2
INVALID point 40556 class code val: 2 0 0
work-around: Run the display using multiple time trapped

inputs to create larger plot files. (501908)
When using Input Trace Order to plot, either the
individual trace annotation, or the timing line
annotations can be improperly shifted, depending on the
use of a trace gap. Avoid the problem by using Ensemble
Redefine before Create CGM+Plotfile, or CDP can be
used rather than Input Trace Order. (502165)
If you have a large number of plot layers for
Traces/Plots, some parameters can be lost at the
bottom of the menu. Toggle off the topmost parameters
for Enter RMS Explicitly for full access to all
parameters. (502157)
If the Number of traces for Gain Calc. is specified
greater than the number of traces to be plotted, and an
Ensemble Gap is specified, the data overplots the timing
line annotation. Specify Number of traces for Gain
Calc. no larger than the total number of traces to plot.
(502608)
Reset the timing on a zipper cannot be reset from
within the interactive menu. A value of 10 is always
used. If required, the value can be reset by using a
private copy of the cgmplot_socket menu, and editing
the default value for zipper_msec. (502756)
Display a down line only can incorrectly generate text
in the seismic data. There is no work-around for this
problem. (502885)
Upon creating a plotfile, the plot control file is set with
color_cgm = True, even if the trace display is black and
white. This can cause some plotting software to make
three passes over the plot. If so, edit the control file
(xxxx_cntl) and set this value to False. (503521)
When plotting a large number of traces with a
corresponding attribute graph, the borders of the graph
Other Docs
Known Problems
can appear to disconnect, and then wrap around at the

end of the section facing the wrong direction. (503770)
The sidelabel can be truncated if you input a value for
Amount of whitespace greater than zero, and the
resulting label is larger than the seismic data used for
plotting.
work-around: Find the current length in the cgm_cntl
file; this is the 4th parameter after VDC_VIEWPORT. Add
the amount of whitespace required and set the minimum
side label size in the menu to the increased size.
(504097)
When plotting a dataset containing every Nth ensemble
or specifying INLINES:XLINES as sort keys, a large
cgm.bnxx file may be created in the flow directory if
wildcards are used in the Disk Data Input sort list. The
work-around is to explicitly specify the range of
ensembles in the input step. (301354)
If you choose the posting method of ORDER and the
selection list begins with 1, the second trace will actually
be annotated. In order to label the first trace the
selection list should begin with 0. (301843)
Solaris Only: Executing the exact same flow on AIX vs.
Solaris systems produces two different size velocity
boxes. The Solaris version has more space between the
time and velocity columns. No known work-around at
this time except to use The Unisec modules. (509697)
A Create CGM+ Plotfile flow that has a seismic dataset
and a color cell fill overlay may have the color plot over
the wiggle traces, depending on the number of traces for
gain calculation. The work-around is to specify in the
menu more traces than are being passed for gain
calculation. (512199)
Excess amounts of blank paper may occur as the result
of the VDC maximum X coordinate extent being set to
32767 in the generated CGM+ plotfile. The potential
length of plot may come out to be (32767)/(dot
resolution of plotter). Contact support to see if a patch is
available. (130422)
Other Docs
Known Problems
Crooked Line Geom Spreadsheet

SGI Only: Attempting to open a saved track will cause
the Geometry Spreadsheet interface to crash. (513944)
When you choose the Layout Bins Icon there are 3
options MB1,2,3. If you choose MB1 first then MB2 will
no longer work. If you wish to experiment with the
various options use MB2 first. (512663)
Database Display
NULL values for an X/Y database attribute cause
projections to other domains to fail. NULL values can be
filled using the Math/Fill operation in XDB Database
Display to correct for this problem. (503398)
AIX Only: Database display is not displaying the null
values as triangles on the top and bottom of the graph
on an IBM. On the IBM, there is no way of telling where
the null values occurred. The only way you know you
have nulls is <null>. will be posted by the attributes that
have nulls. (515341)
Using the option 3D - Display - XYGraph then choose
any three X,Y,Z attributes from the TRC order. Then
enable the Alternate Domain option, the display may
crash. (120125)
Database/Header Transfer
When creating multiple user defined headers, the
created header name can contain trailing string values
from one of the previous entries.
work-around: Place the shortest user defined string first
in the list of header transfers or call the process multiple
times. (503391)
The database will not accept the transfer of 8R floating
point headers which can be created in a SEG input step.
The fatal error is:
Database format = 2
Header format = 3
work-around: Obtain ASCII files for spreadsheet import in

order to place this data in the database. (504225)
Other Docs
Known Problems
Database/Horizon Transfer
Currently you may not transfer IHD type horizons
directly to the database using this module. There are two
work-arounds. The first is to use the ASCII export option
then import this file in XDB. The second is to copy the
nnnnnnnn.IHD binary file in the LINE directory to
nnnnnnnn.HOR using the UNIX cp command. (301638)
Datum Statics Apply
If you run the Datum Statics Calculation with a new ID
number (e.g 04) for Source/Receiver/CDP parameter
files, you get a notification of "Job completed". If you
immediately go in Datum Statics Apply and try to pick
the new Source/Receiver/CDP parameter files, the new
ID entries i.e (S_STAT04 etc.) will not be visible in first
attempt. However in second attempt the new entries are
there. (120120)
Datum Statics Calculation
When you run this module multiple times different
CSTATxx attributes may be created. However only ONE
version of C_STATIC ever exists that is the same as the
last execution of this module. When you use the module
Apply Datum Statics the user chooses which version to
apply. However some modules such as DMO to Gathers
3D ALWAYS use C_STATIC. Therefore it is best practice
to make the version you wish to apply the last. (301410)
This module fails if the database attribute C_STATIC
does not exist. The work around is to use DBTools to
create this attribute before running this module. Or run
a flow containing Apply Elevation Statics to put
C_STATIC into the CDP database, then run Datum
Statics Calculation. (128231)
DBTools
If NULL values exist at the end of a range of attributes,
only the non-null range is plotted, even if you select to
plot null values. The NULL value count is also lumped
into the first histogram plot. (504860)
Other Docs
Known Problems
Problems can be encountered when displaying a plot

which contains NULL values. An error returned to your
shell indicates:
Ensure failed ((int)((xMax-xBase)*xScale)<_nBin), file
/advance/port/src/lib/dbtX/Histogram.C
NULL values can be filled using the XDB tool to display

these attributes. (505282,515339)
This process fails when attempting to display stations
which have 8 digit values. The error will point to a failure
in /advance/port/src/lib/dbtX/MarkersO.C. There is no workaround for this problem. (506097)
SGI ONLY: Accessing large (in our case 24 million traces)
TRC Database attributes may cause DBTools to core
dump. For SGI, setting the variable
DBTOOLS_SERIALIZE_LOAD may help for surveys less
than 10 million traces. For the larger databases, you will
have to create smaller databases for viewing and can
merge later on.(507828)
If you are selecting traces in DBTools and sending them
to a process such as Trace Display via IDA. DBTools
may appear to hang then eventually return the error:
ensure failed line 109 of /71/advance/port/agc/ar.c
This is caused by the user selecting traces from DBTools

that are not on the sort list in Disk Data Input. (507869)
In the tabular view, when editing cells, sometimes this
tool will stop accepting edits. At this point in time no
cause has been determined and the only work around is
to use XDB and ASCII export, make the changes, then
re-import. (507973)
While editing in tabular view entering certain values
such as 5.1 will return 5.099999 instead. (507974)
When altering any entry the LIN order it is recommended
that you use the XDB tool rather than DBTools.
(508331,508722,301008)
The ability to interactively display traces to Trace
Display will not work if more than one attribute is
selected in View - Overlay. (515016)
Other Docs
Known Problems
Taking the log of an attribute that has a 0.0 in the array

will fail. There is no error message DBTools only outputs
results up to the trace with the 0.0 value. (515033)
Delimit ranges may report incorrect min/max values if
the bin grid definition is smaller than the actual dataset.
(130864,130808)
Viewing "Summary statistics" "focus on, exclude
selection" is not working. (130607)
User brings up DBTools-->File-->XDB Database Display
and goes to SIN database to display attribute. If he then
tries to switch to another line XDB Display crashes. The
workaround is to go back out to ProMAX UI and re-enter
DBTools under other line. (128736)
SGI Only: Attempting to copy an attribute will cause
DBTools to crash. Work-around: use XDB or dbmath to
copy the attribute. (518323)
Disk Data Input
See also Interactive Data Access.
On large datasets which are sorted requiring overlapping
groups of traces, such as sort string 1-9999(3)[4], the
sort can fail with the following errors:
Failed to locate position of trace within the dataset (Memory sort)
Program encountered a significant internal error and cannot continue.
The error results from a situation that was not anticipated by the
developer (Disk sort)
work-around: Break the input dataset into smaller

pieces. (502021)
The error:
Corrupted trace or trace header encountered
has been encountered after reading in field data which

has a non-standard TRC_TYPE value. If this error is
encountered, you should use a Trace Header Math step
to reset TRC_TYPE =1 during the field tape input flow.
(502653)
Certain combinations of sort keys such as CDP: CDP_Y
may generate memory errors. The work-around is to use
Inline Sort. (512181)
Other Docs
Known Problems
It has been reported that users have encountered

problems sorting datasets that have individual
TRC/HDR files greater than 2 GBytes. We recommend
that users set the size for primary and secondary storage
in the config_file to 2000 or less. (512529)
Certain sort combinations where the group size is larger
than the increment e.g. 1-200(4)[19] may generate a null
trace in the resulting output dataset. (145744)
Disk Data Insert
When Observe Dataset Boundaries is set to Yes, the
LSEG_END header is not set to 1 on the final trace of the
inserted datasets. You can manually override the header
by selecting the appropriate trace in an IF block, and
resetting the header using Trace Header Math.
(502692)
When inserting sorted datasets in Merge mode the
inserted datasets may not be merged into a single
ensemble. The datasets are sorted correctly, but can
split on the input boundaries. If required, the Inline
Sort or Ensemble Redefine process can be used to
create single ensembles on the fly. (503659)
Maximum traces per output ensemble is limited to a
value of 9999. To obtain larger ensembles, change the
actual MAXDTR values in the disk_insert menu, or use
Ensemble Redefine within the job stream itself.
(504159)
Occasionally this module will fail with an error
indicating that the sample rates of the two datasets do
not match, even though a MB2 history of each dataset
indicates they are the same. This is due to the executive
seeing the sample rate as 1.999 or 2.001 rather than
2.0. The work around is to use the sample rate override
option in the menu. (507858)
SGI ONLY: This module will fail with the message:
Typed I/O error - bad file handle
If there are more than 5 inserts in the flow, and the first
dataset has only one trace. (512619)
Other Docs
Known Problems
Disk Data Output

When using the overwrite option after modifying a
geometry, the expanded dataset information cannot be
updated for the CDP extents. Using the MB2 dataset
information listing will show incorrect extents. The
problem can be avoided by outputting to a new dataset
instead of using the overwrite option. (503387)
This process writes in round robin fashion to all
secondary partitions listed in the config_file until
encountering one or more full filesystems. Multiple
TRC/HDR pairs are then written to the next non-full
filesystem found in the config_file list. For example, if
Disk 1 and Disk 2 were full, followed by Disk 3 and Disk
4, Disk 3 would receive TRC/HDR files 1,2,3, 5,6,7,...
and Disk 4 would receive TRC/HDR files 4,8,... While
this does not create an actual output problem, it can
potentially cause disks at the top of the config_file list to
fill more quickly than disks at the bottom of the list.
(503763)
If traces are appended to an existing dataset, the
Maximum traces per ensemble is reset to the
maximum number of traces in the appended dataset. A
subsequent Disk Data Input step using the Get All
option will output ensembles based upon the final
appended value. An Ensemble Redefine or Inline Sort
can be included after the append step to ensure that the
number of traces per ensemble is set correctly. A
simple sort on Disk Data Input will also provide a workaround if this situation is encountered. (503949)
Users have reported that at times the CIND file for a
given dataset becomes unusually large. At this time the
cause has not been determined. The suggested workaround is to copy this dataset into a line with no
database, or write it out as SEG-Y. Then read it back in.
This will shrink the CIND file to a more normal size.
(513082)
If you are using MB2 to check the status of a dataset
while it is being written to disk it is possible that ProMAX
mistakes this as a duplicate trace being created and
stamps the dataset as not matching the database.
(513095)
Other Docs
Known Problems
DMO to Gathers 3D
Running this module changes your OFB_CNTR and
OFB_NO headers to a constant value. You can use Trace
Header Math before this process to save the offset
values into a user defined header. These may be used to
restore the original values after DMO. (505646)
This module is NOT passing the flow parameters to the
Processing History for subsequent use in Create CGM+
Plotfile labeling or dataset history. (508050)
Using the Offset Squared option for offset sampling
outputs nothing but dead traces (TRC_TYPE=2). The
work around is to only use the OFFSET option for offset
sampling. (514245)
Eigen Stack
If you attempt to use a time gate that was created by
defining the bottom layer first you will get this error.
Request for memory buffer has negative size
The workaround is to re-pick the gate defining the

shallow layer first.(513945)
Eigenvector Filter
SGI Only: This process may stall during execution if the
design gate contains zero amplitudes. (507074)
work-around: Use a design gate that encompasses only
live data.
SGI Only: Program stalls when amplitudes greater than
100 are used.
work-around: Use Trace Math to scale down amplitudes.
(508141)
Emacs Editor
Linux Only: Does not run from within the ProMAX User
interface. (516052,130873)
ESI Disk Data Input
This module will fail if you attempt sort using headers
that are not integers (148177)
Other Docs
Known Problems
Expand Flex Binning

Application of this process will reset the global data
domain of the relevant dataset to unrecognized. While
this will generally not affect any subsequent use of the
dataset within the processing system, the global flag can
be reset if needed using Trace Header Math (change
attributes/data domain). This is fixed in the 2003.3
release.(503954)
This module will allow data to be input in any sort order.
However it will try to hold enough space in memory for 9
ensembles. In datasets where the default primary key is
something like INLINE there may not be enough memory
to hold 9 ensembles and you will get an Ensure failed error
message. (513202)
Explicit FD 3D Depth Mig (SMP)
Using values other than the default for Maximum Depth
may generate results that are stretched below this
depth. (514077)
Occasionally when the re-start option is selected, the
job.log file may get corrupted generating the following
message:
Current tool is ST_FXYM3D
(number 7 in the flow) Message is:
Error reading from socket. The corresponding socket tool probably died.
Stopping Program. Errno: 0 (Error 0)
The work-around is to delete the corrupted line. (128572)

Explicit FD 3D Time Mig
Velocity inversions can cause low frequency artifacts.
(301212)
Increases amplitudes by factor of 100. This happens for
all platforms, but only if the menu option SharedMemory Parallel Version is selected. If the option
Network Parallel is selected in the menu, the problem
does not occur. The problem has been fixed using the
Explicit FD 3D Time Migration (SMP) module.
(513014)
Other Docs
Known Problems
Extract 2D Table from 3D

When you select Stacking Velocity for input this module
will also generate an inaccurate interval velocity in depth
table. (513138)
Extract Database Files
A full extraction does not complete the grid information
in the LIN database. Appropriate entries should be
edited. A more robust approach is to bin and finalize
that database using a Geometry Spreadsheet
application. (505914)
For marine geometries, the marine flag may not be set.
(505912)
This process checks for CDP values in the headers, even
when Extract CDP binning is toggled off. Use Trace
Header Math to create a temporary integer CDP value.
(505939)
An Invalid CDP X-coordinate error message appears
when attempting to project coordinates to CDPs after a
full extraction of the database. For example, projecting
SRF Geometry Station to CDP Geometry Station.
(507386)
work-around: Use Math->Fill for both the CDP Geometry
X_COORD and Y_COORD before projecting.
Finite Difference Modeling
When inputting a dataset and using the geometry from
the headers, if you have a roll-on shot situation, the
global shot fold is set by the first input shot. Because the
roll-on increases the fold at the next shot, your job can
abort with the following error message (507343):
The number of traces in this ensemble is more than specified in the
global variables
Users have reported getting SIGBUS errors with this

module while attempting to use the Ormsby wavelet. The
work-around is to switch to the Ricker wavelet. (512535)
There is a problem with the menu. If the user first
selects the Normal Point Source option and wants to
use a trace dataset for header information (Take
geometry from the headers of an input data set? - Yes)
and subsequently opts to use the "Exploding Reflector"
Other Docs
Known Problems
option the job fails with an error stating that the data is
not sorted in CDP order. The Exploding Reflector option
does not have the option to use trace header information
and disappears from the menu when using this selection
but is still expecting to pull the geometry information
from the headers. The solution is to make sure you turn
off the "Take geometry from the headers of an input data
set?" parameter before using the Exploding Reflector
option. (140358)
First Break Pick Macro
This module will fail if you attempt to use the NN Picker.
(512768)
First Break picks are not visible if you review or animate
saved images. (130529)
F-K Analysis
On a 3D dataset, if you pick a polygon and save it, then
re-execute the flow, the polygon will not display. It may
still be applied with no problems. (512332)
F-X Decon
SGI Only: This module is running slower in version
2003.x than it did in 1998.6. Work-Around: use version
1998.6 if possible. (149746)
Floppy Input
This process can fail on some operating systems, either
with a SIGSEGV segmentation violation error (Solaris) or with a
Floppy Open Error pointing to an invalid filename (AIX). In
some cases, limiting the input to fewer records
(approximately 300) and processing the input file in
pieces has resolved this problem. (503674)
No facility to input OYO 3 format from a mcseis170
recorder. Currently there is no work around for this
problem. (301359)
Fourier Trace Interpolation
The last output trace may be numbered incorrectly.
Work-around: Use Trace Header Math to re-number the
trace or pad an extra trace prior to interpolation then
delete it afterwards. (305444)
Other Docs
Known Problems
Gated SC Decon 4: Cleanup

This module is designed to delete the INI and SOL
scratch files. This module will run and complete
normally even if there are no files to delete. (515530)
Geometry Spreadsheet General
If shots or receivers are deleted in the spreadsheet and
the database is subsequently rebinned and refinalized,
any previously created database attributes generated
outside geometry definition, such as first break picks
and statics, will not match the new database description.
Those attributes should be recreated if they are required
in any subsequent processing. (502579)
If shots are deleted in a spreadsheet initiated from an
extraction or UKOOA import, the File/QC option from
the TRC database will hang. (502964)
Parameter tables defined with integer values for sort
keys larger than plus or minus 2**23 (8388608) can fail
with the following error:
Unable to find SIN given FFID xxxxxxxx
Within the geometry spreadsheets and database, integer

attributes can be entered with a precision up to plus or
minus 2**31, and trace headers are loaded correctly
during the Inline Geometry Header Load process.
However, parameter table accessing keys using the
larger values fail due to truncation problems. (502967)
work-around: Repick or recreate the parameter table
based upon key values that are not similarly affected, for
example, using SIN or SOURCE rather than FFID.
When interpolating, if zero values are in the spreadsheet
and Interpolate all values in marked block by record
number is selected, the zero values are replaced with
interpolated values. If NULL values are in the
spreadsheet and Interpolate all values in marked block
by station number is selected, the NULL values are not
interpolated. (504995)
The Undo option in the Edit menu item can fail to
operate correctly. (505307)
The Import -> Merge option does not work for the Line
column in the spreadsheet editor. (503740)
Other Docs
Known Problems
Depending upon the type and size of font chosen and the
amount of re-sizing of the spreadsheet window the last
line in the spreadsheet may be only partially visible.
Potential work-arounds are to delete
the.Spread_parms.xdr file in the users home directory.
Also make sure the 75DPI font is ahead of the 100DPI
font in the font search path. (507740)
Using a Binning Bias of -1 causes an error. This may
make it impossible to get the desired value for the first
CDP. The work-around is to use some other bias value
like 0, -2 etc. then use Trace Header Math to re-number
the CDP values. Afterwards, extract a new geometry.
(301897)
When a database is binned in pieces, and the option to
use the default for offset binning is taken, the last
execution of binning determines the range of OFB_NOs
for the line. It is possible that the resulting min-max
range is not accurate for the entire line. The workaround is to use the User Defined option for offset
binning and always use the maximum range for the line,
regardless of what it is for a particular portion. (510198)
When the values for SRF and SIN do not increase in the
same direction CDP_ELEV may get projected in reverse
order. This appears to occur when you choose the option
CDPs increase from last trace in the binning menu.
(514180)
AIX ONLY: The Cross Domain icon does not work in
XYGraph. (144466)
Hand Statics
Inputting a large number (approximately 1500) of
REC_SLOC/static pairs via an ASCII input file will cause
this process to fail with the error message:
Character parameter is too large to input. Severe memory problem.
Memory buffer overrun detected.
work-around: Break the ASCII file into several smaller

files and run this process several times. (501070)
Header Values
This module will fail with a message:
Improper delimiting in header list
Other Docs
Known Problems
If you attempt to list a trace header name that is only

one character long. The work-around is not to create
trace headers of one character. (303189)
History Viewer
The dataset history viewer will not access and display
the residual statics database filename if the Normal
Database option is not chosen in the Apply Residual
Statics menu. If required for display purposes you can
save the history viewer session, edit the file, and then
read that file back into the display session. (500929)
Hodogram Analysis
Users have reported this module generating theta and
phi polarization angles that make no sense. It is
suggested users check the output listing closely for
angles that are too large. (513376)
Horizon Flattening
Although code says 50,000 samples are allowed in the
pick table, we found that only somewhere between
12500 and 15000 picks are allowed. That is, a table with
12500 picks worked, while table with 15000 picks failed
with:
Error reading CDPs and TIMES from the horizon table!
work-around: Break into smaller pick tables (~12500 picks

per table) and run on subsets of data. (507364)
Horizon to RMS Velocity*
During the conversion to RMS, velocities are output only
for CDPs covered by the first horizon (when multiple
horizons are selected). If the first horizon cannot
encompass the entire line, run this process multiple
times, appending the output files as needed. (503109)
Horizon Velocity Analysis
The median and mean functions are switched when
running in the edit velocities mode. Use median
smoothing for mean smoothing, and vice-versa. (503108)
Other Docs
Known Problems
IF
In some cases the end of ensemble flag will not be passed
to subsequent processes. This module was redesigned to
better handle large volumes of data. If this flag is
essential, the work around is to either use Ensemble
Redefine after the IF/ELSEIF. Or use the same primary
key in the IF as you did in the Disk Data Input. (507877)
If you have nested IF/ELSEIF modules in a flow and the
primary key is the same as in the input step you may get
unexpected traces output. The work-around is to use or
create a different header. (512958)
Inline Geom Header Load
When overwriting a dataset, the following warning: Format
is 1, should be 2 indicates that a standard header has been
created with the wrong type. For example, OFFSET
might be inadvertently created using Trace Header
Math prior to loading geometry as an integer value, yet is
required to be a floating point header. The incorrect
header can be deleted prior to the Inline Load step using
the Header Delete process, or the output should be
directed to a new dataset. (503296)
Marine Data Only: This process can fail with a SIGSEGV
error if you run Extract Database Files, and then
attempt to load the geometry based upon the Match by
valid trace number designation. You should be able to
load geometry by matching on SIN, or by creating a
unique trace header such as SOURCE using Trace
Header Math. (503873)
TIM_SHOT values with 7 digits used to match header
and database values fail to load headers properly,
indicating that certain shots are not in the database. If
required, place the TIM_SHOT value in a different
header, such as DAY_SHOT, which will then correctly
match the larger values. (506811)
Linux Only: Marine inline header load may fail if SRF
OPF FOLD attribute does not exist. The work around is
to bin receivers in the spreadsheet. (515840)
Interactive Data Access
When using IDA with Trace Display and displaying large
datasets, (such as 100,000 traces), you can experience
Other Docs
Known Problems
difficulty using the backwards arrow. Using the back

arrow to go back one ensemble works the first few times,
however, paging forward and backward three or more
times, may take you back to the beginning of the sort.
From this point on, the back arrow will take you to the
beginning of the sort unless you specify a new sort.
(507388)
When using IDA with Trace Display, IDA can fail when
requesting more than 600000 traces. (507462)
When multiple applications are set up to run IDA from a
single X-server, all applications will send and receive the
same PD messages. Avoid multiple IDA sessions from a
single screen unless it is intended to use the same traces
by all active IDA sessions. (506040)
If IP address is specified rather than host name for
display device, IDA displays first ensemble then hangs.
the job runs fine without IDA. (511240)
Inline Geom Header Load in ProMAX 2003 behaves
differently on marine and land data. If the input dataset
for Geom Load has some dead traces (TRC_TYPE 2),
land data processes all the traces while in case of marine
data dead traces are dropped. (1147104)
Insight Data Input
LINUX Only: Fails with a socket error, no known workaround at this time. (518077)
Interactive Radon/Taup Analysis
Attempting to use the SUBTRACT option in this module
may cause it to fail with a signal 11 error. There is no
known work-around at this time. Fixed in version
2003.3 (513560)
Interactive Spectral Analysis
The process fails with a SIGSEGV error when using
stacked data on input, and the Primary header for
trace label is left defaulted to Source. Set the labelling
header to CDP, or some other poststack entry. (501620)
If only one trace is input the program fails with the
following message in the job.output:
Ensure failed (old._ny==yOld.n()), file
Other Docs
Known Problems
/advance/port/src/lib/agC/Bytemap.C line 70
work-around: Input 2 different traces in Disk Data

Input.(506977)
If you perform an extreme or microzoom on one of the
tiles such as the spectral or phase display, you can experience the windows hanging while the screen refreshes
or the process can exit out of the X-window. (507133)
Solaris Only: You may experience Grayscale colormap
problems if you:
1) Run a ProMAX session without other applications,
such as SeisWorks which will feed ProMAX correct
colors.
2) Select Multiple subsets in the ISA menu. (507284)
work-around: If Interactive Spectral Analysis displays
strange colors or black, click Data ->Trace Display ->
Color map-> Color. Then select Options -> Spectral
Analysis. This sets Trace Display to the strange colors.
Go to your original display and select Data -> Trace
Display, your colormap is switched back to Grayscale.
If you iconify then restore the display access to the color
map is no longer possible. The work-around is to re-start
the flow. (515299)
The method used to scale the forward FFT in this module
differ from the one used in Trace Math Transform. The
latter is more accurate. (126876)
Solaris Only: The T-X display will be all black is the
Xdefault *.useColorObj: False is set. (138726)
Interactive Velocity Analysis*
This process will still run but is no longer supported on
the current certified platforms. You are encouraged to
use Velocity Analysis.
Interactive Vel Editor*
When using the Input/Set velocity option with a value of
0, the stored values are set to 1.0 e-5. If hard zeros are
required, you should first set a constant non-zero
velocity, and then add the negative velocity value in a
subsequent step. (503179)
Other Docs
Known Problems
Interpretational Mig. Vel. Analysis

This module will fail with the message Abnormal termination
Signal = 10 if the input dataset is missing any CDPs.
(509261)
List/Restore from Tape
The option to Restore 5.0 does not work. To restore 5.0
Archives, run the tar command from the UNIX command
line. 5.0 Archive files are written with a ./ prepended to
the full file name. (500856)
When restoring a dataset from a Line/Survey, you are
prompted for the Former Area name. The parameter can
be filled out, but is not used during the restore process.
(501777)
Upon completion of any Restore operation, the
job.output file should be reviewed for the occurrence of
any UNIX errors. The restore job may continue to
completion, even though errors similar to the following
may exist:
Unix error - broken pipe
ctar: Error reading file xxx/yyy/...
The dataset affected by the error can be restored in a

rerun of the Restore operation, selecting the appropriate
dataset. Individual files can also be restored by running
the ctar executable from the command line. (502043)
The following error can be encountered when restoring a
ProMAX Release 5.1 archive:
Encountered checksum error on file xxx/yyy
work-around: Set Ignore checksum errors to Yes.

Warning messages are still printed for those files which
encounter checksum errors, and the integrity of those
files should be verified if possible. (502019)
The Header Dump option does not work, failing with the
error message:
No mode (-c, -x, or -t) was specified
There is no work-around for this error. (503124)

ProMAX looks in the original secondary storage
directories, if they exist, and accesses old directories
Other Docs
Known Problems
rather than using the secondary storage directories

listed in the config_file. (507033)
When restoring a new AREA, the user interface will not
automatically refresh and show the new AREA. The
work-around is to either add a new AREA or select the
config button at the bottom of the user interface and
toggle the Sort Areas option from yes to no. Either of
these will cause the user interface to refresh and show
the new name. (301664)
Setting the parameter Use primary storage for trace files
= yes does not prevent ProMAX from attempting to write
to secondary file systems. (515425)
Make Database Basemap
This process requires a ZMS license feature. If you do
not have a current ZMS license at your site, we have
included a demo ZMS feature to enter in your FLEXlm
license file. This entry can be found in the file:
$PROMAX_HOME/etc/zms.license.
If PD is not running, the program fails with the error:
Could not open a PD connection. Error = 300000000
work-around: Start PD manually with

PROMAX_HOME/port/bin/start_pd or run another
program that will start PD, such as VVE. (507356)
Linux Only: This module fails with a PD related error.
No work around at this time. (516196)
The Zycor routines used by this module have a limit of
80 characters for file names. The error message is:
Error submitting deck to ZMS Server
Work-around: Create short symbolic links to

$PROMAX_HOME and $PROMAX_DATA_HOME.
(518724)
Marine Trace Decimation
This module sets the TRC_TYPE value to be the same as
the last trace decimated in the ensemble. If this happens
to be something other than 1 it could result in traces
being dropped from a dataset. The work-around is to use
Trace Header Math to re-set the TRC_TYPE = 1. (303033)
Other Docs
Known Problems
Merge Database Files

The following error results if one of the line names begins
with a numeric value:
Error occurred in OPF routine: MERGE PROCESSOPF unable to
initialize source area: xxx, line: yyy unable to perform merge
The problem can be avoided by renaming the line to start

with an alphabetic character. (502233)
You can experience problems when trying to merge
database files in conjunction with a previous ProMAX
5.1 database. The work-around is to use Extract
Database Files to create a database under the current
version. (507234)
Migration Vel Analysis
LINUX Only: Fails with the following error. (517578)
Parameter ifx does not exist in the packet file!
Quitting
NN Horizon Picker
The program fails with following error message if the
TRC database does not exist (507492,504682):
Database error - error opening database file, Error creating AUTOSTAT
database entry.
work-around: Create a new line. Place Extract Database

Files in flow before NN Horizon Picking (TRC exists).
This module will not run on 3D un-stacked data.
(513180)
Noise QC Monitor
This process has been compiled for AIX systems only.
(300405)
Normal Moveout Correction
3D Only: This module uses the CDP_X and Y
coordinates of the first trace in the ensemble to
determine the interpolated velocity to use. If these values
are inaccurate, or different from the rest of the traces in
the ensemble, an incorrect function will be applied.
(512197)
Other Docs
Known Problems
NMO correcting data using velocities output from 3D

Dip Velocity Analysis yields a SIGBUS error on Solaris,
a SIGSEGV error on IBM, and runs on SGI but produces
bad results (traces with amplitudes of 0 or a constant
number) (123666)
Work-Around: You have to use a statically linked
executable from ProMAX 6.2 with a 6.2
$PROMAX_HOME/port/misc/header.list and 6.2
menus.
Pad 3D Stack Volume
Some users have reported that when padding by inline,
zero fold inlines are not output. (512543)
Putting Trace Header Math tools that generate negative
ILINE_NO values after a Pad 3D Stack Volume corrupts
the ILINE_NO trace header values. The work-around is
to put a Disk Data Output after Pad 3D Stack Volume
and a Disk Data Input before the Trace Header Math.
(512950)
Pad Traces
If you sort input traces with duplicate CDPs existing
within the primary sort order (Common Offset DMO
binned data), Pad Traces followed by a Remove Padded
Traces drops all but one of the duplicate CDP traces. If
the Remove traces is included in Pad Traces, all
duplicate CDP traces are dropped. (500689)
The program does not function properly if you select the
option to remove duplicate traces in a bin, and the last
trace in an ensemble is a duplicate. (505508)
Parallel Max. Power Autostatics
If the number of inlines is not evenly divisible by the
number of nodes this module fails with the message:
(132520)
Bad start INLINE number
This is fixed in version 2003.3.
Other Docs
Known Problems
Parameter Table Editor

When you use CREATE to make a default table, values
for NULL are 0.0 and 1000.0. Should be 1, otherwise
when used in VVE module crashes with following error:
(507752)
Warning occurred Message is:
Unexpected Z description, TIME. Changing to TimeAssertion failed: jy>=0,
file /seg/71/advance/port/src/lib/agfc/tb3.c, line 447
The next sub-flow will not be executed due to errors Abnormal termination
(/ProMAX/sys/exe mainWin.exe) Signal = 6 (Core file generated)
The requested trace editing key SKEY isn't in the trace header!
This message may appear if you have Trace
Kill/Reverse in your flow where your parameter table
has been corrupted by the SKEY header. (512541)
work-around: Since tables with the SKEY header cannot
be read in, you will have to Create a new table selecting
the correct primary and secondary keys, then
export/import the values from your old table into the
new one.
Attempting to import an ASCII file into an existing
parameter table that is smaller will either fail or delete
the original data in the table. The work-around is to
create a new table to import into. (515428)
Phase Shift 3D Migration
This module is cutting off the last sample. If you need to
perform an operation where this is critical, such as
removing AGC scalars, run Trace Length to restore data
to the full length. (514071)
Phase-Shift or Stolt 3D Migration can error out in
Remute/Rekill server stage, even if this code is not used.
This seems to be most prevalent when a big proportion of
the data is dead. (In this case, about 40%). Contact
customer support for a possible patch. (129225)
Plot CGM+ Plotfile
Zeh Only: In order to get Zeh 4.2.5.20 to run with
ProMAX 2003, you need to use the
$ZEHOME/config/zeh_plotfile script provided with ZEH.
Other Docs
Known Problems
As we did before, check the zeh_plotfile script to make

sure your NODENAME, PASSWORD, SCRDIR,
DAEMDIR, and PRGDIR are set correctly. Then simply
copy this $ZEHHOME/config/zeh_plotfile script to your
$PROMAX_HOME/port/bin directory. (you can rename
the zeh_plotfile script that is in your
$PROMAX_HOME/port/bin directory to something else
to preserve it first). If you are using OpenWorks, you can
also copy the $ZEHHOME/config/zeh_plotfile script to
the $OWHOME/hardcopy/bin directory. Make sure this
script exists in your $ZPSPRG directory as well. You
should then be able to successfully run Plot CGM+
Plotfiles* as long as your config_file file has your plotter
device defined and cgmplot line filled out properly.
(131309)
SDI Only: This module is in-compatible with the latest
version of SDI software. Work-around: submit plots from
the SDI GUI. Contact support@lgc.com for a possible
patch. (145361)
The UNISEC Create CGM+ module does not put the VDC
extents in the .cgmp file, since the .cgm file is metric the
extents are not required by the rasterizing software.
However Plot CGM+ Plotfiles is expecting them and fails.
Work-around: Submit plots via the plotting vendors GUI
(SDI,Zeh, Larson) (148249)
Post-Stack Inversion
Does not check min and max frequency values for valid
input. (508075)
The threaded version of this module runs much slower
than the non-threaded option. (515603)
Progressive Mute Analysis
In 3D, if the mute table is picked on CDP ordered data it
should be resolved before using this module. Otherwise
the extrapolation is un-reliable. (507672)
Prestack Kirchhoff 3D Time Migration
TMPDIR is being prepended to scratch directory path. If
you have TMPDIR being set somewhere, you may find
that TMPDIR will be used as your scratch directory
versus what you set for PROMAX_SCRATCH_HOME.
Other Docs
Known Problems
This can be verified by running UNIX Commands: show

environmental variables in your flow. (513228)
work-around: In your config_file you may insert the
variable: merge temporary directories: psh
in order to override what is being set by TMPDIR.
SGI: Restart from checkpoint fails w/ signal 15 if you do
not have a Disk Data Output in your flow. This seems to
be random on different SGI machines. (513213)
The downward statics are being applied in full but the
upward static is about 1/2 of what it should be. A
statically linked new executable is on the ftp site under.
product/ProMAX/v2003.0/<platform>/exe
README_127776 and kirktime3d.exe_127776.Z (a
compressed tar file) (127776)
Pre-Stack Kirchoff Time Migration
This module will fail if you set antialiasing to yes and let
it compute (0.0) trace spacing. Work around is to input a
valid number. (508042)
If you request specific offset planes and ask for every cdp
to be output, the job fails with a SIGBUS error. The work
around is to explicitly set the output bounds to remove
the edge CDPs, or do a Get All in Disk Data Input.
(702352)
Linux Only: This tool fails with a socket accept error.
Contact support@lgc.com for a possible patch. (147022)
Prestack Kirchhoff Depth Mig.
AIX Only: This module fails with a segmentation fault
message. (134149)
AIX Only: This module fails with a segmentation fault
message. (134149)
If you are specifying output CDP increments greater
than the input CDP increment, anti aliasing filters will
be applied. With coarse output CDP spacings, the
program will perceive almost all the dips except for the
flat ones to be aliased, and therefore all your dips are
filtered. We recommend an output CDP increment equal
to your input CDP increment be used. (139669)
Other Docs
Known Problems
Prestack Wave Equation Datuming

This process requires the trace header SRF_SLOC. This
header is not always defined for geometries described
under the 6.0 release. Use Trace Header Math to set
SRF_SLOC = REC_SLOC if required. (502110)
ProMAX 3D Viewer
After changing data range, color or scaling parameters
you are asked to reread the data volume. This second reread is not normally required and the dialog box may be
dismissed. (507806)
It has been reported that sometimes if you have multiple
entities on the screen, i.e. combinations of opacity and
animation, when you change the parameters of the
opacity cube all of the entities disappear and you have
to reread to get them back. No other known work-around
at this time. (507808)
The environment variable TMPDIR is not recognized
when creating CGM files. The temporary files always go
to /var/tmp. If this directory is too small a possible
work-around is to create a link pointing to a larger
filesystem. Or set the environment variable TMPDIR
prior to runing this module. (512924)
The 3D Viewer in Promax will not run without an
OpenWorks license available. In 1998.6 it gave the same
error, but then went ahead and started the viewer.
Contact support@lgc.com for a fix. (132103)
Pulse Test
SGI Only: This module generates incorrect results on
IRIX systems. The work-around is to use Interactive
Spectral Analysis to view the amplitude and phase
spectra. (510497)
Q Compensation
This module behaves differently depending upon
whether you select the menu from the VSP interface or
the 2D/3D interface. If you are applying Q
Compensation to normal seismic data, be sure that your
flow is built from either the 2D or 3D interfaces.
(508582)
Other Docs
Known Problems
Radon Filter
Radon Filter can create an artificial AVO response.
Radon Filter increases amplitude with offset on the
near offset traces and then causes an amplitude
decrease with offset on the far offset traces. (507281)
work-around: Do not band-limit the modeled output in this
program, use Bandpass Filter.
Radon Analysis allows the picking of water bottom
relative mutes. Radon Filter does not. The work-around
is to first flatten on the water bottom and not use water
bottom relative mutes. (512849)
Specifying "Minimum time of interest" other than "0"
multiple gates does NOT work. (141209)
Read Sierra Velocity Model
This process will abort without an error message if there
is a carriage return at the end of the line containing the
model name. The <cr> character must be deleted by
editing the input file order to be read into ProMAX.
(505671)
You may encounter this error when reading some Sierra
Velocity Models.
Unable to interpret model file header
It is not narrowed down to any specific type of model but

instead is random. (513205)
Reflectivity/Synthetic Logs
The option to add multiples/transmission losses to the
synthetic traces is in error. The amplitudes are too low
and the polarity is reversed. The work-around is to use
either Finite Difference Modeling or Synthetic Trace
Generation. (508201)
Refraction Statics
Linux Only: When attempting to edit the GRM Depth
Model using MB1 to select does not always
register.Cycling through the solutions may cause it to
register. (130535)
Other Docs
Known Problems
Linux Only: If you display traces while editing first

break picks the position of the SIN may not be correct
until you begin to move through the volume. (130534)
Refraction Statics Calculation
If you choose to use refractor velocity option in the
statics calculation, rather than user defined, then you
must also calculate the depth model at the same time.
Otherwise you may get extremely large statics output.
(507822)
If the sort order in the Sources spreadsheet if different
from the Receiver Spreadsheet Refraction Statics will
generate an incorrect depth model. The work-around is
to sort the spreadsheets so that both are increasing in
the same direction. (126886)
Resample Log
This process may add zero samples to the bottom of the
log. If required, a Trace Length process can be used to
bypass these samples. (503923)
There is a problem with Resample Log and Well Log
Pad to Surface being in the same flow. (507238)
work-around: Run a Well Log Disk Data Output and Disk
Data Input between the resample and the Pad to
surface.
SEG I/O General
See also Tape Administration.
When Input primary selection choice is not set to
Input All, the process will read a maximum of 50,000
ensembles. (501900)
Maximum data block size in bytes in the SEG read
menus is now obsolete and will be ignored if set here.
You now have to set that in your device.tts by using the
variable MAXBLK="nnnn". (512672)
The NREW (no rewind) parameter in the device.tts file is
not being honored. Using NREW+NUNL may operate
properly. (514411,515409)
Other Docs
Known Problems
Seg-B Input
SEG-B Input assumes the record length of first record
for entire dataset. If the first record is shorter than the
rest, all other records will be truncated. The work-around
is to specify the record length explicitly in the menu.
(136816)
SEG-D Input
See also SEG I/O General.
You may encounter the following error attempting to
read I/O System Two tapes.
SEGD: I/O System Two, No lines detected.
There is no known work-around at this time. Contact

support@advance.com to see if a patch is available.
(509031)
Although the problem of reading FFID values greater
than 9999 has been addressed, there is still a problem in
the menu that prevents sorting on FFIDs greater than
9999. (510983)
When re-mapping headers the job.output will report 2
times the actual value of the byte location being remapped. (512469)
ProMAX is unable to completely extract geometry
information from the Western version of RAPS 2000 SegD tapes. (513039)
Menu: omit records of type: Docs specify that you
should be able to type in a string like 1:5:10:14........
however the emacs widget does not appear and you
cannot type this type of string. (512037)
Sercel 408 format: Source and receiver point and index
number are not properly mapped from the SEG-D
header to ProMAX. (513969) The workaround it to remap
them manually.
Main Header Mapping:
S_LINE,Shot Line,2I,,,69/
SOU_SLOC,Shot Station,2I,,,74/
Trace Header Mapping:
Other Docs
Known Problems
R_LINE,Receiver Line,2I,,,22/
SRF_SLOC,Receiver Station,2I,,,25/
Some formats of Seg-D are showing a 1 msec. time shift
from pre-1998.6 versions of ProMAX. This has been fixed
in version 2003.3. (304758)
Work-around: Transfer time of first sample in SEG-D
header to new TAPE_T0 header word. Header statics may
be used subsequently to shift trace data up or down.
On some 8048 format tapes ProMAX is not incrementing
the FFID. (133287)
Linux Only: X015 formats are not converting properly.
Contact support@lgc.com for a possible patch. (134764)
SEG-Y Input
See also SEG I/O General.
The option to read in data using a primary sort of
Receiver is inoperable. The process will fail with a
SIGSEGV Signal 11 error, or with a Primary key out of range error if
a Data Output step is included in the flow. The data
should be read into the ProMAX system with the SEG-Y
Input defaults, and resorted as necessary. (503544)
The menu does not currently allow for input of the value
0 for the parameter Number of errors in a row before
aborting job, even though the value of 0 can be used to
indicate that all such errors should be ignored. The
type_desc option in the segy_read.menu file can be
modified as follows: (503652)
parameter: ABORT
type_desc: (int 5 1 99999)
should read
type_desc: (int 5 0 99999)
The process can incorrectly modify the LIN database

units of measurement from meters to feet when used
with an existing database, if the input SEG-Y file is also
not detected as metric. The LIN attribute IUNITSZ can be
reset to a value of 3 for metric. (503739)
Solaris only: Reading Western MS-DOS or Charisma
formats from tape, the job says it has completed
normally, but the Job.output reveals that it has actually
Other Docs
Known Problems
failed w/ the error: (507749)

AFILE: signal termination.
This module suffers from the same problem as Disk

Data Input when attempting to sort values greater than
8.333 million. work-around is to use IF to sort after
using Get All in the Seg-Y menu. (507859)
Values greater than 50,000 are not allowed in the sort
list. Work-around is to use an IF statement after Seg-Y
input to select these ensembles. (513004)
The job.output only reports the units of measurement if
they are English (feet). (303429)
The gain is not being decoded correctly for the 32 bit
fixed point format (4 byte with gain). (513323)
Menu accepting disk image with sample interval of 0. If
you enter a value of zero, the menu will not override it
with a non zero value. (513064)
When using the TTS CONFIG="MFM" option to ignore
multiple filemarks between records job errors on last
record and goes into infinite loop. ProMAX reports the
following error (513375):
EXECUTIVE TAPE SOCKET ERROR: Attempt to send 4 byte block failed.
UNIX error: Bad file number
Trying to read a multiple tape Seg-Y file using an

Overland stacker, the job may hang on the second tape.
Contact support@advance.com for a possible fix to the
proclient binary. (514208)
Although the option to save the EBCDIC header to the
dataset history works, you cannot view it using the MB3
history. (514168)
SOU_H20D and REC_H20D not being read properly if
they are in the default byte locations. The work-around
is to re-map them elsewhere. (305060)
There is a limit of approximately 63,000 samples per
trace. Exceeding this limit causes the job to fail with
memory errors(148281)
SEG-Y Output
See SEG I/O General.
Other Docs
Known Problems
Any flow with more than one Seg-Y Output in it will fail
unless there is an input module between them. (507871)
Depending on the number of input samples this module
may pad extra samples on the output trace. This only
happens if the output format is 1 or 2 Byte formats.
(509875)
Multiple Seg-Y Output modules in the same flow fail
with the message, "Error trying to open a device". There
is no known work-around at this point. (513366,513782)
The automatic system generated EBCDIC header has the
area name twice, rather than Area and Line. (514169)
If you modify a flow and save it in 1998.6 and the SEGY
Out menu is from 1998.1, the save will delete the SEGY
Out menu. (514108)
not being honored. (514411,515409)
Linux Only: Flows with multiple Seg-y Outputs will fail.
(137213)
SeisWorks 2D Seismic Info
Trying to run this module with an old menu will give an
error. The option Shift MB2 to overlay a new menu does
not fix it. Users must bring in a new menu from the
processes list. (515674)
SeisWorks Horizon Input*
For 2D data, horizons are input with primary and
secondary keys of LINE_NO and FRN_TRNO. These
horizons can be interactively displayed and manipulated,
but some processes such as Database/Horizon
Transfer, can require different table sorting to work
properly. In this case, the horizon can be exported to
ASCII format, and reimported with the required sort
keys. (503129)
Display of horizons input to ProMAX using this process
may fail if the associated trace data was not created in
the ProMAX system using SeisWorks Seismic Input.
Input of both horizons and data from a SeisWorks
project should resolve this problem. (502983)
Other Docs
Known Problems
When ProMAX writes horizon files (.hzd) to SeisWorks

they are not visible until the index is re-built. (303246)
SeisWorks Seismic Input*
Queued Jobs: Do not submit multiple jobs from the
same flow, as input information is taken from the most
recent job submission. If queueing is required, you
should replicate the flow and submit queued jobs from
the separate flows as needed. (504219)
All input records will be truncated to the length of the
first trace encountered in the flow. If differing trace
lengths are required for multi-line input you may need to
pad the record length of the first line pulled from the
database, or create a dummy line containing the desired
attributes to be read first. The problem will be further
complicated if multiple sample rates are encountered.
(504175)
work-around: Group the 2D lines with similar parameters
together for a single run. Make a separate run for each
group. You can use SeisWorks Seismic Input Info to
find such groups before running the job to input data.
Do not use the Entire Survey option if the SeisWorks
project has a subset of all lines in the survey. (X or Y
increment in the Master Grid Coordinates not equal
to 1). The following error results:
ExfVolInit: trace increment specified must be a multiple of the minimum
possible trace increment for the current project
Explicitly specify the minimum increment in the ProMAX

menu in these cases. (506867)
This module will fail with the message:
error message warning: parent width too small in multiple_menu_choose
If the 2D SeisWorks project has more than 1000 lines.

(513077)
This job will fail if there are only two entries in the plist
file. (138845)
SeisWorks Seismic Output*
If a job containing SeisWorks Output is started and
then killed, the output dataset name should be verified
Other Docs
Known Problems
in the menu prior to restarting the job. The menu can

inadvertently pick up the first dataset name from the
Project list of datasets. (504264)
If you are running ProMAX 1998.6 but are writing to OW
R98 or R98+ (1998.0 or .1) and are attempting to add a
NEWLINE to a 2D project, you will get this pop-up:
Project _auto_extend:Permissions_error: Cannot extend project
OWPROJECTNAME data model. The project model extension script
$OWHOME/bin/extendOW50Rev0ToRev5.sh either does not exist or does
not have execute permission. Pls check this file and try again.
This EXTEND script only exists in OW1998.5 so it works

if you are writing to that. If you want to add a 2d line in
1998.1, you will have to do that with OpenWorks,
redefining the survey. (512505)
The ProMAX menu allows users to type in a longer 3dV
filename than the BCM program will read. Users should
limit the filename to six characters if BCM is to be used.
(513608)
When writing large files out to Seisworks the default of
5000 for the parameter Checkpoint Modulus may slow
the process down. Try either setting this to "0" to disable
checkpoint or set to a high values such as 1,000,000.
(141626)
Spiking/Predictive Decon
The parameter Window Rejection Factor is only applied
(i.e. a trace is killed) based on the deepest gate and
operator pair. (508205)
Example:
Window Rejection Factor = 2
Operator Lengths = 200,200,200
Gates = 500-600,800-900,1000-1390
In this case all traces would be killed because the last
gate width is 390, which is less than 2*200.
Gates = 500-600,800-900,1000-1500
In this case all traces come out live because the last gate
is larger than 2*200. However these traces should have
been killed because the shallow gates are still less than
2*200.
Other Docs
Known Problems
Split / End_Split
Tools which initialize a new header will fail when placed
inside a Split/End Split branch with the error:
Trace headers corrupted
Those processes must be run outside the Split/End

Split processes. (502883)
Fails when placing Parallel Begin/End inside of
Split/End Split. (513181)
Current tool is END_SPLIT
Trace headers corrupted (5)
Current ILINE_NO is 8
parameters
(number X in the flow) Message is:

Current CDP is 557
Please check input
Sort selection does not function properly when the

primary header word is an integer and the secondary
header word is a float, or vice-versa. (514179)
Stack 3D
IRIX Only: Submitting jobs to LP queues is causing
$TMPDIR to be re-set to /var/tmp. (514084)
The work-around is to edit the file:
$PROMAX_HOME/port/bin/PromaxRuntime script
adding the following line:print unset TMPDIR
This module will fail if more than one hostname in listed
for the parameter Enter Name of Host. This parameter
is designed to allow execution on a host other than the
one currently running ProMAX. It is not there for
distributed parallel processing. (304207)
Steepest Ascent Autostatics
Option to decouple source/receiver statics solutions
does not appear to be working. Setting Similarity of
common source & receiver statics equal to 0 has no
effect. (507451)
Stolt 3D Migration
Phase-Shift or Stolt 3D Migration can error out in
Remute/Rekill server stage, even if this code is not used.
This seems to be most prevalent when a big proportion of
Other Docs
Known Problems
the data is dead. (In this case, about 40%). Contact

customer support for a possible patch.
Synthetic CDP Generation
This module may not output live traces to the maximum
offset specified in the menu. (514643)
This module is generating incorrect reflection
coefficients. (148738)
Tape Administration
Accessing the Status button on a multivolume tape read
job where the tape stacker is in the process of changing
tapes will issue a spurious mount message. You must
wait for the stacker to complete changing tapes, and
then reply to the New Stack is loaded continuation message.
The status button is also not accessible during tape
rewind. (502650)
Problem: Tape mount dialog window pops-up but you
cannot see the text. The solution is to add entries like
these to the.Xdefaults file in each users home directory.
ProMAX Tape*background: MistyRose
ProMAX Tape*foreground: sienna4
LINUX Only: The TTS TAPE_REQUEST is not

communicating with opcon. ProMAX hangs with a tape
request to opcon. (127983)
Linux Only: The documentation for setting up Linux
stinit.def file. Please download the file quick.pdf from
the Landmark ftp site. (516215)
The variable CONFIG=BCAT is not being recognized.
Users should switch to the variable CONFIG=NCAT
instead. This may be placed either in the device.tts file or
edit the Proclient script. (126439)
the DEVICES file.
Other Docs
Known Problems

Tape Copy
Solaris Only: This process can fail on write with the
following error:
Error writing block to output device Error = 22
The problem is currently unresolved. (503263)

The option to use multiple output drives may not work
correctly with some tape systems. Copy operations will
be performed on the first output drive only. (504199)
When attempting to dump traces once in the Tape
Dump user interface, the user interface can crash. This
seems to be random. (507309)
Tape Dump
The Header Only option gives zero size error message
implying an empty file. The work-around is to use either
the Data Only or Both option. (512645)
8mm with argument SMNG will not dump. You should
be able to dump 3490 tapes configured in the pmx
database with SMNG., however an 8mm drive with this
set has been seen to fail. (90127)
Work-Around: delete the SMNG argument and add FMNT.
Tape Data Input
This module will give the false error message:
Unbalanced parentheses were found in a number string
This happens when you use the square brackets [.] in

the sort list. The job will complete normally with the
proper traces read. (508165)
Can no longer select a subset of traces in Tape Data I/O.
(90197)
work-around: You can use SPLIT o IF to select a subset
of traces.
Other Docs
Known Problems
Setting the parameter MAXBLK to anything other than

default may result in ProMAX being unable to read
multi-volume datasets. (513607)
LINUX Only: Tape Data Input will read the first tape and
ask for the second tape, but even though it says the job
is running, no traces from the second tape are being
read or written out. (142620)
Tape Data Insert
A Signal 6 error can be encountered if selecting traces by
database header limits, and the number of entries
implied by the input sort string does not match the
number of header entries selected as sort keys. (504058)
This process allows shared device with merged insert.
However, it should not do this. In our example problem,
the merge option is selected and the device name was left
the same as Tape Data Input. The job ran, but obviously
it cannot merge data when the insert dataset is not on a
device. Job should fail with the message, cannot run merge
insert in shared device mode. You must select the merge option
and select a different device name in the menu. (507203)
This module will give the false error message:
Unbalanced parentheses were found in a number string
This happens when you use the square brackets [.] in

the sort list. The job will complete normally with the
proper traces read. (508165)
Currently cannot do multiple blind tape reads on a
shared device (Tape Data Input/Insert on same
physical drive). This is due to the need to scan and write
to disk the CIND/CMAP files for each dataset during the
initialization phase. (511857)
Tape Data Output
When using the option to output a subset of traces, the
Trace list parameter does not recognize the square
bracket code used to identify groups of traces. For
example, 20-100(20)[3]. The trace list can be completed
without the square bracket string, or the data can be
Other Docs
Known Problems
subset prior to Tape Output using an IF-THEN block.

(502202)
The short dataset information for the extents of the
dataset (MB2 on dataset listing) can be in error for tape
datasets. (502421)
When encountering SCSI problems during a job run, a
job requested output to a second tape without writing
data to the first tape. In this case, volume 1 of the
dataset will not be available, and subsequent attempts to
read the data into the system can fail. (505001)
Tau-P Transform
This process requires a CDP database with valid
X_COORD and Y_COORD rows. Running the process
without a CDP database will fail with memory errors.
(506788)
Tau-P Inverse Transform
Traces output from this module will be flagged as traces
and geometry not matching the database. If the input
traces do indeed match then the user must run Trace
Header Math to reset these flags. (507838)
Time/Depth Conversion
This module may fail with a velocity file read error if the
velocity table is too large. The work-around is to
decimate the velocity field and make it smaller. (509239)
Time Slice Input
Vertical axis annotation will be incorrect if the horizontal
axis is inline. Possible work-arounds include using
INCREASING for axis increments when selecting
INLINE_NO for Horizontal axis; use XLINE_NO for
Horizontal axis; use only a single time slice; for
multiple time slices use Ensemble Redefine based on
the differences in the header slc_time. (512154)
Time Varying Trim Statics
Program fails after 3.04 million traces are read. (506933)
work-around: Run this process on datasets less than
approximately 3 million traces.
Other Docs
Known Problems
This module may fail because it runs out of memory. The

amount of memory needed depends upon the number of
offsets,cdps and horizons used. The best work around is
to increase the value for Window Interval. This reduces
the number of horizons. (507791)
Trace Display
See also Interactive Data Access.
Trace headers created as character strings are
annotated as zero values if displayed using the trace
labelling option. The Trace Display Label process, or
the interactive annotation button available from within
Trace Display can be used to create text annotation.
(502516)
When editing parameters, the Snap options can appear
to provide erratic results on some datasets. (504118) In
addition it has been noted that the Snap option can take
an abnormally long time to run on data sorted by
Inline/Crossline. (503118)
The Neural Net First Break Picker operating in
interactive mode does not pick zero crossing events
correctly. You are advised to pick on a peak or trough.
(503611)
The menu bar option to pick first break headers will be
active even if no valid first break parameter files are
available for selection. In this case, a Trace Header
Math used to set FB_PICK = 0.0 can be inserted
immediately before the display in order to create a valid
header. (504122)
The dx/dy function is labeled as ft/sec even if the
database is set to meters. (507881)
Solaris Only: Using MB3 to add new layer does not work
if you are running ProMAX on a Solaris 2.6 system and
displaying to an IRIX 6.5.x system. No known work
around at this time. (508097)
Selecting Grayscale as the Trace Display Mode in the
menu does not bring up Grayscale as the color map.
Users must select color64 from the Edit pull-down menu
then select the proper color table from the View pulldown menu. (302007)
Other Docs
Known Problems
View -> Edit colormap -> File -> Open -> greyscale.rgb
Attempting to display a previously picked Auto-Statics
Horizon may not show all the picks. The parameter
table is correct, the problem is in the display. (512949)
First break picks will not display if the primary sort key
in Disk Data Input is SOU_SLOC. The work-around is to
sort on something like FFID or SIN. (512964)
This module may fail with an Ensure failed... message if you
try to display too many samples. The work-around is to
display fewer traces. (513104)
Different results (worse) with NN Picking in Trace
Display compared to batch program NN First Break
Picker. (511000)
Trace scaling is dependent on the number of traces in
the ensemble. (303629)
1) "Entire" scaling is based upon each ensemble.
2) "Individual" scaling is based upon each trace.
3) Smooth is applied to traces within an ensemble.
4) Ensemble boundaries are important to Trace Display
and can have a noticeable impact on the resulting
display.
It is possible to generate parameter tables in Trace
Display that have negative start times. Some tools such
as Spiking/Predictive Decon will fail if one of these tables
is used. If you are making picks near time zero check the
resultant table for negative values (513724)
When Disk Data Output, or another output tool is used
in conjunction with Trace Display, Trace Display may
corrupt the last trace in the dataset if the Output Mode
is set to When Done rather than Immediate. (513405)
Solaris Expert 3D Graphics only: Trace Display does
not refresh properly after other windows display over the
top of the Trace Display. (303915)
Solaris: In Trace Display while picking layers, if you are
running ProMAX on a Solaris systems and displaying
back to an SGI the MB3 option to Pick another Layer
does not function. (513792)
Other Docs
Known Problems
The option to Exit/Stop flow does not work as expected

in flows containing multiple input steps. E.g. Disk Data
Input - Trace Display - Disk Input - Velocity Analysis.
Selecting Exit/Stop Flow in Trace Display stops the
Trace Display but the Disk Data Input and Velocity
Analysis will then run. (514259)
AIX Only: Selecting the MAX icon then a trace with MB1
may compress the display of trace header values,
making it impossible to see all values. The MB2 option is
fine. The work-around is to change the CDE window
setting to "Raise Window When Made Active" (515138)
AIX Only: Pop-up displays, such as the list of parameter
tables will appear blank if displaying on systems with
AIX versions earlier than those supported on version
2003.0. (513777)
Linux Desktop Only: When using the DX/DT option
MB3 should label the velocity on the screen. It does not
the work around is to use Shift + MB3. (130946)
Linux Only: If you kill a flow from the notification
window it takes Trace Display about 30 seconds to
disappear. (516062)
IRIX Only: This module will abort if the maximum
number of ensembles per screen is set to 10 or greater,
and the parameter, traces per screen, is set to 0.
(144587)
Solaris Only: If you are running ProMAX on a Solaris
system and displaying on a desktop using Exceed
7.1.0.2 the MB3 pull down menu will not display.
(149359)
Trace Header Math
The following expression used to work and now errors
with a message about mis-matched parenthesis (looks
like a code change caused a non-fatal condition to
become fatal, so the parentheses were being incorrectly
parsed. Before, it was just being ignored.) (511994)
ANGLE=ATAN(((sou_y-rec_y)/(sou_x-rec_x))/3.1415927)*180.
work-around: The following pair and alternate version all

work and produce the same results:
TMP=((sou_y-rec_y)/(sou_x-rec_x))/3.1415927
Other Docs
Known Problems
ANGLE=ATAN(TMP)*180.
ANGLE2=ATAN((sou_y-rec_y)/((sou_x-rec_x)*3.1415927))*180.
Trace Kill/Reverse
On 3D lines, if multiple FFIDs have the same sou_x and
sou_y locations, the trace edits called on these FFIDs are
applied only to the last FFID in the group. This will only
happen if the Trace Kill/Reverse list has been opened
with the parameter table editor. The editor attempts to
perform a 3D resolve on the table causing the problem.
(507685)
If the primary key for editing traces, such as
REC_SLOCS, becomes 8 digits or larger, adjacent traces
may get edited. The work-around is to choose a primary
key with smaller numbers or use an IF block to sort off
the REC_SLOCS to be killed and use a universal kill.
(509843)
The requested trace editing key SKEY isn't in the trace header! This
error occurs when your parameter table has been
corrupted by the SKEY header.(512541)
work-around: Since tables with the SKEY header cannot
be read in, you will have to Create a new table selecting
the correct primary and secondary keys, then
export/import the values from your old table into the
new one.
Trace Length
This module does not correctly re-set the trace headers
TLIVE_S and TFULL_S. Therefore it is possible that
applying a re-mute after this module will give incorrect
results. The work around is to use Trace Header Math
to manually re-set the headers. (507786)
Trace Math
When adding traces the OFFSET and AOFFSET trace
headers may get corrupted. The work-around is to either
save them to a user defined header or use a different sort
key, such as CHAN. (147861)
Other Docs
Known Problems
Trace Muting
The re-mute option may not give correct results if the
module Trace Length has been applied previously. The
Trace Length module does not correctly re-set the trace
headers TLIVE_S and TFULL_S. Therefore it is possible
that applying a re-mute after this module will give
incorrect results. The work-around is to use Trace
Header Math to manually re-set the headers. (507786)
Applying a bottom mute to data that has already had a
top mute applied will re-ramp the top of the trace. In
affect, the ramp will be squared rather than linear.
(507816)
The option to Apply where specified does not work
properly. In general, using the option Interpolate over
secondary key will give the desired results. (508337)
Trace Sample Math
When special characters (e.g. !,@,#,$,%,^,&,<,>,? etc) are
included in the equation (e.g 3 + #4 + 5) the program
assigns zero to everything after the special character (the
result from the previous equation is 3) The same is true
when using brackets, Also everything after a space is
ignored. (514024,514023,514022)
When numbers (e.g 1234) or mathematical expressions
(e.g sqrt(16), 1 + 4) are written on the left side of the
equation (e.g 1234=sine(sample)) the program outputs
the value of the left side of the equation instead of the
value of the right side. In the last example the output
would be 1234. This doesnt happen when an
alphanumeric expression is used on the left side.
(514026)
Trace Splice
Problems have been encountered when attempting to
use this process to splice poststack traces. If required,
you should be able to work around the problem using
Disk Data Input and Disk Data Insert in merge mode,
along with trace shifts and Trace Math operations.
(504215)
Other Docs
Known Problems
True Amplitude Recovery

The first trace processed through has anomalously low
amplitudes if the following conditions are true:
1) The WB_TIME trace header is present and contains a
non-NULL value.
2) The spherical divergence option is selected using a
spatially variant velocity function.
3) The dB/sec option is selected.
The work-around is to run Trace Equalization after
True Amplitude Recovery, or just kill/ignore the one
low amplitude trace. (513094)
Turning Ray Tomography*
Multiple iterations of this process may inadvertently fill
the LIN database. You should delete previous LIN entries
created by previous tomography runs (type TOMO) in
order to continue with further iterations. (504024)
TV Spectral Whitening
If you are using the Time-Variant option, you need to set
the Automatic filter panel design for the Time Invariant
option to "Yes", then toggle back to the Time-Variant
option. Otherwise you will get the error No input for
spectral balancing frequencies (135929)
UNISEC Create CGM+*
When plotting color overlays, it will not be possible to
label or profile header values that do not exist in the
overlay dataset. For typical velocity file overlays,
information may need to be built in the CDP database,
and transferred to the available CDP domain headers.
(503358)
Errors similar to the following may be encountered when
displaying the process history created via Automatic
Generation or Existing History, and the history text
contains commas.
Error in line 213 column 13
PARAMETER IS OUTSIDE LIMITS
SHOULD BE BETWEEN 0.005 AND 1.000
If commas, parentheses, or leading blanks are required,
Other Docs
Known Problems
the text string should be enclosed in single quotes.

(504603)
There may be problems executing a flow which has
previously been submitted or exited. Re-entering the flow
the Headers to profile can randomly deselect choices
made from the pop-up menu. In this case, you will need
to reselect choices and extent parameters. (504954)
The sidelabel is blank if Display processing history is
None and AUTOHT=ON. Use AUTOHT = OFF. (504805)
When requesting isovels above your plot, such as
PROFILE,ISO(ISO VEL,D,,,,0,2000)...the isovel lines will
plot, but there may be no corresponding annotation of
the velocities. (505022)
When using Headers to Profile or Headers to Label, if you
select headers from the pop-up menu and accept, you
will not be able to de-select all the options to return to
the none state. You would need to call in a new menu,
or comment out those statements in the parameter file.
(505084)
work-around: Use Create CGM+ plotfiles or open the
database program (XDB) select the SRF parameters and
select New - Project - CDP to manually project to the
CDP domain.
The flow will fail if more than three horizons are
imported. (301276) The error is:
Current tool is SEG_WRITE (number 4 in the flow) Message is:
Override trace header entry: NONE, not found in ProMAX trace header
The work-around is to use Database Header Transfer to

put additional horizons into existing header words such
as UPHOLE. Then add UPHOLE to the remap headers
list in the UNISEC Create CGM+ menu. Then add a line
like this in the .par file:
HORIZON,UPHOLE(horizon3,,.03,4)
If the sample interval of the seismic data is less than 1.0

msec. the job will fail with this error:
NSAM= 5001 SR= 0.000 ITIME1=
*** Error,RECL must be > 0
Other Docs
Known Problems
The workaround is to resample to at least 1.0 msec.

(513860)
The WIGMOD Parameter does not function. (137565)
User Interface
Renaming a line will cause datasets to be flagged as
having invalid trace numbers and geometries. Geometry
definitions can be reloaded, or in necessary, the global
trace matching flags overridden using Trace Header
Math. (502294)
The Copy routines for Area/Line/Datasets will attempt
to copy dataset files to the same partition in which the
original files reside, including those found on secondary
storage partitions. If a disk partition is filled due to
insufficient space during this operation, the copy option
will abort. (501703) If additional space is made, you
should specify a new output name, different from the
name used in the first failed copy operation. (501494)
When attempting to copy a Line which includes data
residing on secondary storage, the copy will fail with a
mkdir error, as the new Area/Line directories are not
available on the relevant secondary storage partitions.
Assuming that the config_file includes those secondary
storage partitions, the directories can be allocated from
within ProMAX by first creating the new Line, and then
touching that Line by activating the Database Display
tool. (501854)
For lines with OPF files spanning onto secondary
storage, copying that line into a newly created empty
area can fail. Failure results from required area level
directories not being created on the secondary storage
partitions. The problem can be avoided by accessing the
database from the new area. (502474)
Previously parameterized menus requiring selection of a
database parameter may not list newly created database
files. Exiting the selection list without a selection resets
the menu parameter to Invalid, at which time reentering
the selection shows all possible database selections.
(502593)
The notification status for a flow which fails because the
FlexLM license file does not contain a required feature
Other Docs
Known Problems
line is not captured by the UI notification mechanism.

The actual error is captured in the relevant job.output
file. If a flow simply fails to execute, you should check
the job.output file for this type of error. (503510)
If you have a dataset larger than 2 Gbytes and more
than 2 Gbytes worth of TRCn/HDRn files reside on the
same filesystem, then the MB2 history may report the
wrong size for this dataset. This is most likely to occur if
the maximum filesize in the config_file is set larger than
2000 Mbtyes. It is strongly recommended that this
value NEVER be set larger than 2000. (507909)
Problems running on <host> if <host>_PROMAX_HOME
is set. If you have defined in your .cshrc
<host>_PROMAX_HOME set for various machines with
tape drives, and HOST1 with HOST1_PROMAX_HOME
set, the UI hangs at start-up, never making it past the
logo screen. On HOST2, the UI comes up but points to
$PROMAX_HOME/data rather than to
$PROMAX_DATA_HOME. (512542)
Explanation: Conceivably this may be expected behavior.
For example if <host>_PROMAX_HOME is supplied
where host is the current machine this will supersede
ANY PROMAX_xxx_HOME variables. So for example
PROMAX_DATA_HOME would be ignored in preference
to <host>_PROMAX_HOME/data. IE the presence of the
<host>_PROMAX_HOME hides the
PROMAX_DATA_HOME and the default data is used.
Workaround: Put IF blocks into the .cshrc or start up
script to avoid setting <host>_PROMAX_HOME unless
its really remote.
If you have a help file open and are viewing a job.output
at the same time, closing the job.output window will also
close the help file. The work around is to use this
environment variable. (513437)
setenv PROMAX_HELP_KILL_POLICY t
Setting the environment variable TMPDIR will cause
ProMAX to create files in /tmp that do not get
automatically deleted. If you must use this variable then
you should check the/tmp directory periodically.
(303832)
Other Docs
Known Problems
Using the Print Flow option on a flow containing any of

the Seisworks I/O menus will cause a core dump.
(303803)
If you are using MB2 to check the status of a dataset
while it is being written to disk it is possible that ProMAX
mistakes this as a duplicate trace being created and
stamps the dataset as not matching the database.
(513095)
Changing the batch queue priority from the ProMAX UI
also changes the priority for interactive jobs. This is fixed
in version 2003.0. (125582)
The User Interface may crash if you build a flow with a
tape input tool such as Seg-Y Input and your device.tts
file has an unmatched end quote (). (125386) The error
message is:
Error in lisp call string concatenate. Some are not a string.
SGI Only: On SGI systems configured to run two

monitors as one X-Session, ProMAX will refresh screens
twice as much as it normally does. Contact
support@lgc.com for a possible patch. (129158)
If you have your Areas sorted alphabetically and copy an
area, the Area at the top of the list is opened rather than
the newly copied one. (130531)
LINUX Desktop Only: Depending on the screen size and
resolution the Product button may not appear on the
screen. This makes it impossible to change products
from the User Interface. The work around is to make the
fonts in the ProMAX Xresource file smaller. (515979)
When using Shift MB-2 in the ProMAX UI to refresh a
process menu, the process will be enabled after the
refresh irrespective of its status before hand. (516417)
When using Shift MB-2 in the ProMAX UI to refresh a
process menu, the process will be enabled after the
refresh irrespective of its status before hand. (516417)
The button on the User Interface under Config that
allows the user to have pop-ups remain after the mouse
is moved out is ineffective. (516862)
Other Docs
Known Problems
When you print flows with Menus like Trace Header

Math that allow you to type in parentheses. They do not
show up in the output HTML file. The work-around is to
manually edit the HTML file. (144140)
Velocity Analysis
This process may not display pre-existing functions for
editing on some lines, due to differences in the
resolution of X,Y coordinates derived from the input
table as compared to the actual CDP X,Y values found in
the database or trace headers. This will most often arise
when using the output from the DMO to Gathers 3D
process as input to Velocity Analysis. In the case of 3D
DMO gathers, CDP database coordinates can be
transferred to the trace headers prior to Velocity
Analysis. (503390) If this problem arises in a more
general case, a more lengthy work-around using the
import and export of information to modify the velocity
table coordinates can be provided by contacting a
support representative. (503234)
This module does not honor the trace headers TLIVE_E
and TFULL_E when calculating the semblance. Instead it
honors the global trace length. Typically, this will only be
a problem if the data was modified by modules such as
Trace Length or Time/Depth Conversion. (508600)
If the output velocity table name was made by choosing
the ADD option, this module will fail with a signal 11 or
SIGBUS error. The work-around is to choose CREATE
rather than ADD when making a new table name.
(512652)
When the number of samples in the trace is less than the
number of precomputed semblance traces, you will get
an incorrect velocity scale. The work-around is to either
reduce the number of semblance velocities or lengthen
the traces. (513075)
Users have reported that at analysis locations whose
offset distribution are limited, the display gain in the
first stack panel may be unusually high. The cause has
not been determined at this time. (513347)
Setting the "Contrast Power Factor" in the "Semblance
Parameters" to a non-whole number may cause red
horizontal bands to appear in the semblance display.
(513631)
Other Docs
Known Problems
On some datasets if displaying horizons the display can

invert. I.e time 0 is at the bottom of the display. Any
picks made on this display will be fine. The work-around
is to turn off the horizon display. It may also be caused
by displaying horizons on the dynamic stack panel.
(513482)
If you select a new velocity table from the File menu in
the Velocity Analysis display and save picks to that file
you are not able to edit or use the table. (513810)
If the parameter Semblance Width is changed within
Object Visibility of Velocity Analysis a subsequent zoom
does not show a right scroll bar. The work-around is to
either alter the semblance within the menu, or zoom first
to get a scrollbar, then change the semblance width with
Object Visibility. (515427)
There is a limit of 19 horizons that can be displayed in
Velocity Analysis. (514304)
Solaris Only: Using the Snap Once option pulls all the
picks up, and multiple uses of this option continues to
pull picks to the top of the semblance tile. (130464)
Setting "stretch mute = 0.0" to disable is really
equivalent to setting it to 1000% rather than totally
allowing stretch to "zero time" as is the case in our
current NMO module. (148528)
Velocity Analysis Precompute
This module will fail if the number of semblance velocity
functions is greater than the maximum fold set in the
SuperGather formation menu. The work-around is to
increase the value for fold in the menu. (513120)
When running Velocity Analysis after precompute, the
semblance display will appear compressed in time if the
flow has menus from versions older than 1998.6.
(513579)
Velocity Manipulation
Smoothing a velocity table may drop the functions at the
first and last CDPs. The work around is to input the
smoothed table back into Velocity Manipulation and
explicitly define the output range. (514444)
Other Docs
Known Problems
Velocity Viewer/Point Editor*

If you specify a beginning and end time to edit, the
velocity displayed will honor those constraints. However,
editing a velocity function creates a function which
starts at zero time. Similarly, using this process to
convert to a different type of velocity file outputs a field
for the entire time range of the data. You should QC the
output velocity files prior to using in subsequent
applications. (502497)
The velocity field smoothing option introduces a
discontinuity at the bottom the velocity field. This
discontinuity happens at about one-half of the temporal
operator up from the bottom. The work-around is to
perform this smoothing in Velocity Manipulation or
Volume Viewer Editor, or using the menu parameters
specify the depth/time is greater than it really is.
(511538)
Volume Viewer/Editor
Select Yes to Display Gather Locations in 2D event.
even though the helpfile indicates this must be a 3D only
function. If this is not done, turning on the Volume
Viewer/Editor PD icon will not activate the MB1 Send
Trace Location icon. (504963)
It has been shown that adding horizons adds to the
program allocated memory size, but removing those
horizons does not decrease the allocated size. The
program then allocates more memory if horizons,
including those just removed, are added. (507431)
In 2D, the mouse button help for Smoothing and
Gridding is confusing. It should read Number of CDPs
and Time in Msec. (507989)
Specifying surface coordinates of xy and trying to
smooth using edit-grid/smooth volume generates the
same velocity for all inlines and crosslines (infinitely
smooths in the spatial domain). The work-around is to
specify ILN/XLN as surface coordinates and smooth
based on inlines and crosslines. (510876)
The map view display sent to a different machine does
not show the gather locations. If the map view display is
sent to the same machine where ProMAX is running, the
gather locations display properly. (510439)
Other Docs
Known Problems
It is possible that by using the defaults presented in the

gridding/smoothing spreadsheet, ProMAX will generate
a table with negative CDP values. This will cause
modules such as Kirchoff Time Migration to fail with a
Signal 11 error. The work-around is to input realistic values
in the spreadsheet. (512026)
Attempting to limit the 3D volume by ILN:XLN may
generate an error like this:
Fatal error occurred on 21-Oct-99 at 08:51:01Message is: User depth
coordinate limits are invalid.
The cause has not yet been determined. (512176)

Using the option to Save as - Other Horizon does not
work. The work-around is to output the horizon as an
interpreted horizon. Then export to ASCII and import the
ASCII file as an Other Horizon. Perform the following
steps. (512748)
1. Output Horizon as an interpreted horizon
(.IHT OR.IHD)
2. Export your interpreted horizon file to ascii.
3. Create a new Other Horizon file using CDP for
primary key.
4. Import the ASCII file you exported
When you use CREATE to make a default table, values
for NULL are 0.0 and 1000.0. Should be 1, otherwise
when used in VVE module crashes with following error:
(507752)
Warning occurred Message is:
Unexpected Z description, TIME. Changing to TimeAssertion failed: jy>=0,
file /seg/71/advance/port/src/lib/agfc/tb3.c, line 447
The next sub-flow will not be executed due to errors Abnormal termination
(/ProMAX/sys/exe mainWin.exe) Signal = 6 (Core file generated)
Display is inverted when layer continuation has only one

point. E.g. When you are picking horizons and creating a
model in pieces you may have only one point on a
horizon that makes it from the first set of CDPs you
created the model for to the next one. If that is the case,
Other Docs
Known Problems
the velocity field and background data flip upside down

when you open the horizon. (513281)
The vertical crosshair always stays on the first CDP
location no matter which CDP Velocity Analysis is on
when interacting with Volume Viewer/Editor. (125538)
Horizons must extend beyond a single inline to be
visible. (128156)
Problems have been reported in the Volume Viewer
Editor when geometries are created with initial
coordinates of X=0, Y=0. The work-around is to bias
these values by some non-zero value. (134308).
Horizons picked using this module will not be visible
using either Trace Display or Velocity Analysis. (134864)
You can read in an interpreted horizon (IHT) and tell VVE
to save it as an Other Horizon (HOR) but it will not show
up in the HOR table. This works for 2d but not 3D.
(147960)
Well Log Input
The program and documentation allow for a dump of the
LIS and LAS formats by specifying file number zero in
the menu. The menu does not allow for input of file
number zero. This can be fixed by changing the
type_desc descriptor for the FILENUM parameter in the
log_read.menu file from: type_desc: (int: 3 1 999) to:
type_desc: (int: 3 0 999) (504490)
Currently for this process to read Version 2.0 LAS
Standard logs, the Start, Stop and Step lines should not
include spaces between the descriptor and the units of
measurement. (504968) For example, a file coded as
STRT .FT
xxxx.xxxx:START DEPTH
should be modified to
STRT.FT
xxxx.xxxx:START DEPTH
This module does not handle LAS version 2 files where

the lines are wrapped. The work-around is to edit the
files so that each depth step and its mnemonics are one
continuous line i.e. unwrapped. (512622)
Although the LAS specifications only require a ~ (tilde)
and the first letter of the section to identify it ProMAX
Other Docs
Known Problems
requires the full description. E.G. ~VERSION

INFORMATION rather than simply ~V. (600569)
For more info about LAS specifications, check
http://www.cwls.org/las_info.htm
Due to changes made in the LAS format from version 1.2
to 2.0 certain fields such as units and well name will not
read properly. (147324)
Well Log Synthetic Match Filter
The match filter can fail or output a dead filter trace if
the MB3 stretch/squeeze option is used on samples
located above the anchor after using MB1 to move
locations. (503563)
Western 4 Input
An option to read variable length records is available for
disk files. A similar option is not available for tape
datasets. The process can fail with an error similar to the
following: (504109)
I am lost, attempting to synchronize, Record: x Trace: y
Using the menu to override the reel header for trace

header length causes a signal 11 error. (511945)
XY Graph
The menu allows inputting negative numbers in the bin
distance (dx and dy), and will initiate a graph with a bin
space. The application will core dump when attempting
to manipulate this grid. Do not input negative bin sizes,
you should utilize the origin and azimuth values
appropriately to position the binning grid. (501378)
This process can fail with the error: Cannot retrieve data or
with an error in the UNIX window related to.../agC/Arra.c if a
database with all NULL shot station values is
encountered. (502973)
The alternate domain plot does not work if midpoints
have not been assigned. (502498)
Lines which are due North-South or East-West can
spawn a display interface in which the display scale is
created in minute increments, leading to apparent
display problems. Adding a small amount to one of the
Other Docs
Known Problems
relevant X or Y coordinates will circumvent this problem.

(503700)
After importing
$PROMAX_HOME/port/misc/misc_files/3d/marine_unkooa and
creating a basemap, and highlighting the contributors to
the trace domain: Select all (MB2) occasionally blows
away the XYGraph. (507378)
ProMAX VSP Problems

3-Component Hodogram Analysis
The program assumes that the maximum value in a gate
is a peak. If the maximum is a trough and you have
picked on a peak, the output will be 180 degrees off.
(503259)
When VSP data is sent through this process, 5 traces are
output for each 3 traces input, or for each VSP FFID. All
output traces are present except for the last trace of the
last FFID. (506969)
work-around: Create a dataset with an extra FFID.
Hodogram Analysis
If the input windowed sample values are less than +/1.0, the horizontal axis is scaled to +/- 1.0. The vertical
axis scales correctly to the input samples. You can
rezoom the window, or more effectively, use a scaler in
Trace Math going into the analysis tool to set the input
amplitudes larger. (504429)
The labels H1,H2 in the upper right corner of the display
are the opposite of what they should be. (508717)
Users have reported this module generating theta and
phi polarization angles that make no sense. It is
suggested users check the output listing closely for
angles that are too large. (513376)
VSP Report
Attempting to generate more than 7 reports causes
formatting problems on the output. (515024)
This module fails with a segmentation fault in version
2003.0 (516114)
Other Docs
Known Problems
VSP/CDP Transform
The program uses all the shot and receiver X,Y
coordinates to compute a slope and intercept of a line.
The transformed data will be imaged along this line in
map view. If there are duplicate shot and receiver
coordinates, an improper line gets computed, and the
job may possibly fail. (505491)
This module may generate spikes if the datum is below
the source elevation(513565)
VSP Geometry Spreadsheet
VSP Geometry Spreadsheet
The values in the X and Y columns are destroyed when
Station column is filled. It is not required to fill in this
column. (507633)
Vel Table From VSP
Although the option is given in the menu to limit the
offsets used to compute the velocities, this range is not
being used. (507635)
ProMAX MVA Problems

CRP Gather Raytracing*
Ray tracing files cannot span disks correctly, resulting in
errors such as:
Unix error - no such file or directory
Error opening file: .../xxxxxxxxTRHD
Could not open table xxxxxxxxTRHD
work-arounds: There are 3 possible work-arounds: 1) In a

UNIX window physically move the file to a secondary
disk that has free space and rerun the raytracing. 2)
Rerun raytracing outputting the file onto the primary
disk. 3) Output to primary and then physically move the
file to a secondary disk with free space available, and
create a link from the primary to the secondary location.
(504847)
Other Docs
Known Problems
Extract 2D Table from 3D

When you select Stacking Velocity for input this module
will also generate an inaccurate interval velocity in depth
table. (513138)
When running jobs from the Flow Chart you will get an
error stating that super_exec.exe is not found. The workaround is to either make a link or simply copy superExec
to super_exec.exe in the $PROMAX_HOME/sys/exe
directory. (303744)
Horizon Manipulation
You are unable convert Other Horizons to depth in
ProMAX MVA. There are format discrepancies between
SeisWorks Horizon Input and Horizon Manipulation.
Program errors with (507521):
Horizons can have only 1 Y value! Is this a proper horizon?
work-around: Run VVE and convert from Other Horizon to

Interpreted Horizon in Time (IHT).
If you use the option to decimate horizons this module
will either fail with an error or complete normally
outputting the same number of points as the input
horizon. (511598)
The workflow to bring in 3D SeisWorks horizons and
then add them together using Horizon Manipulation
doesnt work at present. The work-around is to add the 2
horizons in SeisWorks 1st (using horizon computations)
and then bring in the new horizon to ProMAX. (305310)
Interactive Horizon RMO Analysis*
If an RMO pick is made after zooming the display, the
associated colors or seismic traces can be severely
distorted. The problem can be rectified by scrolling out
and then back into the analysis area. (503345)
Saving RMO picks in IHVA through the pull down menu
does not give the same results as using the Save icon
(floppy disk picture). When you bring up both IHVA and
the MVA Xsection Window, send a horizon to IHVA,
pick RMO, save using the pull down menu, and then
proceed to send the next horizon to IHVA, a popup
appears saying the picks are not saved. When the save
icon is used the popup does not appear when the next
Other Docs
Known Problems
horizon is sent to IHVA. In either case, the RMO picks

are actually saved. To save time, we recommend using
the Save icon. (503959)
IHVA automatic picker will not pick across gaps in a 2D
line. This causes tomographic inversion to produce
interval velocities with NAN values from the beginning
time to the time of the last horizon. The work-around is
to either create horizons on each side of the gap, or
manually pick velocities across the gap. (510145)
If you are picking RMO in IHVA on a zoomed window,
when you make a pick the time horizon is not plotted
correctly and the time picks are no longer on the
horizon. If you iconify the plot and re-display, the plot
will be correct. (512537)
Interactive Horizon RMO
This module is not displaying interpolated picks
properly. (144411)
MVA Flow Chart*
The dialog box for selecting tables or datasets does not
let you create new names. To create a new name, you
should return to the general ProMAX interface. (503437)
The Flow Chart UI contains the correct template for the
Velocity Analysis Precompute. However, the Velocity
Analysis Precompute menu in the MVA flow builder
itself contains a link to an incorrect process. The
Processes.list file in the $PROMAX_HOME/port/menu
directory should be modified, substituting vaprecom for
the existing vabatch. (506089)
SGI Only: You cannot exit the flowchart. The parmdb
process continues to run and may try to use 100% of a
CPU. You must kill the flow from the Notification window
or kill the process from the UNIX shell. (507165)
MVA Tomography Inversion*
After coding the menu to accept more than one horizon,
reentering the menu may result in the number of
horizons being reset to 1. (503402)
Other Docs
Known Problems
MVA Xsection Window*

When you run MVA Xsection Window in time, display
individual time horizons, and save them to a Horizon
Group, a Depth Horizon Group table (HGP) is created
rather than a Time Horizon Group table (HGT). The
work-around is to rename or copy the HGP file to an
HGT file. (503727)
IRIX ONLY: This module may fail with some versions of
IRIX. E.g fails on IRIX 6.5.6 and 6.5.10 but not 6.5.1.
(514262)
ProMAX 3D PSDM Problems

3D Travel Time Generator
Travel time generation can fail if the associated disks are
filled by other jobs before the TT files have time to span
to another disk. You can try lowering the size of the TT
files by setting the environment variable TT_FILESIZE =
nnn (nnn = number of mbytes). Or setting the
environment variable TT_ZERODISK = y will actually
grab the required disk space prior to execution. (504757)
The User Interface crashes when this menu is selected.
Contact support@lgc.com for a new menu. (516300)
Will not allocate more than 2 GBytes of memory. Contact
Will not allocate more than 2 GBytes of memory. Contact
The output may be all noise if the job is run in Volume
mode and the aperture in the TT Generator is set to
some small part of the survey. The work-around is to set
the grid definition to the whole survey. (137855)
There is an option in the menu to "Output Random line
Travel Times". If you say Yes the menu asks for a point
file. There is no mention of this line in the docs and
there is no information on what a point file is supposed
to contain. The solution is to create a simple ASCII file.
The first line is the number of points (n, which define the
random line), followed by n lines with the IL and XL
positions of the node. (143187)
n
Other Docs
Known Problems
IL1 XL1
IL2 XL2
Software Development Problems

SDK Documentation
2 character module names are not processed in exec
tools_to_delete file. You may however, manually
comment it out of the generated toolcall.f file. (512086)
Make System
IRIX Only: Attempting to link a module will generate an
Un-resolved text symbol error. (147596)
Work-Around:
cd $PROMAX_HOME/sys/lib64
ln -s ./libCio.so.1 ./libCio.so
ProMANAGER Problems
Proloop is not interpreting the & in Disk Data Input
from another line. When passed "area & line & dataset",
proloop is supposed to translate this to populate the
pop-choose for area, line, and dataset in a Disk Data
Input menu reading a dataset from another line.
Currently, it is passing the input string verbatim. The
original character was a pipe |, but this was changed to
a & to accommodate peculiarities of MsAccess. The pipe
still works, but the & doesnt. (509963)
Submitted flows fail to honor product paths in .promax.
The 1998.6 version of ProManager does not use multiple
search paths from a users .promax file during job
submission. (512935)
work-around: Functionally equivalent to defining paths
in a PROMAX_DOT_PROMAX_HOME or
$HOME/.promax file can be arranged by setting any or
all of: PROMAX_SYS_EXE_HOME,
PROMAX_PORT_MENU_HOME,
PROMAX_PORT_HELP_HOME,
PROMAX_PORT_MISC_HOME in the ProManager job
submission environment. These variables will need to be
added to the environment catalog first.
Other Docs
Known Problems
Problems parameterizing multi-level menus like Create

CGM Plotfile. Menus within menus cannot be
parameterized from ProManager in one pass. Some
menu options which are complicated pop-ups or which
call programs directly will not work at all. (509880)
Partial work-around: From the ProMAX UI, edit the
template, open the submenu for which substitution is
needed and save the template. Then select for
substitution in ProManager the template table. Edit the
template again in ProMAX UI and save with a different
submenu open, re-access in the ProManager UI.
Expression parsing error. Using Template or Replicate
tables in ProManager to read a dataset from another
area/line/ can produce a parsing error. This can happen
when the parser does not parse concatenated variables
correctly. (513166)
For example where replica.Name is a string and
replica.Seq is an integer:
replica.Name+replica.Seq = myName+1 (incorrect)
replica.Name+replica.Seq = myName1 (correct)
work-around: Include adding a field to the replica table

and using the String fill tool.
Another suggestion would be to avoid these types of
names. You could do the following
replica.Name+ "_" +replica.Seq = myName_1
Environment: $HOME cannot be added to environment.

The ProManager User Guide says that for Solaris it is
necessary to add the variable $HOME to the
environment in ProManager (that is the [Env] icon in the
left toolbar). This is not possible. (513167)
The aar_promax and ProManager do not communicate
correctly using LP Queues (AIX). The aar_promax and
owner.jar do not correctly set the USER environment
variable needed by scripts called in their respective
remote environments. (513145)
If the file .promax.proloop does not exist as directed by
PROMAX_DOT_PROMAX_HOME, you cannot start the
ProMAX UI from ProManager. A simple touch
.promax.proloop solves the problem. (512141)
Other Docs
Known Problems
The job status option to display available disk space

does not report the available space in
PROMAX_SCRATCH_HOME. (513585)
The auto-QC and auto-submit features will be disabled
on AIX for ProManager 2003.0. This has been noted in
the documentation. (514273)
The version of MySQL distributed with ProMAX 1998.6
may not install on some IRIX 32 bit systems. (303592)
Linux Only: User cannot kill a job from the ProManager
interface. The error message is: /usr/bin/kill not found
(516203)
Solaris Elite and Creator 3D Graphics only: The
ProMAX explorer window is not refreshing properly when
you use the scroll bar. (304799)
Linux Only: Chaining of flows does not work. Only the
flow executes. (516192)
IRIX Only: Set Home option does not work. (126721)
If a chained flow has been built or executed before, it
ignores the host, environment, and queue you specified
for the flow you run before the chained flow. It instead
runs in the environment specified for the previous
execution of that flow. Work-around: Rebuild the flow
using the host, and environment, and queue you wish to
run in when the chained flow is executed. (139274)
If you have a template and you copy and rename the
template within the same area and use the new renamed
template to build a flow, the flow that is built in ProMAX
has the original template name not the new name. This
doesnt happen if you copy from one area to another,
only within an area. (305473)
ProManager will allow the creation of duplicate Area and
Line names, even though ProMAX will not. (145235)
LINUX Only: Flow chaining does not work. (146786)
Total Tape Solution

When mounting the wrong VSN for a catalog, the
labelled tape mount request does not post error message
to (re)mount. (509299)
If you mount again the following message will appear in
Other Docs
Known Problems
the job.output:
Expected VSN and the observed VSN read from the input volume do not
match.
This error condition has no override option.
Delete tape dataset ALWAYS prompts for catalog DSN

deletion when deleting from the Area or Line level, even if
the dataset is a non-catalog dataset. (513058)
Writing to an external VSN but mounting an internal
(catalog) SL tape may result in a tape overwrite. (508654)
This could happen if an attempt is made to write to an
external VSN list and the wrong labeled tape is mounted.
This tape happens to be a library tape and it was
overwritten when the operator chose to override the
error. Upon review of the code, this is possible ONLY if:
1) The bypass label processing switch is set.
2) The bypass vsn processing switch is set.
3) And the PROMAX_TOPCAT_HOME environment
variable is not set or is set incorrectly.
work-around: The possibility of this happening may be
avoided by setting the configuration flag: AEEJ
Modifying TopCat attribute MPOOLNAM does not add
additional volumes to the media pool. (510442)
Java.config from Solaris REMHOME install has incorrect
port (SOLARIS). (513309)
When running a remote tape job to a Solaris machine,
the user gets the following error message:
RUNTIME NOTE: FAILED SOCKET RECIEVE ON HOST:[sparky.
TapeNotificationClient: Exception = Connection refused to host:
[cruiser:1111];
nested exception is:
java.net.ConnectException: Connection refused
work-around: The $REMHOME/etc/java.config uses a port of 1111

for Opcon, this should be 1099 by default.
Convert_device.txt2tts script is setting REMHOME
improperly. When converting an existing device.txt that
has and fclient.exe stanza to be converted to a
REMHOME, a sys/exe/ will be appended to the
Other Docs
Known Problems
REMHOME path. You will want to delete this from your

new device.tts. The REMHOME setting is similar to a
PROMAX_HOME setting which does not include a
sys/exe in the path. (513332)
Config_file explanation for device.tts line is unclear.
When editing the device file stanza in the
PROMAX_HOME/etc/config_file, either your HOME
directory or PROMAX_HOME/etc will be prepended to
your device file name. Typing an explicit path will not
work. (513331)
DEVICE.TTS: If the hostname entered in the device.tts
file does not match the results from the command
uname -n ProMAX will return an error:
Unable to make socket connection between client and ProMAX
This is most often caused when fully qualified

hostnames are used. (513479)
In the TTS online Documentation Basic Configuration
section, the description for TMHOST is
TMHOST="terminal:0.0" This is the location to display
the mount messages issued for this device. If this is not
supplied, mount message are sent to the location of the
User Interface where the job was submitted. If a user is
using a remote tape drive, the default mount location
only works if the DISPLAY environment variable is set to
hostname:0.0 If this variable is left to the default of
:0.0, the mount message actually goes to the machine
with the tape drive attached. (513523)
SGI ONLY: The REMOTE_TAPE_HOME /port/bin/
scripts for TAPE_REQUEST and TAPE_NOTIFICATION
look for hostname and rsh under /bin rather than
/usr/bsd/hostname and /usr/bsd/rsh which is
standard on most SGI installs. The work-around is to
edit these scripts to match the correct paths on your
system. (513363)
Remote Tape AIX only: In the case where the remote tape
device is attached to an AIX system that does not
contain a full ProMAX installation you may get the
following error message when trying to access the device:
ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM
Other Docs
Known Problems
We believe this is due to a library missing from the

remote tape distribution The work-around is to do a full
ProMAX AIX install or at least the ../sys/lib directory.
(303623)
ShowCat: The documentation does not explain that in
order to run this program $PROMAX_HOME/port/bin
and $PROMAX_HOME/sys/bin must be in the users
search path. Otherwise users will get an error saying
promaxpath not found. (513506)
not being honored. Use NREW + NUNL to bypass the
rewind and eject behavior. (514411,515409)
SGI Only: The "Process Killed" message is NOT coming
to the Opcon Tape Notification window when user kills a
job from the ProMAX UI "Notification Window". (136556)
When a user cancels a job from the ProMAX UI, the
Process Killed message does not show up in opcon. The
work-around is to notification and tape request files.
(145230)
Add "export THREADS_FLAG=native" to both the following files:
$PROMAX_HOME/port/bin/TAPE_NOTIFICATION
$PROMAX_HOME/port/bin/TAPE_REQUEST
AIX Only: The proclient binary distributed in the tar-file
under $PROMAX_HOME/port/misc/remote_tape. Does
not work. Contact support@lgc.com for the correct
version
the DEVICES file.
Other Docs
Known Problems

LandMark Known Problems

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LandMark Known Problems

Caricato da

Copyright:

Formati disponibili

Known Problems List1

ProMAX System Administration

Known Problems List

No link to a known problem found for this process.

ProMAX 2003.3.2 Known Problems Jan. 1, 20032

ProMAX System Administration

ProMAX 2003.3.2 Known Problems Jan. 1, 2003

ProMAX 2003.3.2 Known Problems Jan. 1, 20033

ProMAX System Administration

Recently Discovered Problems

Within the geometry spreadsheets and database, integer

ProMAX 2003.3.2 Known Problems Jan. 1, 20034

ProMAX System Administration

Analysis can suffer degraded performance if data is

ProMAX 2003.3.2 Known Problems Jan. 1, 20035

ProMAX System Administration

line at the bottom of this file:

Where "fb0" would denote the first monitor and "fb1"

Log off and then back on system to restart Xserver.

ProMAX 2003.3.2 Known Problems Jan. 1, 20036

ProMAX System Administration

is not possible there is a work-around. In addition to the

The work-around is to edit the ProClient script:

NQS Queues: In the script

ProMAX 2003.3.2 Known Problems Jan. 1, 20037

ProMAX System Administration

Solaris Only: Boot scripts that are K-Shell (/bin/ksh)

ProMAX 2003.3.2 Known Problems Jan. 1, 20038

ProMAX System Administration

2D: Static column: you cannot interpolate statics in

ProMAX 2003.3.2 Known Problems Jan. 1, 20039

ProMAX System Administration

The 2D Land Geometry Spreadsheet option to bin using

ProMAX 2003.3.2 Known Problems Jan. 1, 200310

ProMAX System Administration

calculate unique channels for each shot. However, you

ProMAX 2003.3.2 Known Problems Jan. 1, 200311

ProMAX System Administration

When importing a UKOOA file with negative northings,

Deleting a shot from the sources spreadsheet will cause

ProMAX 2003.3.2 Known Problems Jan. 1, 200312

ProMAX System Administration

The documentation states that if you are entering

work-around: Fill out Number of inlines and Number of

ProMAX 2003.3.2 Known Problems Jan. 1, 200313

ProMAX System Administration

a negative bin dimension) can generate X and Y values

ProMAX 2003.3.2 Known Problems Jan. 1, 200314

ProMAX System Administration

will halt. (293557)

ProMAX 2003.3.2 Known Problems Jan. 1, 200315

ProMAX System Administration

Amoco SIS Input

The work-around is to use Trace Length to pad the trace.

ProMAX 2003.3.2 Known Problems Jan. 1, 200316

ProMAX System Administration

around is to eliminate these traces or change the trace

ProMAX 2003.3.2 Known Problems Jan. 1, 200317

ProMAX System Administration

Setting Label Plots with AVO_ATTR to yes does not give

Build Unisec Parmfile

work-around: Make your plot fit the paper. (505023)

ProMAX 2003.3.2 Known Problems Jan. 1, 200318