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 problemfor this process is listed in this document.

If you are accessing this document via Other Docs: KnownProblems, please page down to review the Known Problemslist for other processes.

This file is updated monthly and placed on our ftp server forretrieval on an ongoing basis. For information on how todownload the most recent copy of the Known Problems listplease refer to Downloading and Uploading Files with FTPin the Accessing the Internet as a Resource chapter of theSystem Administration guide.

Other Docs Known Problems

ProMAX 2003.3.2 Known Problems Jan. 1, 20032 ProMAX System Administration

ProMAX 2003.3.2 Known Problems Jan. 1, 2003

When you click the Known Problems icon in your onlinedocumentation, it will take you to an entry in this listing ifthere is a corresponding known problem. If there is not acorresponding problem, you are taken to the start of this file.

The number following the description of a problem is used asa reference ID. It is used when contacting the technicalsupport group for additional information regarding the statusof the problem. This file is organized as follows:

• Recently Discovered Problems lists problems foundafter this listing. This list includes problems for allProMAX products. Each recently discovered problem willalso be repeated in the appropriate category below.

• ProMAX 2D/3D Problems contains an alphabeticallisting of all problems associated with ProMAX 2D and3D.

• ProMAX VSP Problems contains an alphabetical listingof all problems specific to ProMAX VSP.

• ProMAX MVA Problems contains an alphabetical listingof all problems specific to ProMAX MVA.

• ProMAX 3D PSDM Problems contains an alphabeticallisting of all problems specific to ProMAX 3DPSDM.

• Software Development Problems

• FrameViewer Problems contains a list of problemsspecific to the Frame Viewer software used to display theProMAX helpfiles.

• ProManager Problems contains a listing of problemsspecific to the ProManager flow replication tools. Thisincludes MySQL problems.

• Total Tape Solution Problems contains a list ofproblems associated withTTS,OPCON,ShowCat,device.tts and resource databaseproblems.



Recently Discovered Problems

ProMAX 2D/3D Problems

General ProMAX

• Database attributes can be lost if you run concurrentjobs that add new attributes to the same OrderedParameter File (OPF) in a database file. If this occurs,you can get a partial recovery by restoring the OPF indexfile from your backup media. (502707)

• Database attributes can be lost if you access an OPF filewhich spans filesystems, but the active config_file doesnot contain the appropriate OPF flag for the requiredfilesystems. (501718)

• Parameter tables defined with integer values for sortkeys larger than plus or minus 2**23 (8388608) may failwith an error such as:

Unable to find SIN given FFID xxxxxxxx

Within the geometry spreadsheets and database, integerattributes can be entered with a precision up to plus orminus 2**31, and trace headers are loaded correctlyduring Inline Geometry Header Load. However,parameter table access on those keys using the largervalues will fail due to truncation problems.

work-around: Repick or recreate the parameter tablebased 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 themenu can fail with memory errors upon execution. Atypical limit for ASCII strings is 50 kbytes. (502573)

• Parameter Table Editor: When selecting a parametertable which allows for multiple time gates, select allgates in increasing order. However, if time gates areselected out of order, you can export and then reimportthe columns in the correct order using the parametertable editor. For example, after you have added a gateduring a subsequent interactive session. (504247)

• Display tools memory use: Interactive Data Access,Trace Display, Interactive Spectral Analysis, and FK



Analysis can suffer degraded performance if data isviewed outside ensemble boundaries. These problemsinclude: increased usage of memory, CPU, and wall clocktime as additional traces are processed within a singleflow. The problem is most apparent when passing a largenumber of traces through Trace Display, and not usingthe default value of 0 for Number of traces to displayper screen. Exit the flow to clear the CPU usage. You areencouraged to maintain input ensemble boundarieswhere possible when using these display tools. (505892)

• Display Tools: When using Exit/Stop in any of the inter-active display tools, the numeric files in the flow direc-tory are not automatically deleted. It is best to useExit/Continue flow. (506109)

• Licensing: The user interface may crash if you try toswitch to the VSP product and do not have a valid VSPlicense. (514918)

• Problem: Tape mount dialog window pops-up but youcannot see the text. The solution is to add entries likethese to each users .Xdefaults file.

ProMAX Tape*background: MistyRoseProMAX Tape*foreground: sienna4

• Displaying on a dual monitor Solaris system, whilerunning on an IBM may fail with the error:

X Error of failed request: BadWindow (invalid Windowparameter)

work-arounds:Option 1: use Exceed to log into your AIX machine andrun display jobs.

Option 2: Change your dual monitor to a single monitordisplay. On a dual-headed (2 monitor) Solaris systemone of the heads can be disable via editing

/etc/dt/config/Xservers file.

NOTE*** You DO NOT edit the /usr/dt/config/Xserversfile but instead copy it to /etc/dt/config and edit thatone.

A typical dual-headed system would have the following



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 tobe 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 inthe config_file as "big" and PROMAX_LITTLE_ENDIAN isset to true in the start up script. Result: The job runsand the data is output as big-endian (it doesn’t considerthe value that is set in the start up script,) It doesn’t dowhat it says in the config_file about the user being ableto override the default for a particular job by settingeither PROMAX_BIG_ENDIAN orPROMAX_LITTLE_ENDIAN in the environment. (516151)

• Linux Only: When ProMAX gets the endian order fromthe config_file it doesn’t report in the job.output whichendian 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 itsprocesses. To kill a series of queued jobs, be sure to killwaiting jobs before any active ones, or waiting jobs willbecome 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 difficultiessetting up lp queues on some IRIX systems. Werecommend using NQS queues instead, however if that



is not possible there is a work-around. In addition to thesteps described in the System Admin. Manual do thefollowing. (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 inorder to run this program $PROMAX_HOME/port/binand $PROMAX_HOME/sys/bin must be in the userssearch path. Otherwise users will get an error sayingpromaxpath not found. (513506)

Tape Devices: ProClient script does not run on 32 bitIRIX Systems. Attempting to access a tape device on oneof these systems will generate this error (513567):

ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM. Possiblestart-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 yourcorrect $PROMAX_HOME. (515371)

• NQS Queues: To avoid potential problems users shouldset the umask to 000 in their.cshrc files. (515646)



• Solaris Only: Boot scripts that are K-Shell (/bin/ksh)will not run during the boot process. inet.d will only runscripts that are/bin/sh. The script startrmi is anexample of one that cannot be used “as is”. The work-around is to make the syntax within the script conformto /bin/sh standards. (515494) EG:

PROMAX_HOME=/xx/yyexport PROMAX_HOME

• Linux Only: The 2003.3 documentation regardingsetting up Linux lp queues is not complete. Pleasedownload the file queue_setup.pdf from the Landmarkftp site. (516214)

product/ProMAX/v2003.0/port/help/rel_notes

• LINUX Only: The TTS TAPE_REQUEST is notcommunicating with opcon. ProMAX hangs with a taperequest to opcon. (127983)

• Linux Only: The documentation for setting up Linuxstinit.def file. Please download the file quick.pdf from theLandmark 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 8characters causes additional characters to append toname causing jobs to fail with error message: (148604)

FATAL TAPE SYSTEM RUNTIME ERROR:A matching logical device name: [LOCAL8MMX] was not found inthe 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 greaterthan plus or minus one into the Pattern spreadsheet. Ifrequired, receivers can be renumbered to avoidsubsequent pattern exit or binning problems. (504078)



• 2D: Static column: you cannot interpolate statics ineither 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 availablefor some, but not all stations, they are written in thestatic column, but the entries between the actual staticswill still be 0. This makes it impossible to interpolatebetween these values.

work-arounds:

1. Import Geometry file into spreadsheet, importing staticsinto the elevation column.

2. Interpolate using step 1.

3. Export geometry file into an ASCII file.

4. Import geometry file into spreadsheet, importing staticsinto the static column. (507313)

• Skid and Offset information may be lost if the geometryis being built by assigning midpoints based on existingindex numbers in the TRC and the spreadsheet is sorted.This occurs because of the re-mapping in the TRCdomain. This problem can be avoided by sorting beforeentering skid and offset information. (507707)

• The SPS Import option ignores any uphole informationin the SPS file. Upholes must be entered manually.(507758)

• Importing into the spreadsheet only matches by Stationnot by Line and Station. This could cause uphole timesand hole depth to be assigned incorrectly. (512105)

• The option to delimit while importing a UKOOA file doesnot work. (303275)

• Offset header is not being loaded correctly. Azimuth inthe Trace QC is correct; source and receiver locationsare correct, but the offset sign is wrong on the neartrace. (129292)

• In the binning menu ProMAX allows you to enter morethan two values to the right of the decimal point. If youbin at this point these are the values that will be used.However if you save and re-enter this menu the valuesare rounded off to two digits. To get the greater accuracyyou must re-type in the true number. (276579)



• The 2D Land Geometry Spreadsheet option to bin usingexisting CDP numbering and coordinate values isredoing the values:

TRC GEOMETRY CDP_XTRC GEOMETRY CDP_YCDP GEOMETRY CDP_XCDP GEOMETRY CDP_Y

The work-around is to use Database/Header Transfer toput the CDP_X and CDP_Y trace header values into theTRC and CDP database manually, then use just theFinalize Database option of the 2D Land GeometrySpreadsheet, do not bin. (134913)

• Currently the import of SPS is only partially compliantwith the documented standards. In the relational file,column 47 is identified as the "channel increment",which we import directly to the pattern spreadsheet asthe channel increment. However, the standards allowthis value to optionally represent the number ofsequentially numbered channels at a given receiverstation. There is no means of distinguishing which ofthese two modes to honor. The work-around via an awkscript to modify the relational file to explicitly include allchannel groups. (516639)

• AIX ONLY: The “Cross Domain” icon does not work inXYGraph. (144466)

Test

2D/3D Marine Geometry Spreadsheet*


• 3D: UKOOA import does not honor cable entry and willrenumber channels if necessary. Our example problemis a 3D marine geometry with 6 streamers, identified bythe last column in a UKOOA file, and the channelnumbers decrease from 240-1 on each streamer. TheImport definition defines a column for the cable but doesnot populate column. The Import apply/append menuoffers an option to renumber channels, but it starts fromx and numbers to x+1. Decreasing channels or cablesout of order will not tie to correct data channels.

work-around 1: You can edit the TRC with DBTools to



calculate unique channels for each shot. However, youmust make a series of edits. This works, but is hugelytime-consuming for a 100MM trace database.

work-around 2: We can provide an awk script thatmanipulates the UKOOA file before import. Call supportfor script. (507355)

• 3D: Multiple streamer patterns with different number ofchannels are not currently allowed in the spreadsheet. Ifrequired, the channels must be renumbered to acommon channel numbering scheme. (502371)

• 2D: If a marine geometry is defined with receivers aheadof the source, such as in a dual boat configuration, thesign of the offset is not calculated correctly. The sign ofthe offsets is created as if the cable is trailing the source.All other entries, such as Absolute offset, X/Y andAzimuth are correct. If a signed offset is required for anypurpose, use Trace Header Math to set the signed offsetappropriately. (503508)

• 2D: The Setup dialog box indicates station intervalparameters are optional. For the Auto 2D options, theseparameters must be entered. Failure to do so can resultin incorrect geometry patterns. (505103)

• 2D: In Auto 2D, if the channel increment is -2, the farchannel is eliminated.

work-around: Define one more channel than is needed.(507049)

• 2D: You must specify the Sail Line Azimuth entryunder Setup in 2D Marine Geometry even though themenu says, “Optional”. If you do not make this entry, thedefault Azimuth of 1 is used, This can cause CDP folderrors due to “round off” errors. The fold can be doubledwhen the azimuth is not specified. (507330)

• 2D: The 2D Marine Spreadsheet does not honor multiplepatterns for cables and will cause the job to fail.(507311)

• When importing navigation data, there is an option inthe “UKOOA receiver column definition” window thatallows an attribute to have math applied. Multiplying by0.0 has no effect. (507641)



• When importing a UKOOA file with negative northings,trace coordinates are imported correctly, but shots areread as positive coordinates. work-around is to multiplythe column in Source spreadsheet by -1. (504235)

• The SIN spreadsheet column values for QC Dist and QCOffset may be switched depending on the specifiedstreamer azimuths. Values such as 0, 90, 180, 270, and360 are OK, but all other values switch these twocolumns. (507760)

• The SOURCE ID column in a standard UKOOA 90 file isnot being transferred to the SOURCE column in thesources spreadsheet. The work-around is to use aneditor or the grep command to create a separate filecontaining the ‘S’ Lines from the UKOOA file. Thenimport these via the ASCII Import option. (508657)

• If you start a 2D Land Geometry Spreadsheet in a 2DMarine Line, you will get cdp_x and cdp_y in your TRCdatabase even though they do not belong there. (Theyare not there if you start a new line with 2D Marine). Ifyou copy a 2D land line to a new line and use it for a 2Dmarine line, the cdp_x and cdp_y values in the TRC OPFwill remain in the TRC unchanged from the previous lineafter the 2D Marine geometry finishes. These valuesshould have no affect on subsequent processing.(512220)

• When performing UKOOA Import and trying to change"Record ID" characters user is crashed out of importwindows with following error: (513404)

Error: Attempt to unmanage a child when parent is not Composite

• Deleting a shot from the sources spreadsheet will causeCDP binning to fail. The work around is to leave badshots in the spreadsheet and set the FFID to zero. Thenrun Geom Header Load by FFID and the zero ffid’s willbe dropped. (303998)

• In the binning menu ProMAX allows you to enter morethan two values to the right of the decimal point. If youbin at this point these are the values that will be used.However if you save and re-enter this menu the valuesare rounded off to two digits. To get the greater accuracyyou must re-type in the true number. (276579)



• The documentation states that if you are enteringbinning parameters by hand, you must enter anappropriate X and Y grid origin and an appropriateazimuth relative to the Y axis in order to establish theCDP, inline and crossline numbering scheme. What isnot stated is that this is the CENTER of the first bin.(516174)

• Problems have been reported in the Volume ViewerEditor when geometries are created with initialcoordinates of X=0, Y=0. The work-around is to biasthese values by some non-zero value. (134308).

3-Component Receiver Orientation

• In this process, the maximum value in a gate is a peak. Ifthe maximum value is a trough, and you have picked ona peak, the output will be 180 degrees off. (503259)

• In testing the results from the Hodogram Analysis Icompared them to 3C Rcvr Orientation. The 2component works correctly, but the 3C does not rotatecorrectly. (513380)

3-Component Transforms

• SGI Only: The Eigen value ratio option accumulatesCPU time, but does not produce any outputs. (503919)

• If you select a user defined trace header for placement ofthis attribute, the trace header must contain realnumbers. If an integer header is used, a single attributeis written to only the last trace of an ensemble. (504222)

3D Mix

• If you had not built a 3D PostStack database, running3D 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 ofcrosslines 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 (typicallydue N-S or E-W) and crossline bin dimension (typically



a negative bin dimension) can generate X and Y valuesfor inline and crossline inverse to the documenteddescription. Quality check the database attributes afterrunning 3D PostStack Geometry, and the sign of theBin size in crossline direction parameter altered ifnecessary. (502241)

3D Post Stack Regrid

• In surveys where the first inline and crossline does notequal 1 this module may zero traces on the lownumbered inlines. (513857)

• There is a numerical noise problem when the input gridis oriented at exactly 45 with respect to the output grid.The work around is to adjust one of the coordinates sothat the relative angle is not exactly 45 degrees. The fixinvolves only making the processing direction decisiononce. At 45 degrees, it doesn’t really matter whether theprocessing direction is inline or crossline (as long as thesame direction is used throughout. (130491)

• In the usage section of this help file, it is not stated thata Post-Stack database must exist for the dataset theuser wishes to alter in 3D Post Stack Regrid. This can beaccomplished by running 3D Post-Stack Geometry.(13489)

3D Ref Statics Model*

• If SOURCES are in descending order in the geometrydatabase, the corresponding receiver XYs appear flippedwhen describing the mode. This is a visualizationproblem; it does not affect the actual model definition.To obtain the correct shot-receiver appearance, sortSOURCES into ascending order and refinalize thedatabase prior to running this process. (503455)

3D Refraction Statics Inversion*

• Linux Only: The interactive mode of this program willnot converge. It will run until it reaches the maximumnumber of iterations. The non-interactive mode doesconverge. (149431)

3D Supergather Formation

• When the minimum center crossline number is greaterthan the maximum center INLINE number the program



will halt. (293557)

Work-Arounds(1) Use a supergather grid large enough to not violatethis condition, then window later.

(2) Select the supergather by individual center-cdpnumbers instead of the grid rectangle

3D Supergather Select

• If the trace header word SG_CDP already exists but hasthe wrong format type, the value of SG_CDP is incorrect.The work-around would be to put a Header Delete in theflow before this module. (513616)

3D Velocity Viewer/Editor

• If you say YES to specifying the bounds of the velocityfield and select a sub-set of the data, then toggle theparameter to NO. You will still only get the sub-setpreviously specified. The work-around is to re-set therange back to the entire field. (301336)

• Using the smoothing option in this tool to create avelocity function at every CDP does not work. Althoughviewing this velocity field looks correct the resulting tablemay have missing or duplicate functions. The work-around is to use the Volume Viewer/Editor. Use INLINEand XLINE as coordinates and re-grid to everyINLINE/XLINE then save the volume. (508289)

Additive Noise and Spikes

• The ensemble/trace selection controls for where to placeimpulsive noise references internal counters of ensembleand trace within ensemble rather than any sort keys andtrace header words. Thus 3:4/ refers to the fourth traceencountered within the third ensemble in the inputstream. (514184)

• This may generate noise at the water bottom if NMO isnot applied before the noise burst edit. (142347)

Alternate Machine

• This module fails with a Segmentation Violation. It isrecommended to use the new ProManager tools tosubmit jobs to alternate machines. (513640)



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 notdisplay in the popup listing after the copy. Exit andrenter the menu to display the attribute. (502326)

Archive to Tape

• The current ctar code still exhibits a 127 file namecharacter limit. (507370)

• Cannot archive a file of more than 2 Gbytes to tape ordisk. (515505)

• Solaris Only: If you run the archive to tape flow andspecify disk image with removal, the ctar session dumpscore. This is only a problem if you request that the filesbe removed. (304597)

Automatic Gain Control

• When the difference between the smallest and largestabsolute amplitudes in an AGC gate are extremely largean overflow can occur in the scalar calculation causingthe entire trace to be zeroed. (512744) (305313 IRIXOnly).

• This module fails using the “Apply and Save” option ifthe 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-aroundis to ignore this trace in further processing. (512116)

• This module will output zero amplitude angle ofincidence gathers if the first trace of the input CDPensemble is a dead trace. I.e trace_type = 2. The work-



around is to eliminate these traces or change the tracetype header to = 1. (513486)

• If you run separate jobs with min-max angles set tovalues 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 appropriategradient values to zero but not the intercept. (303037)

• The fluid factor stack (Attribute 9) is not being calculatedcorrectly. (513755)

• The Gradient and Correlation calculations are incorrect.Contact [email protected] for a possible fix. (150333)

AVO Interactive Crossplot

• On data with non-integer sample intervals, if you pickseismic polygons and cross-plot them, then stop and re-start the flow, the polygons may be shifted deeper intime. (507771)

• This module will not run properly in conjunction withIDA and DBTools. It is recommended to use Disk DataInput 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” ahorizon may cause the job to abort. The work-around isto pick and snap horizons in Trace Display then viewthem in this module.(509845) (509757) (509964)

• In AVO Interactive Crossplot, when you slide the barson Crossplot Scaling, the labeling on the axes does notchange to match the data. (303036)

• Snap option flips display. This may occur when usingthe horizon pick icon and then using MB3 to snap yourpick. (512272)

• Adding points to the polygon may corrupt the polygontable. (512984)

• Cannot change horizon color if 2 or more horizons areup. (512315)



• Setting Label Plots with AVO_ATTR to yes does not giveany label at all. (512963)

• Selecting a polygon that encompasses ALL plotteddatapoints should highlight ALL of the seismic traces, itdoes not. The 1st and last trace are not highlighted.(304141)

• Using Horizon Attributes/Window Horizon can causetime axis and seismic display to flip so time 0 is at thebottom and time xxx is at the top of the display. Thisseems to happen when your windowed gate extends tothe bottom of the display. The windowed horizon polygonis flipped as well. Any other manually entered polygonsstay in their original location. When you turn offHorizon Attributes/ Window Horizon, all goes back tothe correct position. (512139)

• This fails to read the crossplot tables generated by IRIXor AIX, but works in Solaris (1998.6 and 2003.0).(131226)

AVO Volume Reconnaissance

• Although the help file does not state this, the inputvolume should be padded. Otherwise you will get thiserror:(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 isexpected 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 coloroverlay. The positive side of the wiggle trace disappearsonce a trace is clipped. The work-around is to replace thevalues 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)



and set PARMS,SIDEL=R (for right side), L (for left side)or LR (for both). YOU MUST PASS DATA for EVALS,LDIRto be honored. (513621)

• This module will not read in horizon pairs with CDPvalues greater than 32,000. (143043)

CDP Binning

• It has been reported that if this module attempts to writeto an OPF partition that is 100% full, the database maybecome corrupted. (138796)

CDP/Ensemble Stack

• Applying Final datum statics after stack updatesTLIVE_S and TFULL_S incorrectly. TLIVE_S andTFULL_S are altered by close to 2* fnl_stat instead of1*fnl_stat. work-around: Use Trace Header Math to addFNL_STAT to TLIVE_S and TFULL_S after stack.’ReapplyMutes’ in further programs will be fine. (513345)

CDP Trim Statics

• On Marine data you will still need to bin receivers to getthis to run. An SRF OPF is required. (515166)

Color Edit

• A 3D license is required if you start this process from aflow. If no 3D license is available, start the Color Editorfrom an interactive display tool. (505907)

Common Offset F-K DMO

• On some datasets the remove padded traces portion ofthis macro does not work. Checking the job.output fileand comparing the number of traces output from theDMOFK_PANEL and RMPAD_TRACES steps will show ifthis is occurring. The work-around is to use a modulelike Disk Data Input to eliminate the traces flagged aspadded (e.g. PAD_TRC=1). (508875)

Convert 2D Table to 3D

If you try to append a 2D table to an existing 3D tableyou will get the following error:

cannot find outvel2 in packet file



The work around is to edit the menu velTo3D.menu,The line outvel2 should have type_desc instead ofselect_item. (514114)

• The database method for mapping 2D to 3D fails. Theother two methods work properly. (136809)

Create CGM+ Montage SDI

• Users have reported that attempting to use this modulewith Version 2000 SDI_MONTAGE fails with themessage:

libXm.a [shr_32.o] NOT FOUND

One work-around is to create a script called sdi_montagethat un-sets the variable LIBPATH before executing thesdi_montage executable. (512895) NOTE: Fixed in2003.0

Create CGM+ Plotfile

• A signal 10 sigbus error occurs if you try to overplot aheader value created in the same flow. You shouldoutput a file with the new header, and bring the new fileinto Create CGM+ Plotfile with Disk Data Input.(500653)

• The process dies with a memory fault when creating anautomatic sidelabel on an input file lacking a CIND file,such as a SeisWorks Input or Synthetic TraceCreation. You should output a ProMAX file prior tocreating the CGM+ file. (500449)

• If plots are not at 400 or 200 dpi, label text fonts cannotscale exactly. You should scale your plots to 400 or 200dpi, to get an exact scaling. (501007)

• 3D timeslice only: When plotting timeslice traces, CDPvalues are null. To plot timeslice traces in CGM+ format,use Trace Header Math to set CDP = xline_no orinline_no, depending on timeslice orientation. (501790)

• Turn off the label for overplot attributes does notwork correctly. When overplotting attributes, turn offlabeling by selecting Yes to Include Label, and creatinga blank entry for the Label Text field. (501771)



• This process currently handles up to 8000 monochromesamples and 4000 color samples per trace. Using agreater number of samples results in the errors:

scaling mode 8224 illegalscaling mode 8192 illegalIllegal Element Id in Class 2INVALID point 40556 class code val: 2 0 0

work-around: Run the display using multiple time trappedinputs to create larger plot files. (501908)

• When using Input Trace Order to plot, either theindividual trace annotation, or the timing lineannotations can be improperly shifted, depending on theuse of a trace gap. Avoid the problem by using EnsembleRedefine before Create CGM+Plotfile, or CDP can beused rather than Input Trace Order. (502165)

• If you have a large number of plot layers forTraces/Plots, some parameters can be lost at thebottom of the menu. Toggle off the topmost parametersfor Enter RMS Explicitly for full access to allparameters. (502157)

• If the Number of traces for Gain Calc. is specifiedgreater than the number of traces to be plotted, and anEnsemble Gap is specified, the data overplots the timingline annotation. Specify Number of traces for GainCalc. no larger than the total number of traces to plot.(502608)

• Reset the timing on a zipper cannot be reset fromwithin the interactive menu. A value of 10 is alwaysused. If required, the value can be reset by using aprivate copy of the cgmplot_socket menu, and editingthe default value for zipper_msec. (502756)

• Display a down line only can incorrectly generate textin the seismic data. There is no work-around for thisproblem. (502885)

• Upon creating a plotfile, the plot control file is set withcolor_cgm = True, even if the trace display is black andwhite. This can cause some plotting software to makethree 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 acorresponding attribute graph, the borders of the graph



can appear to disconnect, and then wrap around at theend of the section facing the wrong direction. (503770)

• The sidelabel can be truncated if you input a value forAmount of whitespace greater than zero, and theresulting label is larger than the seismic data used forplotting.

work-around: Find the current length in the cgm_cntlfile; this is the 4th parameter after VDC_VIEWPORT. Addthe amount of whitespace required and set the minimumside label size in the menu to the increased size.(504097)

• When plotting a dataset containing every Nth ensembleor specifying INLINES:XLINES as sort keys, a largecgm.bnxx file may be created in the flow directory ifwildcards are used in the Disk Data Input sort list. Thework-around is to explicitly specify the range ofensembles in the input step. (301354)

• If you choose the posting method of ORDER and theselection list begins with 1, the second trace will actuallybe annotated. In order to label the first trace theselection list should begin with 0. (301843)

• Solaris Only: Executing the exact same flow on AIX vs.Solaris systems produces two different size velocityboxes. The Solaris version has more space between thetime and velocity columns. No known work-around atthis time except to use The Unisec modules. (509697)

• A Create CGM+ Plotfile flow that has a seismic datasetand a color cell fill overlay may have the color plot overthe wiggle traces, depending on the number of traces forgain calculation. The work-around is to specify in themenu more traces than are being passed for gaincalculation. (512199)

• Excess amounts of blank paper may occur as the resultof the VDC maximum X coordinate extent being set to32767 in the generated CGM+ plotfile. The potentiallength of plot may come out to be (32767)/(dotresolution of plotter). Contact support to see if a patch isavailable. (130422)



Crooked Line Geom Spreadsheet

• SGI Only: Attempting to open a saved track will causethe Geometry Spreadsheet interface to crash. (513944)

• When you choose the Layout Bins Icon there are 3options MB1,2,3. If you choose MB1 first then MB2 willno longer work. If you wish to experiment with thevarious options use MB2 first. (512663)

Database Display

• NULL values for an X/Y database attribute causeprojections to other domains to fail. NULL values can befilled using the Math/Fill operation in XDB DatabaseDisplay to correct for this problem. (503398)

• AIX Only: Database display is not displaying the nullvalues as triangles on the top and bottom of the graphon an IBM. On the IBM, there is no way of telling wherethe null values occurred. The only way you know youhave nulls is <null>. will be posted by the attributes thathave nulls. (515341)

• Using the option 3D - Display - XYGraph then chooseany three X,Y,Z attributes from the TRC order. Thenenable the “Alternate Domain” option, the display maycrash. (120125)

Database/Header Transfer

• When creating multiple user defined headers, thecreated header name can contain trailing string valuesfrom one of the previous entries.

work-around: Place the shortest user defined string firstin the list of header transfers or call the process multipletimes. (503391)

• The database will not accept the transfer of 8R floatingpoint headers which can be created in a SEG input step.The fatal error is:

Database format = 2Header format = 3

work-around: Obtain ASCII files for spreadsheet import inorder to place this data in the database. (504225)



Database/Horizon Transfer

• Currently you may not transfer IHD type horizonsdirectly to the database using this module. There are twowork-arounds. The first is to use the ASCII export optionthen import this file in XDB. The second is to copy thennnnnnnn.IHD binary file in the LINE directory tonnnnnnnn.HOR using the UNIX cp command. (301638)

Datum Statics Apply

• If you run the Datum Statics Calculation with a new IDnumber (e.g 04) for Source/Receiver/CDP parameterfiles, you get a notification of "Job completed". If youimmediately go in Datum Statics Apply and try to pickthe new Source/Receiver/CDP parameter files, the newID entries i.e (S_STAT04 etc.) will not be visible in firstattempt. However in second attempt the new entries arethere. (120120)

Datum Statics Calculation

• When you run this module multiple times differentCSTATxx attributes may be created. However only ONEversion of C_STATIC ever exists that is the same as thelast execution of this module. When you use the module“Apply Datum Statics” the user chooses which version toapply. However some modules such as “DMO to Gathers3D” ALWAYS use C_STATIC. Therefore it is best practiceto make the version you wish to apply the last. (301410)

• This module fails if the database attribute C_STATICdoes not exist. The work around is to use DBTools tocreate this attribute before running this module. Or runa flow containing Apply Elevation Statics to putC_STATIC into the CDP database, then run DatumStatics 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 toplot null values. The NULL value count is also lumpedinto the first histogram plot. (504860)



• Problems can be encountered when displaying a plotwhich contains NULL values. An error returned to yourshell 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 displaythese attributes. (505282,515339)

• This process fails when attempting to display stationswhich have 8 digit values. The error will point to a failurein /advance/port/src/lib/dbtX/MarkersO.C. There is no work-around for this problem. (506097)

• SGI ONLY: Accessing large (in our case 24 million traces)TRC Database attributes may cause DBTools to coredump. For SGI, setting the variableDBTOOLS_SERIALIZE_LOAD may help for surveys lessthan 10 million traces. For the larger databases, you willhave to create smaller databases for viewing and canmerge later on.(507828)

• If you are selecting traces in DBTools and sending themto a process such as Trace Display via IDA. DBToolsmay 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 DBToolsthat are not on the sort list in Disk Data Input. (507869)

• In the tabular view, when editing cells, sometimes thistool will stop accepting edits. At this point in time nocause has been determined and the only work around isto use XDB and ASCII export, make the changes, thenre-import. (507973)

• While editing in tabular view entering certain valuessuch as 5.1 will return 5.099999 instead. (507974)

• When altering any entry the LIN order it is recommendedthat you use the XDB tool rather than DBTools.(508331,508722,301008)

• The ability to interactively display traces to TraceDisplay will not work if more than one attribute isselected in View - Overlay. (515016)



• Taking the log of an attribute that has a 0.0 in the arraywill fail. There is no error message DBTools only outputsresults up to the trace with the 0.0 value. (515033)

• Delimit ranges may report incorrect min/max values ifthe bin grid definition is smaller than the actual dataset.(130864,130808)

• Viewing "Summary statistics" "focus” on, “excludeselection" is not working. (130607)

• User brings up DBTools-->File-->XDB Database Displayand goes to SIN database to display attribute. If he thentries to switch to another line XDB Display crashes. Theworkaround is to go back out to ProMAX UI and re-enterDBTools under other line. (128736)

• SGI Only: Attempting to copy an attribute will causeDBTools to crash. Work-around: use XDB or dbmath tocopy the attribute. (518323)

Disk Data Input

• See also Interactive Data Access.

• On large datasets which are sorted requiring overlappinggroups of traces, such as sort string 1-9999(3)[4], thesort 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 thedeveloper (Disk sort)

work-around: Break the input dataset into smallerpieces. (502021)

• The error:

Corrupted trace or trace header encountered

has been encountered after reading in field data whichhas a non-standard TRC_TYPE value. If this error isencountered, you should use a Trace Header Math stepto reset TRC_TYPE =1 during the field tape input flow.(502653)

• Certain combinations of sort keys such as CDP: CDP_Ymay generate memory errors. The work-around is to useInline Sort. (512181)



• It has been reported that users have encounteredproblems sorting datasets that have individualTRC/HDR files greater than 2 GBytes. We recommendthat users set the size for primary and secondary storagein the config_file to 2000 or less. (512529)

• Certain sort combinations where the group size is largerthan the increment e.g. 1-200(4)[19] may generate a nulltrace in the resulting output dataset. (145744)

Disk Data Insert

• When Observe Dataset Boundaries is set to Yes, theLSEG_END header is not set to 1 on the final trace of theinserted datasets. You can manually override the headerby selecting the appropriate trace in an IF block, andresetting the header using Trace Header Math.(502692)

• When inserting sorted datasets in Merge mode theinserted datasets may not be merged into a singleensemble. The datasets are sorted correctly, but cansplit on the input boundaries. If required, the InlineSort or Ensemble Redefine process can be used tocreate single ensembles on the fly. (503659)

• Maximum traces per output ensemble is limited to avalue of 9999. To obtain larger ensembles, change theactual MAXDTR values in the disk_insert menu, or useEnsemble Redefine within the job stream itself.(504159)

• Occasionally this module will fail with an errorindicating that the sample rates of the two datasets donot match, even though a MB2 history of each datasetindicates they are the same. This is due to the executiveseeing the sample rate as 1.999 or 2.001 rather than2.0. The work around is to use the sample rate overrideoption 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 firstdataset has only one trace. (512619)



Disk Data Output

• When using the overwrite option after modifying ageometry, the expanded dataset information cannot beupdated for the CDP extents. Using the MB2 datasetinformation listing will show incorrect extents. Theproblem can be avoided by outputting to a new datasetinstead of using the overwrite option. (503387)

• This process writes in round robin fashion to allsecondary partitions listed in the config_file untilencountering one or more full filesystems. MultipleTRC/HDR pairs are then written to the next non-fullfilesystem found in the config_file list. For example, ifDisk 1 and Disk 2 were full, followed by Disk 3 and Disk4, Disk 3 would receive TRC/HDR files 1,2,3, 5,6,7,...and Disk 4 would receive TRC/HDR files 4,8,... Whilethis does not create an actual output problem, it canpotentially cause disks at the top of the config_file list tofill more quickly than disks at the bottom of the list.(503763)

• If traces are appended to an existing dataset, theMaximum traces per ensemble is reset to themaximum number of traces in the appended dataset. Asubsequent Disk Data Input step using the Get Alloption will output ensembles based upon the finalappended value. An Ensemble Redefine or Inline Sortcan be included after the append step to ensure that thenumber of traces per ensemble is set correctly. Asimple sort on Disk Data Input will also provide a work-around if this situation is encountered. (503949)

• Users have reported that at times the CIND file for agiven dataset becomes unusually large. At this time thecause has not been determined. The suggested work-around is to copy this dataset into a line with nodatabase, 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 datasetwhile it is being written to disk it is possible that ProMAXmistakes this as a duplicate trace being created andstamps the dataset as not matching the database.(513095)



DMO to Gathers 3D

• Running this module changes your OFB_CNTR andOFB_NO headers to a constant value. You can use TraceHeader Math before this process to save the offsetvalues into a user defined header. These may be used torestore the original values after DMO. (505646)

• This module is NOT passing the flow parameters to theProcessing History for subsequent use in Create CGM+Plotfile labeling or dataset history. (508050)

• Using the Offset Squared option for offset samplingoutputs nothing but dead traces (TRC_TYPE=2). Thework around is to only use the OFFSET option for offsetsampling. (514245)

Eigen Stack

• If you attempt to use a time gate that was created bydefining 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 theshallow layer first.(513945)

Eigenvector Filter

• SGI Only: This process may stall during execution if thedesign gate contains zero amplitudes. (507074)

work-around: Use a design gate that encompasses onlylive data.

• SGI Only: Program stalls when amplitudes greater than100 are used.work-around: Use Trace Math to scale down amplitudes.(508141)

Emacs Editor

• Linux Only: Does not run from within the ProMAX Userinterface. (516052,130873)

ESI Disk Data Input

• This module will fail if you attempt sort using headersthat are not integers (148177)



Expand Flex Binning

• Application of this process will reset the global datadomain of the relevant dataset to unrecognized. Whilethis will generally not affect any subsequent use of thedataset within the processing system, the global flag canbe reset if needed using Trace Header Math (changeattributes/data domain). This is fixed in the 2003.3release.(503954)

• This module will allow data to be input in any sort order.However it will try to hold enough space in memory for 9ensembles. In datasets where the default primary key issomething like INLINE there may not be enough memoryto hold 9 ensembles and you will get an “Ensure failed” errormessage. (513202)

Explicit FD 3D Depth Mig (SMP)

• Using values other than the default for Maximum Depthmay generate results that are “stretched” below thisdepth. (514077)

• Occasionally when the re-start option is selected, thejob.log file may get corrupted generating the followingmessage:

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 forall platforms, but only if the menu option Shared-Memory Parallel Version is selected. If the optionNetwork Parallel is selected in the menu, the problemdoes not occur. The problem has been fixed using theExplicit FD 3D Time Migration (SMP) module.(513014)



Extract 2D Table from 3D

• When you select Stacking Velocity for input this modulewill also generate an inaccurate interval velocity in depthtable. (513138)

Extract Database Files

• A full extraction does not complete the grid informationin the LIN database. Appropriate entries should beedited. A more robust approach is to bin and finalizethat database using a Geometry Spreadsheetapplication. (505914)

• For marine geometries, the marine flag may not be set.(505912)

• This process checks for CDP values in the headers, evenwhen Extract CDP binning is toggled off. Use TraceHeader Math to create a temporary integer CDP value.(505939)

• An Invalid CDP X-coordinate error message appearswhen attempting to project coordinates to CDPs after afull extraction of the database. For example, projectingSRF Geometry Station to CDP Geometry Station.(507386)

work-around: Use Math->Fill for both the CDP GeometryX_COORD and Y_COORD before projecting.

Finite Difference Modeling

• When inputting a dataset and using the geometry fromthe headers, if you have a roll-on shot situation, theglobal shot fold is set by the first input shot. Because theroll-on increases the fold at the next shot, your job canabort with the following error message (507343):

The number of traces in this ensemble is more than specified in theglobal variables

• Users have reported getting SIGBUS errors with thismodule while attempting to use the Ormsby wavelet. Thework-around is to switch to the Ricker wavelet. (512535)

• There is a problem with the menu. If the user firstselects the Normal Point Source option and wants touse a trace dataset for header information (Takegeometry from the headers of an input data set? - Yes)and subsequently opts to use the "Exploding Reflector"



option the job fails with an error stating that the data isnot sorted in CDP order. The Exploding Reflector optiondoes not have the option to use trace header informationand disappears from the menu when using this selectionbut is still expecting to pull the geometry informationfrom the headers. The solution is to make sure you turnoff the "Take geometry from the headers of an input dataset?" parameter before using the Exploding Reflectoroption. (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 animatesaved images. (130529)

F-K Analysis

• On a 3D dataset, if you pick a polygon and save it, thenre-execute the flow, the polygon will not display. It maystill be applied with no problems. (512332)

F-X Decon

• SGI Only: This module is running slower in version2003.x than it did in 1998.6. Work-Around: use version1998.6 if possible. (149746)

Floppy Input

• This process can fail on some operating systems, eitherwith a SIGSEGV segmentation violation error (Solaris) or with aFloppy Open Error pointing to an invalid filename (AIX). Insome cases, limiting the input to fewer records(approximately 300) and processing the input file inpieces has resolved this problem. (503674)

• No facility to input OYO 3 format from a mcseis170recorder. Currently there is no work around for thisproblem. (301359)

Fourier Trace Interpolation

• The last output trace may be numbered incorrectly.Work-around: Use Trace Header Math to re-number thetrace or pad an extra trace prior to interpolation thendelete it afterwards. (305444)



Gated SC Decon 4: Cleanup

• This module is designed to delete the INI and SOLscratch files. This module will run and completenormally even if there are no files to delete. (515530)

Geometry Spreadsheet General

• If shots or receivers are deleted in the spreadsheet andthe database is subsequently rebinned and refinalized,any previously created database attributes generatedoutside geometry definition, such as first break picksand statics, will not match the new database description.Those attributes should be recreated if they are requiredin any subsequent processing. (502579)

• If shots are deleted in a spreadsheet initiated from anextraction or UKOOA import, the File/QC option fromthe TRC database will hang. (502964)

• Parameter tables defined with integer values for sortkeys larger than plus or minus 2**23 (8388608) can failwith the following error:

Unable to find SIN given FFID xxxxxxxx

Within the geometry spreadsheets and database, integerattributes can be entered with a precision up to plus orminus 2**31, and trace headers are loaded correctlyduring the Inline Geometry Header Load process.However, parameter table accessing keys using thelarger values fail due to truncation problems. (502967)

work-around: Repick or recreate the parameter tablebased upon key values that are not similarly affected, forexample, using SIN or SOURCE rather than FFID.

• When interpolating, if zero values are in the spreadsheetand “Interpolate all values in marked block by recordnumber” is selected, the zero values are replaced withinterpolated values. If NULL values are in thespreadsheet and “Interpolate all values in marked blockby station number” is selected, the NULL values are notinterpolated. (504995)

• The Undo option in the Edit menu item can fail tooperate correctly. (505307)

• The Import -> Merge option does not work for the Linecolumn in the spreadsheet editor. (503740)



• Depending upon the type and size of font chosen and theamount of re-sizing of the spreadsheet window the lastline in the spreadsheet may be only partially visible.Potential work-arounds are to deletethe.Spread_parms.xdr file in the users home directory.Also make sure the 75DPI font is ahead of the 100DPIfont in the font search path. (507740)

• Using a “Binning Bias” of -1 causes an error. This maymake it impossible to get the desired value for the firstCDP. The work-around is to use some other bias valuelike 0, -2 etc. then use Trace Header Math to re-numberthe CDP values. Afterwards, extract a new geometry.(301897)

• When a database is binned in pieces, and the option touse the default for offset binning is taken, the lastexecution of binning determines the range of OFB_NO’sfor the line. It is possible that the resulting min-maxrange is not accurate for the entire line. The work-around is to use the “User Defined” option for offsetbinning 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 thesame direction CDP_ELEV may get projected in reverseorder. This appears to occur when you choose the option“CDP’s increase from last trace” in the binning menu.(514180)

• AIX ONLY: The “Cross Domain” icon does not work inXYGraph. (144466)

Hand Statics

• Inputting a large number (approximately 1500) ofREC_SLOC/static pairs via an ASCII input file will causethis 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 smallerfiles and run this process several times. (501070)

Header Values

• This module will fail with a message:

Improper delimiting in header list



If you attempt to list a trace header name that is onlyone character long. The work-around is not to createtrace headers of one character. (303189)

History Viewer

• The dataset history viewer will not access and displaythe residual statics database filename if the NormalDatabase option is not chosen in the Apply ResidualStatics menu. If required for display purposes you cansave the history viewer session, edit the file, and thenread that file back into the display session. (500929)

Hodogram Analysis

• Users have reported this module generating theta andphi polarization angles that make no sense. It issuggested users check the output listing closely forangles that are too large. (513376)

Horizon Flattening

• Although code says 50,000 samples are allowed in thepick table, we found that only somewhere between12500 and 15000 picks are allowed. That is, a table with12500 picks worked, while table with 15000 picks failedwith:

Error reading CDPs and TIMES from the horizon table!

work-around: Break into smaller pick tables (~12500 picksper table) and run on subsets of data. (507364)

Horizon to RMS Velocity*

• During the conversion to RMS, velocities are output onlyfor CDPs covered by the first horizon (when multiplehorizons are selected). If the first horizon cannotencompass the entire line, run this process multipletimes, appending the output files as needed. (503109)

Horizon Velocity Analysis

• The median and mean functions are switched whenrunning in the edit velocities mode. Use mediansmoothing for mean smoothing, and vice-versa. (503108)



IF

• In some cases the end of ensemble flag will not be passedto subsequent processes. This module was redesigned tobetter handle large volumes of data. If this flag isessential, the work around is to either use EnsembleRedefine after the IF/ELSEIF. Or use the same primarykey in the IF as you did in the Disk Data Input. (507877)

• If you have nested IF/ELSEIF modules in a flow and theprimary key is the same as in the input step you may getunexpected traces output. The work-around is to use orcreate a different header. (512958)

Inline Geom Header Load

• When overwriting a dataset, the following warning: Formatis 1, should be 2 indicates that a standard header has beencreated with the wrong type. For example, OFFSETmight be inadvertently created using Trace HeaderMath prior to loading geometry as an integer value, yet isrequired to be a floating point header. The incorrectheader can be deleted prior to the Inline Load step usingthe Header Delete process, or the output should bedirected to a new dataset. (503296)

• Marine Data Only: This process can fail with a SIGSEGVerror if you run Extract Database Files, and thenattempt to load the geometry based upon the Match byvalid trace number designation. You should be able toload geometry by matching on SIN, or by creating aunique trace header such as SOURCE using TraceHeader Math. (503873)

• TIM_SHOT values with 7 digits used to match headerand database values fail to load headers properly,indicating that certain shots are not in the database. Ifrequired, place the TIM_SHOT value in a differentheader, such as DAY_SHOT, which will then correctlymatch the larger values. (506811)

• Linux Only: Marine inline header load may fail if SRFOPF FOLD attribute does not exist. The work around isto bin receivers in the spreadsheet. (515840)

Interactive Data Access

• When using IDA with Trace Display and displaying largedatasets, (such as 100,000 traces), you can experience



difficulty using the backwards arrow. Using the backarrow to go back one ensemble works the first few times,however, paging forward and backward three or moretimes, may take you back to the beginning of the sort.From this point on, the back arrow will take you to thebeginning of the sort unless you specify a new sort.(507388)

• When using IDA with Trace Display, IDA can fail whenrequesting more than 600000 traces. (507462)

• When multiple applications are set up to run IDA from asingle X-server, all applications will send and receive thesame PD messages. Avoid multiple IDA sessions from asingle screen unless it is intended to use the same tracesby all active IDA sessions. (506040)

• If IP address is specified rather than host name fordisplay device, IDA displays first ensemble then hangs.the job runs fine without IDA. (511240)

• Inline Geom Header Load in ProMAX 2003 behavesdifferently on marine and land data. If the input datasetfor Geom Load has some dead traces (TRC_TYPE 2),land data processes all the traces while in case of marinedata dead traces are dropped. (1147104)

Insight Data Input

• LINUX Only: Fails with a socket error, no known work-around at this time. (518077)

Interactive Radon/Taup Analysis

• Attempting to use the SUBTRACT option in this modulemay cause it to fail with a signal 11 error. There is noknown work-around at this time. Fixed in version2003.3 (513560)

Interactive Spectral Analysis

• The process fails with a SIGSEGV error when usingstacked data on input, and the Primary header fortrace label is left defaulted to Source. Set the labellingheader to CDP, or some other poststack entry. (501620)

• If only one trace is input the program fails with thefollowing message in the job.output:

Ensure failed (old._ny==yOld.n()), file



“/advance/port/src/lib/agC/Bytemap.C” line 70

work-around: Input 2 different traces in Disk DataInput.(506977)

• If you perform an extreme or microzoom on one of thetiles such as the spectral or phase display, you can expe-rience the windows hanging while the screen refreshesor the process can exit out of the X-window. (507133)

• Solaris Only: You may experience Grayscale colormapproblems if you:

1) Run a ProMAX session without other applications,such as SeisWorks which will feed ProMAX correctcolors.

2) Select Multiple subsets in the ISA menu. (507284)

work-around: If Interactive Spectral Analysis displaysstrange colors or black, click Data ->Trace Display ->Color map-> Color. Then select Options -> SpectralAnalysis. This sets Trace Display to the strange colors.Go to your original display and select Data -> TraceDisplay, your colormap is switched back to Grayscale.

• If you iconify then restore the display access to the colormap is no longer possible. The work-around is to re-startthe flow. (515299)

• The method used to scale the forward FFT in this modulediffer from the one used in Trace Math Transform. Thelatter is more accurate. (126876)

• Solaris Only: The T-X display will be all black is theXdefault *.useColorObj: False is set. (138726)

Interactive Velocity Analysis*

• This process will still run but is no longer supported onthe current certified platforms. You are encouraged touse Velocity Analysis.

Interactive Vel Editor*

• When using the Input/Set velocity option with a value of0, the stored values are set to 1.0 e-5. If hard zeros arerequired, you should first set a constant non-zerovelocity, and then add the negative velocity value in asubsequent step. (503179)



Interpretational Mig. Vel. Analysis

• This module will fail with the message Abnormal terminationSignal = 10 if the input dataset is missing any CDP’s.(509261)

List/Restore from Tape

• The option to Restore 5.0 does not work. To restore 5.0Archives, run the tar command from the UNIX commandline. 5.0 Archive files are written with a ‘./’ prepended tothe full file name. (500856)

• When restoring a dataset from a Line/Survey, you areprompted for the Former Area name. The parameter canbe filled out, but is not used during the restore process.(501777)

• Upon completion of any Restore operation, thejob.output file should be reviewed for the occurrence ofany UNIX errors. The restore job may continue tocompletion, even though errors similar to the followingmay exist:

Unix error - broken pipectar: Error reading file xxx/yyy/...

The dataset affected by the error can be restored in arerun of the Restore operation, selecting the appropriatedataset. Individual files can also be restored by runningthe ctar executable from the command line. (502043)

• The following error can be encountered when restoring aProMAX 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 whichencounter checksum errors, and the integrity of thosefiles should be verified if possible. (502019)

• The Header Dump option does not work, failing with theerror message:

No mode (-c, -x, or -t) was specified

There is no work-around for this error. (503124)

• ProMAX looks in the original secondary storagedirectories, if they exist, and accesses old directories



rather than using the secondary storage directorieslisted in the config_file. (507033)

• When restoring a new AREA, the user interface will notautomatically refresh and show the new AREA. Thework-around is to either add a new AREA or select the“config” button at the bottom of the user interface andtoggle the “Sort Areas “option from yes to no. Either ofthese will cause the user interface to refresh and showthe new name. (301664)

• Setting the parameter “Use primary storage for trace files= yes” does not prevent ProMAX from attempting to writeto secondary file systems. (515425)

Make Database Basemap

• This process requires a ZMS license feature. If you donot have a current ZMS license at your site, we haveincluded a demo ZMS feature to enter in your FLEXlmlicense 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 withPROMAX_HOME/port/bin/start_pd or run anotherprogram 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 of80 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 asthe last trace decimated in the ensemble. If this happensto be something other than 1 it could result in tracesbeing dropped from a dataset. The work-around is to useTrace Header Math to re-set the TRC_TYPE = 1. (303033)



Merge Database Files

• The following error results if one of the line names beginswith a numeric value:

Error occurred in OPF routine: MERGE PROCESSOPF unable toinitialize source area: xxx, line: yyy unable to perform merge

The problem can be avoided by renaming the line to startwith an alphabetic character. (502233)

• You can experience problems when trying to mergedatabase files in conjunction with a previous ProMAX5.1 database. The work-around is to use ExtractDatabase Files to create a database under the currentversion. (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 theTRC database does not exist (507492,504682):

Database error - error opening database file, Error creating AUTOSTATdatabase entry.

work-around: Create a new line. Place Extract DatabaseFiles 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 Ycoordinates of the first trace in the ensemble todetermine the interpolated velocity to use. If these valuesare inaccurate, or different from the rest of the traces inthe ensemble, an incorrect function will be applied.(512197)



• NMO correcting data using velocities output from 3DDip Velocity Analysis yields a SIGBUS error on Solaris,a SIGSEGV error on IBM, and runs on SGI but producesbad results (traces with amplitudes of 0 or a constantnumber) (123666)

Work-Around: You have to use a statically linkedexecutable from ProMAX 6.2 with a 6.2$PROMAX_HOME/port/misc/header.list and 6.2menu’s.

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 negativeILINE_NO values after a Pad 3D Stack Volume corruptsthe ILINE_NO trace header values. The work-around isto put a Disk Data Output after Pad 3D Stack Volumeand a Disk Data Input before the Trace Header Math.(512950)

Pad Traces

• If you sort input traces with duplicate CDP’s existingwithin the primary sort order (Common Offset DMObinned data), Pad Traces followed by a Remove PaddedTraces drops all but one of the duplicate CDP traces. Ifthe Remove traces is included in Pad Traces, allduplicate CDP traces are dropped. (500689)

• The program does not function properly if you select theoption to remove duplicate traces in a bin, and the lasttrace in an ensemble is a duplicate. (505508)

Parallel Max. Power Autostatics

If the number of inlines is not evenly divisible by thenumber of nodes this module fails with the message:(132520)

Bad start INLINE number

This is fixed in version 2003.3.



Parameter Table Editor

• When you use CREATE to make a default table, valuesfor NULL are 0.0 and 1000.0. Should be 1, otherwisewhen 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 TraceKill/Reverse in your flow where your parameter tablehas been corrupted by the SKEY header. (512541)

work-around: Since tables with the SKEY header cannotbe read in, you will have to Create a new table selectingthe correct primary and secondary keys, thenexport/import the values from your old table into thenew one.

• Attempting to import an ASCII file into an existingparameter table that is smaller will either fail or deletethe original data in the table. The work-around is tocreate a new table to import into. (515428)

Phase Shift 3D Migration

• This module is cutting off the last sample. If you need toperform an operation where this is critical, such asremoving AGC scalars, run Trace Length to restore datato the full length. (514071)

• Phase-Shift or Stolt 3D Migration can error out inRemute/Rekill server stage, even if this code is not used.This seems to be most prevalent when a big proportion ofthe data is dead. (In this case, about 40%). Contactcustomer support for a possible patch. (129225)

Plot CGM+ Plotfile

• Zeh Only: In order to get Zeh 4.2.5.20 to run withProMAX 2003, you need to use the$ZEHOME/config/zeh_plotfile script provided with ZEH.



As we did before, check the zeh_plotfile script to makesure your NODENAME, PASSWORD, SCRDIR,DAEMDIR, and PRGDIR are set correctly. Then simplycopy this $ZEHHOME/config/zeh_plotfile script to your$PROMAX_HOME/port/bin directory. (you can renamethe zeh_plotfile script that is in your$PROMAX_HOME/port/bin directory to something elseto preserve it first). If you are using OpenWorks, you canalso copy the $ZEHHOME/config/zeh_plotfile script tothe $OWHOME/hardcopy/bin directory. Make sure thisscript exists in your $ZPSPRG directory as well. Youshould then be able to successfully run Plot CGM+Plotfiles* as long as your config_file file has your plotterdevice defined and cgmplot line filled out properly.(131309)

• SDI Only: This module is in-compatible with the latestversion of SDI software. Work-around: submit plots fromthe SDI GUI. Contact [email protected] for a possiblepatch. (145361)

• The UNISEC Create CGM+ module does not put the VDCextents in the .cgmp file, since the .cgm file is metric theextents 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 validinput. (508075)

• The threaded version of this module runs much slowerthan the non-threaded option. (515603)

Progressive Mute Analysis

• In 3D, if the mute table is picked on CDP ordered data itshould be resolved before using this module. Otherwisethe extrapolation is un-reliable. (507672)

Prestack Kirchhoff 3D Time Migration

• TMPDIR is being prepended to scratch directory path. Ifyou have TMPDIR being set somewhere, you may findthat TMPDIR will be used as your scratch directoryversus what you set for PROMAX_SCRATCH_HOME.



This can be verified by running UNIX Commands: showenvironmental variables in your flow. (513228)

work-around: In your config_file you may insert thevariable: merge temporary directories: pshin order to override what is being set by TMPDIR.

• SGI: Restart from checkpoint fails w/ signal 15 if you donot have a Disk Data Output in your flow. This seems tobe random on different SGI machines. (513213)

• The downward statics are being applied in full but theupward static is about 1/2 of what it should be. Astatically linked new executable is on the ftp site under.

product/ProMAX/v2003.0/<platform>/exeREADME_127776 and kirktime3d.exe_127776.Z (acompressed tar file) (127776)

Pre-Stack Kirchoff Time Migration

• This module will fail if you set antialiasing to yes and letit compute (0.0) trace spacing. Work around is to input avalid number. (508042)

• If you request specific offset planes and ask for every cdpto be output, the job fails with a SIGBUS error. The workaround is to explicitly set the output bounds to removethe edge CDPs, or do a Get All in Disk Data Input.(702352)

• Linux Only: This tool fails with a socket accept error.Contact [email protected] for a possible patch. (147022)

Prestack Kirchhoff Depth Mig.

• AIX Only: This module fails with a segmentation faultmessage. (134149)

• AIX Only: This module fails with a segmentation faultmessage. (134149)

• If you are specifying output CDP increments greaterthan the input CDP increment, anti aliasing filters willbe applied. With coarse output CDP spacings, theprogram will perceive almost all the dips except for theflat ones to be aliased, and therefore all your dips arefiltered. We recommend an output CDP increment equalto your input CDP increment be used. (139669)



Prestack Wave Equation Datuming

• This process requires the trace header SRF_SLOC. Thisheader is not always defined for geometries describedunder the 6.0 release. Use Trace Header Math to setSRF_SLOC = REC_SLOC if required. (502110)

ProMAX 3D Viewer

• After changing data range, color or scaling parametersyou are asked to reread the data volume. This second re-read is not normally required and the dialog box may bedismissed. (507806)

• It has been reported that sometimes if you have multiple“entities” on the screen, i.e. combinations of opacity andanimation, when you change the parameters of theopacity cube all of the “entities” disappear and you haveto reread to get them back. No other known work-aroundat this time. (507808)

• The environment variable TMPDIR is not recognizedwhen creating CGM files. The temporary files always goto /var/tmp. If this directory is too small a possiblework-around is to create a link pointing to a largerfilesystem. Or set the environment variable TMPDIRprior to runing this module. (512924)

• The 3D Viewer in Promax will not run without anOpenWorks license available. In 1998.6 it gave the sameerror, but then went ahead and started the viewer.Contact [email protected] for a fix. (132103)

Pulse Test

• SGI Only: This module generates incorrect results onIRIX systems. The work-around is to use InteractiveSpectral Analysis to view the amplitude and phasespectra. (510497)

Q Compensation

• This module behaves differently depending uponwhether you select the menu from the VSP interface orthe 2D/3D interface. If you are applying QCompensation to normal seismic data, be sure that yourflow is built from either the 2D or 3D interfaces.(508582)



Radon Filter

• Radon Filter can create an artificial AVO response.Radon Filter increases amplitude with offset on thenear offset traces and then causes an amplitudedecrease with offset on the far offset traces. (507281)

work-around: Do not band-limit the modeled output in thisprogram, use Bandpass Filter.

• Radon Analysis allows the picking of water bottomrelative mutes. Radon Filter does not. The work-aroundis to first flatten on the water bottom and not use waterbottom 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 thereis a carriage return at the end of the line containing themodel name. The <cr> character must be deleted byediting the input file order to be read into ProMAX.(505671)

• You may encounter this error when reading some SierraVelocity Models.

Unable to interpret model file header

It is not narrowed down to any specific type of model butinstead is random. (513205)

Reflectivity/Synthetic Logs

• The option to add multiples/transmission losses to thesynthetic traces is in error. The amplitudes are too lowand the polarity is reversed. The work-around is to useeither Finite Difference Modeling or Synthetic TraceGeneration. (508201)

Refraction Statics

• Linux Only: When attempting to edit the GRM DepthModel using MB1 to select does not alwaysregister.Cycling through the solutions may cause it toregister. (130535)



• Linux Only: If you display traces while editing firstbreak picks the position of the SIN may not be correctuntil you begin to move through the volume. (130534)

Refraction Statics Calculation

• If you choose to use refractor velocity option in thestatics calculation, rather than user defined, then youmust 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 differentfrom the Receiver Spreadsheet Refraction Statics willgenerate an incorrect depth model. The work-around isto sort the spreadsheets so that both are increasing inthe same direction. (126886)

Resample Log

• This process may add zero samples to the bottom of thelog. If required, a Trace Length process can be used tobypass these samples. (503923)

• There is a problem with Resample Log and Well LogPad to Surface being in the same flow. (507238)

work-around: Run a Well Log Disk Data Output and DiskData Input between the resample and the Pad tosurface.

SEG I/O General

• See also Tape Administration.

• When Input primary selection choice is not set toInput All, the process will read a maximum of 50,000ensembles. (501900)

• Maximum data block size in bytes in the SEG readmenus is now obsolete and will be ignored if set here.You now have to set that in your device.tts by using thevariable MAXBLK="nnnn". (512672)

• The NREW (no rewind) parameter in the device.tts file isnot being honored. Using NREW+NUNL may operateproperly. (514411,515409)



Seg-B Input

• SEG-B Input assumes the record length of first recordfor entire dataset. If the first record is shorter than therest, all other records will be truncated. The work-aroundis 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 toread I/O System Two tapes.

SEGD: I/O System Two, No lines detected.

There is no known work-around at this time. [email protected] to see if a patch is available.(509031)

• Although the problem of reading FFID values greaterthan 9999 has been addressed, there is still a problem inthe menu that prevents sorting on FFID’s greater than9999. (510983)

• When re-mapping headers the job.output will report 2times the actual value of the byte location being re-mapped. (512469)

• ProMAX is unable to completely extract geometryinformation from the Western version of RAPS 2000 Seg-D tapes. (513039)

• Menu: omit records of type: Docs specify that youshould be able to type in a string like 1:5:10:14........however the emacs widget does not appear and youcannot type this type of string. (512037)

• Sercel 408 format: Source and receiver point and indexnumber are not properly mapped from the SEG-Dheader to ProMAX. (513969) The workaround it to remapthem manually.

Main Header Mapping:

S_LINE,Shot Line,2I,,,69/

SOU_SLOC,Shot Station,2I,,,74/

Trace Header Mapping:



R_LINE,Receiver Line,2I,,,22/

SRF_SLOC,Receiver Station,2I,,,25/

• Some formats of Seg-D are showing a 1 msec. time shiftfrom pre-1998.6 versions of ProMAX. This has been fixedin version 2003.3. (304758)

Work-around: Transfer time of first sample in SEG-Dheader to new TAPE_T0 header word. Header statics maybe used subsequently to shift trace data up or down.

• On some 8048 format tapes ProMAX is not incrementingthe FFID. (133287)

• Linux Only: X015 formats are not converting properly.Contact [email protected] for a possible patch. (134764)

SEG-Y Input

• See also SEG I/O General.

• The option to read in data using a primary sort ofReceiver is inoperable. The process will fail with aSIGSEGV Signal 11 error, or with a Primary key out of range error ifa Data Output step is included in the flow. The datashould be read into the ProMAX system with the SEG-YInput defaults, and resorted as necessary. (503544)

• The menu does not currently allow for input of the value0 for the parameter Number of errors in a row beforeaborting job, even though the value of 0 can be used toindicate that all such errors should be ignored. Thetype_desc option in the segy_read.menu file can bemodified as follows: (503652)

parameter: ABORTtype_desc: (int 5 1 99999)

should read

type_desc: (int 5 0 99999)

• The process can incorrectly modify the LIN databaseunits of measurement from meters to feet when usedwith an existing database, if the input SEG-Y file is alsonot detected as metric. The LIN attribute IUNITSZ can bereset to a value of 3 for metric. (503739)

• Solaris only: Reading Western MS-DOS or Charismaformats from tape, the job says it has completednormally, but the Job.output reveals that it has actually



failed w/ the error: (507749)

AFILE: signal termination.

• This module suffers from the same problem as DiskData Input when attempting to sort values greater than8.333 million. work-around is to use IF to sort afterusing Get All in the Seg-Y menu. (507859)

• Values greater than 50,000 are not allowed in the sortlist. Work-around is to use an IF statement after Seg-Yinput to select these ensembles. (513004)

• The job.output only reports the units of measurement ifthey are English (feet). (303429)

• The gain is not being decoded correctly for the 32 bitfixed point format (4 byte with gain). (513323)

• Menu accepting disk image with sample interval of 0. Ifyou enter a value of zero, the menu will not override itwith a non zero value. (513064)

• When using the TTS CONFIG="MFM" option to ignoremultiple filemarks between records job errors on lastrecord and goes into infinite loop. ProMAX reports thefollowing 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 anOverland stacker, the job may hang on the second tape.Contact [email protected] for a possible fix to theproclient binary. (514208)

• Although the option to save the EBCDIC header to thedataset history works, you cannot view it using the MB3history. (514168)

• SOU_H20D and REC_H20D not being read properly ifthey are in the default byte locations. The work-aroundis to re-map them elsewhere. (305060)

• There is a limit of approximately 63,000 samples pertrace. Exceeding this limit causes the job to fail withmemory errors(148281)

SEG-Y Output

• See SEG I/O General.



• Any flow with more than one Seg-Y Output in it will failunless there is an input module between them. (507871)

• Depending on the number of input samples this modulemay pad extra samples on the output trace. This onlyhappens if the output format is 1 or 2 Byte formats.(509875)

• Multiple Seg-Y Output modules in the same flow failwith the message, "Error trying to open a device". Thereis no known work-around at this point. (513366,513782)

• The automatic system generated EBCDIC header has thearea name twice, rather than Area and Line. (514169)

• If you modify a flow and save it in 1998.6 and the SEGYOut menu is from 1998.1, the save will delete the SEGYOut menu. (514108)

• The NREW (no rewind) parameter in the device.tts file isnot 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 anerror. The option Shift MB2 to overlay a new menu doesnot fix it. Users must bring in a new menu from theprocesses list. (515674)

SeisWorks Horizon Input*

• For 2D data, horizons are input with primary andsecondary keys of LINE_NO and FRN_TRNO. Thesehorizons can be interactively displayed and manipulated,but some processes such as Database/HorizonTransfer, can require different table sorting to workproperly. In this case, the horizon can be exported toASCII format, and reimported with the required sortkeys. (503129)

• Display of horizons input to ProMAX using this processmay fail if the associated trace data was not created inthe ProMAX system using SeisWorks Seismic Input.Input of both horizons and data from a SeisWorksproject should resolve this problem. (502983)



• When ProMAX writes horizon files (.hzd) to SeisWorksthey are not “visible” until the index is re-built. (303246)

SeisWorks Seismic Input*

• Queued Jobs: Do not submit multiple jobs from thesame flow, as input information is taken from the mostrecent job submission. If queueing is required, youshould replicate the flow and submit queued jobs fromthe separate flows as needed. (504219)

• All input records will be truncated to the length of thefirst trace encountered in the flow. If differing tracelengths are required for multi-line input you may need topad the record length of the first line pulled from thedatabase, or create a dummy line containing the desiredattributes to be read first. The problem will be furthercomplicated if multiple sample rates are encountered.(504175)

work-around: Group the 2D lines with similar parameterstogether for a single run. Make a separate run for eachgroup. You can use SeisWorks Seismic Input Info tofind such groups before running the job to input data.

• Do not use the Entire Survey option if the SeisWorksproject has a subset of all lines in the survey. (X or Yincrement in the Master Grid Coordinates not equalto 1). The following error results:

ExfVolInit: trace increment specified must be a multiple of the minimumpossible trace increment for the current project

Explicitly specify the minimum increment in the ProMAXmenu 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 plistfile. (138845)

SeisWorks Seismic Output*

• If a job containing SeisWorks Output is started andthen killed, the output dataset name should be verified



in the menu prior to restarting the job. The menu caninadvertently pick up the first dataset name from theProject list of datasets. (504264)

• If you are running ProMAX 1998.6 but are writing to OWR98 or R98+ (1998.0 or .1) and are attempting to add aNEWLINE to a 2D project, you will get this pop-up:

Project _auto_extend:Permissions_error: Cannot extend projectOWPROJECTNAME data model. The project model extension script$OWHOME/bin/extendOW50Rev0ToRev5.sh either does not exist or doesnot have execute permission. Pls check this file and try again.

This EXTEND script only exists in OW1998.5 so it worksif you are writing to that. If you want to add a 2d line in1998.1, you will have to do that with OpenWorks,redefining the survey. (512505)

• The ProMAX menu allows users to type in a longer 3dVfilename than the BCM program will read. Users shouldlimit the filename to six characters if BCM is to be used.(513608)

• When writing large files out to Seisworks the default of5000 for the parameter “Checkpoint Modulus” may slowthe process down. Try either setting this to "0" to disablecheckpoint 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 andoperator pair. (508205)

Example:Window Rejection Factor = 2Operator Lengths = 200,200,200Gates = 500-600,800-900,1000-1390

In this case all traces would be killed because the lastgate 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 gateis larger than 2*200. However these traces should havebeen killed because the shallow gates are still less than2*200.



Split / End_Split

• Tools which initialize a new header will fail when placedinside a Split/End Split branch with the error:

Trace headers corrupted

Those processes must be run outside the Split/EndSplit processes. (502883)

• Fails when placing Parallel Begin/End inside ofSplit/End Split. (513181)

Current tool is END_SPLIT (number X in the flow) Message is:

Trace headers corrupted (5) Current CDP is 557Current ILINE_NO is 8 Please check inputparameters

• Sort selection does not function properly when theprimary header word is an integer and the secondaryheader 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 scriptadding the following line:print “unset TMPDIR”

• This module will fail if more than one hostname in listedfor the parameter “Enter Name of Host”. This parameteris designed to allow execution on a host other than theone currently running ProMAX. It is not there fordistributed parallel processing. (304207)

Steepest Ascent Autostatics

• Option to decouple source/receiver statics solutionsdoes not appear to be working. “Setting Similarity ofcommon source & receiver statics” equal to 0 has noeffect. (507451)

Stolt 3D Migration

• Phase-Shift or Stolt 3D Migration can error out inRemute/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%). Contactcustomer support for a possible patch.

Synthetic CDP Generation

• This module may not output live traces to the maximumoffset specified in the menu. (514643)

• This module is generating incorrect reflectioncoefficients. (148738)

Tape Administration

• Accessing the Status button on a multivolume tape readjob where the tape stacker is in the process of changingtapes will issue a spurious mount message. You mustwait for the stacker to complete changing tapes, andthen reply to the New Stack is loaded continuation message.The status button is also not accessible during taperewind. (502650)

• Problem: Tape mount dialog window pops-up but youcannot see the text. The solution is to add entries likethese to the.Xdefaults file in each users home directory.

ProMAX Tape*background: MistyRoseProMAX Tape*foreground: sienna4

• LINUX Only: The TTS TAPE_REQUEST is notcommunicating with opcon. ProMAX hangs with a taperequest to opcon. (127983)

• Linux Only: The documentation for setting up Linuxstinit.def file. Please download the file quick.pdf fromthe Landmark ftp site. (516215)

• The variable CONFIG=BCAT is not being recognized.Users should switch to the variable CONFIG=NCATinstead. This may be placed either in the device.tts file oredit the Proclient script. (126439)






Tape Copy

• Solaris Only: This process can fail on write with thefollowing error:

Error writing block to output device Error = 22

The problem is currently unresolved. (503263)

• The option to use multiple output drives may not workcorrectly with some tape systems. Copy operations willbe performed on the first output drive only. (504199)

• When attempting to dump traces once in the TapeDump user interface, the user interface can crash. Thisseems to be random. (507309)

Tape Dump

• The “Header Only” option gives zero size error messageimplying an empty file. The work-around is to use eitherthe “Data Only” or “Both” option. (512645)

• 8mm with argument SMNG will not dump. You shouldbe able to dump 3490 tapes configured in the pmxdatabase with SMNG., however an 8mm drive with thisset 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 [.] inthe sort list. The job will complete normally with theproper 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 subsetof traces.



• Setting the parameter MAXBLK to anything other thandefault may result in ProMAX being unable to readmulti-volume datasets. (513607)

• LINUX Only: Tape Data Input will read the first tape andask for the second tape, but even though it says the jobis running, no traces from the second tape are beingread or written out. (142620)

Tape Data Insert


• A Signal 6 error can be encountered if selecting traces bydatabase header limits, and the number of entriesimplied by the input sort string does not match thenumber 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 leftthe same as Tape Data Input. The job ran, but obviouslyit cannot merge data when the insert dataset is not on adevice. Job should fail with the message, cannot run mergeinsert in shared device mode. You must select the merge optionand 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 [.] inthe sort list. The job will complete normally with theproper traces read. (508165)

• Currently cannot do multiple blind tape reads on ashared device (Tape Data Input/Insert on samephysical drive). This is due to the need to scan and writeto disk the CIND/CMAP files for each dataset during theinitialization phase. (511857)

Tape Data Output


• When using the option to output a subset of traces, theTrace list parameter does not recognize the squarebracket code used to identify groups of traces. Forexample, 20-100(20)[3]. The trace list can be completedwithout the square bracket string, or the data can be



subset prior to Tape Output using an IF-THEN block.(502202)

• The short dataset information for the extents of thedataset (MB2 on dataset listing) can be in error for tapedatasets. (502421)

• When encountering SCSI problems during a job run, ajob requested output to a second tape without writingdata to the first tape. In this case, volume 1 of thedataset will not be available, and subsequent attempts toread the data into the system can fail. (505001)

Tau-P Transform

• This process requires a CDP database with validX_COORD and Y_COORD rows. Running the processwithout a CDP database will fail with memory errors.(506788)

Tau-P Inverse Transform

• Traces output from this module will be flagged as tracesand geometry not matching the database. If the inputtraces do indeed match then the user must run TraceHeader Math to reset these flags. (507838)

Time/Depth Conversion

• This module may fail with a velocity file read error if thevelocity table is too large. The work-around is todecimate the velocity field and make it smaller. (509239)

Time Slice Input

• Vertical axis annotation will be incorrect if the horizontalaxis is inline. Possible work-arounds include usingINCREASING for axis increments when selectingINLINE_NO for “Horizontal axis”; use XLINE_NO for“Horizontal axis”; use only a single time slice; formultiple time slices use Ensemble Redefine based onthe 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 thanapproximately 3 million traces.



• This module may fail because it runs out of memory. Theamount of memory needed depends upon the number ofoffsets,cdp’s and horizons used. The best work around isto increase the value for “Window Interval”. This reducesthe number of horizons. (507791)

Trace Display

• See also Interactive Data Access.

• Trace headers created as character strings areannotated as zero values if displayed using the tracelabelling option. The Trace Display Label process, orthe interactive annotation button available from withinTrace Display can be used to create text annotation.(502516)

• When editing parameters, the Snap options can appearto provide erratic results on some datasets. (504118) Inaddition it has been noted that the Snap option can takean abnormally long time to run on data sorted byInline/Crossline. (503118)

• The Neural Net First Break Picker operating ininteractive mode does not pick zero crossing eventscorrectly. You are advised to pick on a peak or trough.(503611)

• The menu bar option to pick first break headers will beactive even if no valid first break parameter files areavailable for selection. In this case, a Trace HeaderMath used to set FB_PICK = 0.0 can be insertedimmediately before the display in order to create a validheader. (504122)

• The dx/dy function is labeled as ft/sec even if thedatabase is set to meters. (507881)

• Solaris Only: Using MB3 to add new layer does not workif you are running ProMAX on a Solaris 2.6 system anddisplaying to an IRIX 6.5.x system. No known workaround at this time. (508097)

• Selecting Grayscale as the Trace Display Mode in themenu does not bring up Grayscale as the color map.Users must select color64 from the Edit pull-down menuthen select the proper color table from the View pull-down menu. (302007)



View -> Edit colormap -> File -> Open -> greyscale.rgb

• Attempting to display a previously picked “Auto-StaticsHorizon” may not show all the picks. The parametertable is correct, the problem is in the display. (512949)

• First break picks will not display if the primary sort keyin Disk Data Input is SOU_SLOC. The work-around is tosort on something like FFID or SIN. (512964)

• This module may fail with an “Ensure failed... message if youtry to display too many samples. The work-around is todisplay fewer traces. (513104)

• Different results (worse) with NN Picking in TraceDisplay compared to batch program NN First BreakPicker. (511000)

• Trace scaling is dependent on the number of traces inthe 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 Displayand can have a noticeable impact on the resultingdisplay.

• It is possible to generate parameter tables in TraceDisplay that have negative start times. Some tools suchas Spiking/Predictive Decon will fail if one of these tablesis used. If you are making picks near time zero check theresultant table for negative values (513724)

• When Disk Data Output, or another output tool is usedin conjunction with Trace Display, Trace Display maycorrupt the last trace in the dataset if the Output Modeis set to “When Done” rather than “Immediate”. (513405)

• Solaris Expert 3D Graphics only: Trace Display doesnot refresh properly after other windows display over thetop of the Trace Display. (303915)

• Solaris: In Trace Display while picking layers, if you arerunning ProMAX on a Solaris systems and displayingback to an SGI the MB3 option to “Pick another Layer”does not function. (513792)



• The option to Exit/Stop flow does not work as expectedin flows containing multiple input steps. E.g. Disk DataInput - Trace Display - Disk Input - Velocity Analysis.Selecting Exit/Stop Flow in Trace Display stops theTrace Display but the Disk Data Input and VelocityAnalysis will then run. (514259)

• AIX Only: Selecting the MAX icon then a trace with MB1may compress the display of trace header values,making it impossible to see all values. The MB2 option isfine. The work-around is to change the CDE windowsetting to "Raise Window When Made Active" (515138)

• AIX Only: Pop-up displays, such as the list of parametertables will appear blank if displaying on systems withAIX versions earlier than those supported on version2003.0. (513777)

• Linux Desktop Only: When using the DX/DT optionMB3 should label the velocity on the screen. It does notthe work around is to use Shift + MB3. (130946)

• Linux Only: If you kill a flow from the notificationwindow it takes Trace Display about 30 seconds todisappear. (516062)

• IRIX Only: This module will abort if the maximumnumber 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 Solarissystem and displaying on a desktop using Exceed7.1.0.2 the MB3 pull down menu will not display.(149359)

Trace Header Math

• The following expression used to work and now errorswith a message about mis-matched parenthesis (lookslike a code change caused a non-fatal condition tobecome fatal, so the parentheses were being incorrectlyparsed. 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 allwork and produce the same results:

TMP=((sou_y-rec_y)/(sou_x-rec_x))/3.1415927



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 FFID’s have the same sou_x andsou_y locations, the trace edits called on these FFIDs areapplied only to the last FFID in the group. This will onlyhappen if the Trace Kill/Reverse list has been openedwith the parameter table editor. The editor attempts toperform a 3D resolve on the table causing the problem.(507685)

• If the primary key for editing traces, such asREC_SLOCS, becomes 8 digits or larger, adjacent tracesmay get edited. The work-around is to choose a primarykey with smaller numbers or use an IF block to sort offthe REC_SLOCS to be killed and use a universal kill.(509843)

• The requested trace editing key SKEY isn't in the trace header! Thiserror occurs when your parameter table has beencorrupted by the SKEY header.(512541)

work-around: Since tables with the SKEY header cannotbe read in, you will have to Create a new table selectingthe correct primary and secondary keys, thenexport/import the values from your old table into thenew one.

Trace Length

• This module does not correctly re-set the trace headersTLIVE_S and TFULL_S. Therefore it is possible thatapplying a re-mute after this module will give incorrectresults. 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 traceheaders may get corrupted. The work-around is to eithersave them to a user defined header or use a different sortkey, such as CHAN. (147861)



Trace Muting

• The re-mute option may not give correct results if themodule Trace Length has been applied previously. TheTrace Length module does not correctly re-set the traceheaders TLIVE_S and TFULL_S. Therefore it is possiblethat applying a re-mute after this module will giveincorrect results. The work-around is to use TraceHeader Math to manually re-set the headers. (507786)

• Applying a bottom mute to data that has already had atop mute applied will re-ramp the top of the trace. Inaffect, the ramp will be squared rather than linear.(507816)

• The option to “Apply where specified” does not workproperly. In general, using the option “Interpolate oversecondary key” will give the desired results. (508337)

Trace Sample Math

• When special characters (e.g. !,@,#,$,%,^,&,<,>,? etc) areincluded in the equation (e.g 3 + #4 + 5) the programassigns zero to everything after the special character (theresult from the previous equation is 3) The same is truewhen using brackets, Also everything after a space isignored. (514024,514023,514022)

• When numbers (e.g 1234) or mathematical expressions(e.g sqrt(16), 1 + 4) are written on the left side of theequation (e.g 1234=sine(sample)) the program outputsthe value of the left side of the equation instead of thevalue of the right side. In the last example the outputwould be 1234. This doesn’t happen when analphanumeric expression is used on the left side.(514026)

Trace Splice

• Problems have been encountered when attempting touse this process to splice poststack traces. If required,you should be able to work around the problem usingDisk Data Input and Disk Data Insert in merge mode,along with trace shifts and Trace Math operations.(504215)



True Amplitude Recovery

• The first trace processed through has anomalously lowamplitudes if the following conditions are true:

1) The WB_TIME trace header is present and contains anon-NULL value.

2) The spherical divergence option is selected using aspatially variant velocity function.

3) The dB/sec option is selected.

The work-around is to run Trace Equalization afterTrue Amplitude Recovery, or just kill/ignore the onelow amplitude trace. (513094)

Turning Ray Tomography*

• Multiple iterations of this process may inadvertently fillthe LIN database. You should delete previous LIN entriescreated by previous tomography runs (type TOMO) inorder to continue with further iterations. (504024)

TV Spectral Whitening

• If you are using the Time-Variant option, you need to setthe Automatic filter panel design for the Time Invariantoption to "Yes", then toggle back to the Time-Variantoption. Otherwise you will get the error “No input forspectral balancing frequencies” (135929)

UNISEC Create CGM+*

• When plotting color overlays, it will not be possible tolabel or profile header values that do not exist in theoverlay 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 whendisplaying the process history created via AutomaticGeneration or Existing History, and the history textcontains commas.

Error in line 213 column 13PARAMETER IS OUTSIDE LIMITSSHOULD BE BETWEEN 0.005 AND 1.000

If commas, parentheses, or leading blanks are required,



the text string should be enclosed in single quotes.(504603)

• There may be problems executing a flow which haspreviously been submitted or exited. Re-entering the flowthe “Headers to profile” can randomly deselect choicesmade from the pop-up menu. In this case, you will needto reselect choices and extent parameters. (504954)

• The sidelabel is blank if Display processing history isNone and AUTOHT=ON. Use AUTOHT = OFF. (504805)

• When requesting isovels above your plot, such asPROFILE,ISO(ISO VEL,D,,,,0,2000)...the isovel lines willplot, but there may be no corresponding annotation ofthe velocities. (505022)

• When using Headers to Profile or Headers to Label, if youselect headers from the pop-up menu and accept, youwill not be able to de-select all the options to return tothe ‘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 thedatabase program (XDB) select the SRF parameters andselect New - Project - CDP to manually project to theCDP domain.

• The flow will fail if more than three horizons areimported. (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 toput additional horizons into existing header words suchas UPHOLE. Then add UPHOLE to the remap headerslist in the UNISEC Create CGM+ menu. Then add a linelike this in the .par file:

HORIZON,UPHOLE(horizon3,,.03,4)

• If the sample interval of the seismic data is less than 1.0msec. the job will fail with this error:

NSAM= 5001 SR= 0.000 ITIME1= 0

*** Error,’RECL’ must be > 0



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 ashaving invalid trace numbers and geometries. Geometrydefinitions can be reloaded, or in necessary, the globaltrace matching flags overridden using Trace HeaderMath. (502294)

• The Copy routines for Area/Line/Datasets will attemptto copy dataset files to the same partition in which theoriginal files reside, including those found on secondarystorage partitions. If a disk partition is filled due toinsufficient space during this operation, the copy optionwill abort. (501703) If additional space is made, youshould specify a new output name, different from thename used in the first failed copy operation. (501494)

• When attempting to copy a Line which includes dataresiding on secondary storage, the copy will fail with amkdir error, as the new Area/Line directories are notavailable on the relevant secondary storage partitions.Assuming that the config_file includes those secondarystorage partitions, the directories can be allocated fromwithin ProMAX by first creating the new Line, and thentouching that Line by activating the Database Displaytool. (501854)

• For lines with OPF files spanning onto secondarystorage, copying that line into a newly created emptyarea can fail. Failure results from required area leveldirectories not being created on the secondary storagepartitions. The problem can be avoided by accessing thedatabase from the new area. (502474)

• Previously parameterized menus requiring selection of adatabase parameter may not list newly created databasefiles. Exiting the selection list without a selection resetsthe menu parameter to Invalid, at which time reenteringthe selection shows all possible database selections.(502593)

• The notification status for a flow which fails because theFlexLM license file does not contain a required feature



line is not captured by the UI notification mechanism.The actual error is captured in the relevant job.outputfile. If a flow simply fails to execute, you should checkthe job.output file for this type of error. (503510)

• If you have a dataset larger than 2 Gbytes and morethan 2 Gbytes worth of TRCn/HDRn files reside on thesame filesystem, then the MB2 history may report thewrong size for this dataset. This is most likely to occur ifthe maximum filesize in the config_file is set larger than2000 Mbtyes. It is strongly recommended that thisvalue NEVER be set larger than 2000. (507909)

• Problems running on <host> if <host>_PROMAX_HOMEis set. If you have defined in your .cshrc<host>_PROMAX_HOME set for various machines withtape drives, and HOST1 with HOST1_PROMAX_HOMEset, the UI hangs at start-up, never making it past thelogo 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 suppliedwhere host is the current machine this will supersedeANY PROMAX_xxx_HOME variables. So for examplePROMAX_DATA_HOME would be ignored in preferenceto <host>_PROMAX_HOME/data. IE the presence of the<host>_PROMAX_HOME hides thePROMAX_DATA_HOME and the default ’data’ is used.

Workaround: Put IF blocks into the .cshrc or start upscript to avoid setting <host>_PROMAX_HOME unlessit’s really remote.

• If you have a help file open and are viewing a job.outputat the same time, closing the job.output window will alsoclose the help file. The work around is to use thisenvironment variable. (513437)

setenv PROMAX_HELP_KILL_POLICY t

• Setting the environment variable TMPDIR will causeProMAX to create files in /tmp that do not getautomatically deleted. If you must use this variable thenyou should check the/tmp directory periodically.(303832)



• Using the “Print Flow” option on a flow containing any ofthe Seisworks I/O menus will cause a core dump.(303803)

• If you are using MB2 to check the status of a datasetwhile it is being written to disk it is possible that ProMAXmistakes this as a duplicate trace being created andstamps the dataset as not matching the database.(513095)

• Changing the batch queue priority from the ProMAX UIalso changes the priority for interactive jobs. This is fixedin version 2003.0. (125582)

• The User Interface may crash if you build a flow with atape input tool such as Seg-Y Input and your device.ttsfile has an unmatched end quote (“). (125386) The errormessage is:

Error in lisp call ’string concatenate’. Some are not a string.

• SGI Only: On SGI systems configured to run twomonitors as one X-Session, ProMAX will refresh screenstwice as much as it normally does. [email protected] for a possible patch. (129158)

• If you have your Areas sorted alphabetically and copy anarea, the Area at the top of the list is opened rather thanthe newly copied one. (130531)

• LINUX Desktop Only: Depending on the screen size andresolution the Product button may not appear on thescreen. This makes it impossible to change productsfrom the User Interface. The work around is to make thefonts in the ProMAX Xresource file smaller. (515979)

• When using Shift MB-2 in the ProMAX UI to refresh aprocess menu, the process will be enabled after therefresh irrespective of it’s status before hand. (516417)

• When using Shift MB-2 in the ProMAX UI to refresh aprocess menu, the process will be enabled after therefresh irrespective of it’s status before hand. (516417)

• The button on the User Interface under Config thatallows the user to have pop-up’s remain after the mouseis moved out is ineffective. (516862)



• When you print flows with Menus like Trace HeaderMath that allow you to type in parentheses. They do notshow up in the output HTML file. The work-around is tomanually edit the HTML file. (144140)

Velocity Analysis

• This process may not display pre-existing functions forediting on some lines, due to differences in theresolution of X,Y coordinates derived from the inputtable as compared to the actual CDP X,Y values found inthe database or trace headers. This will most often arisewhen using the output from the DMO to Gathers 3Dprocess as input to Velocity Analysis. In the case of 3DDMO gathers, CDP database coordinates can betransferred to the trace headers prior to VelocityAnalysis. (503390) If this problem arises in a moregeneral case, a more lengthy work-around using theimport and export of information to modify the velocitytable coordinates can be provided by contacting asupport representative. (503234)

• This module does not honor the trace headers TLIVE_Eand TFULL_E when calculating the semblance. Instead ithonors the global trace length. Typically, this will only bea problem if the data was modified by modules such asTrace Length or Time/Depth Conversion. (508600)

• If the output velocity table name was made by choosingthe “ADD” option, this module will fail with a signal 11 orSIGBUS 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 thenumber of precomputed semblance traces, you will getan incorrect velocity scale. The work-around is to eitherreduce the number of semblance velocities or lengthenthe traces. (513075)

• Users have reported that at analysis locations whoseoffset distribution are limited, the display gain in thefirst stack panel may be unusually high. The cause hasnot been determined at this time. (513347)

• Setting the "Contrast Power Factor" in the "SemblanceParameters" to a non-whole number may cause redhorizontal bands to appear in the semblance display.(513631)



• On some datasets if displaying horizons the display caninvert. I.e time 0 is at the bottom of the display. Anypicks made on this display will be fine. The work-aroundis to turn off the horizon display. It may also be causedby displaying horizons on the dynamic stack panel.(513482)

• If you select a new velocity table from the “File” menu inthe Velocity Analysis display and save picks to that fileyou are not able to edit or use the table. (513810)

• If the parameter ’Semblance Width’ is changed withinObject Visibility of Velocity Analysis a subsequent zoomdoes not show a right scroll bar. The work-around is toeither alter the semblance within the menu, or zoom firstto get a scrollbar, then change the semblance width withObject Visibility. (515427)

• There is a limit of 19 horizons that can be displayed inVelocity Analysis. (514304)

• Solaris Only: Using the Snap Once option pulls all thepicks up, and multiple uses of this option continues topull picks to the top of the semblance tile. (130464)

• Setting "stretch mute = 0.0" to disable is reallyequivalent to setting it to 1000% rather than totallyallowing stretch to "zero time" as is the case in ourcurrent NMO module. (148528)

Velocity Analysis Precompute

• This module will fail if the number of semblance velocityfunctions is greater than the maximum fold set in theSuperGather formation menu. The work-around is toincrease the value for fold in the menu. (513120)

• When running Velocity Analysis after precompute, thesemblance display will appear compressed in time if theflow has menus from versions older than 1998.6.(513579)

Velocity Manipulation

• Smoothing a velocity table may drop the functions at thefirst and last CDP’s. The work around is to input thesmoothed table back into Velocity Manipulation andexplicitly define the output range. (514444)



Velocity Viewer/Point Editor*

• If you specify a beginning and end time to edit, thevelocity displayed will honor those constraints. However,editing a velocity function creates a function whichstarts at zero time. Similarly, using this process toconvert to a different type of velocity file outputs a fieldfor the entire time range of the data. You should QC theoutput velocity files prior to using in subsequentapplications. (502497)

• The velocity field smoothing option introduces adiscontinuity at the bottom the velocity field. Thisdiscontinuity happens at about one-half of the temporaloperator up from the bottom. The work-around is toperform this smoothing in Velocity Manipulation orVolume Viewer Editor, or using the menu parametersspecify 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 onlyfunction. If this is not done, turning on the VolumeViewer/Editor PD icon will not activate the MB1 SendTrace Location icon. (504963)

• It has been shown that adding horizons adds to theprogram allocated memory size, but removing thosehorizons does not decrease the allocated size. Theprogram then allocates more memory if horizons,including those just removed, are added. (507431)

• In 2D, the mouse button help for “Smoothing andGridding” is confusing. It should read Number of CDP’sand Time in Msec. (507989)

• Specifying surface coordinates of xy and trying tosmooth using edit-grid/smooth volume generates thesame velocity for all inlines and crosslines (infinitelysmooths in the spatial domain). The work-around is tospecify ILN/XLN as surface coordinates and smoothbased on inlines and crosslines. (510876)

• The map view display sent to a different machine doesnot show the gather locations. If the map view display issent to the same machine where ProMAX is running, thegather locations display properly. (510439)



• It is possible that by using the defaults presented in thegridding/smoothing spreadsheet, ProMAX will generatea table with negative CDP values. This will causemodules such as Kirchoff Time Migration to fail with aSignal 11 error. The work-around is to input realistic valuesin the spreadsheet. (512026)

• Attempting to limit the 3D volume by ILN:XLN maygenerate an error like this:

Fatal error occurred on 21-Oct-99 at 08:51:01Message is: User depthcoordinate limits are invalid.

The cause has not yet been determined. (512176)

• Using the option to “Save as - Other Horizon” does notwork. The work-around is to output the horizon as aninterpreted horizon. Then export to ASCII and import theASCII file as an “Other Horizon”. Perform the followingsteps. (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 forprimary key.

4. Import the ASCII file you exported

• When you use CREATE to make a default table, valuesfor NULL are 0.0 and 1000.0. Should be 1, otherwisewhen 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 onepoint. E.g. When you are picking horizons and creating amodel in pieces you may have only one point on ahorizon that makes it from the first set of CDP’s youcreated the model for to the next one. If that is the case,



the velocity field and background data flip upside downwhen you open the horizon. (513281)

• The vertical crosshair always stays on the first CDPlocation no matter which CDP Velocity Analysis is onwhen interacting with Volume Viewer/Editor. (125538)

• Horizons must extend beyond a single inline to bevisible. (128156)

• Problems have been reported in the Volume ViewerEditor when geometries are created with initialcoordinates of X=0, Y=0. The work-around is to biasthese values by some non-zero value. (134308).

• Horizons picked using this module will not be visibleusing either Trace Display or Velocity Analysis. (134864)

• You can read in an interpreted horizon (IHT) and tell VVEto save it as an Other Horizon (HOR) but it will not showup in the HOR table. This works for 2d but not 3D.(147960)

Well Log Input

• The program and documentation allow for a dump of theLIS and LAS formats by specifying file number zero inthe menu. The menu does not allow for input of filenumber zero. This can be fixed by changing thetype_desc descriptor for the FILENUM parameter in thelog_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 LASStandard logs, the Start, Stop and Step lines should notinclude spaces between the descriptor and the units ofmeasurement. (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 wherethe lines are “wrapped”. The work-around is to edit thefiles so that each depth step and its mnemonics are onecontinuous line i.e. unwrapped. (512622)

• Although the LAS specifications only require a ~ (tilde)and the first letter of the section to identify it ProMAX



requires the full description. E.G. ~VERSIONINFORMATION rather than simply ~V. (600569)For more info about LAS specifications, checkhttp://www.cwls.org/las_info.htm

• Due to changes made in the LAS format from version 1.2to 2.0 certain fields such as units and well name will notread properly. (147324)

Well Log Synthetic Match Filter

• The match filter can fail or output a dead filter trace ifthe MB3 stretch/squeeze option is used on sampleslocated above the anchor after using MB1 to movelocations. (503563)

Western 4 Input

• An option to read variable length records is available fordisk files. A similar option is not available for tapedatasets. The process can fail with an error similar to thefollowing: (504109)

I am lost, attempting to synchronize, Record: x Trace: y

• Using the menu to override the reel header for traceheader length causes a signal 11 error. (511945)

XY Graph

• The menu allows inputting negative numbers in the bindistance (dx and dy), and will initiate a graph with a binspace. The application will core dump when attemptingto manipulate this grid. Do not input negative bin sizes,you should utilize the origin and azimuth valuesappropriately to position the binning grid. (501378)

• This process can fail with the error: Cannot retrieve data orwith an error in the UNIX window related to.../agC/Arra.c if adatabase with all NULL shot station values isencountered. (502973)

• The alternate domain plot does not work if midpointshave not been assigned. (502498)

• Lines which are due North-South or East-West canspawn a display interface in which the display scale iscreated in minute increments, leading to apparentdisplay problems. Adding a small amount to one of the



relevant X or Y coordinates will circumvent this problem.(503700)

• After importing$PROMAX_HOME/port/misc/misc_files/3d/marine_unkooa andcreating a basemap, and highlighting the contributors tothe trace domain: Select all (MB2) occasionally blowsaway the XYGraph. (507378)

ProMAX VSP Problems

3-Component Hodogram Analysis

• The program assumes that the maximum value in a gateis a peak. If the maximum is a trough and you havepicked on a peak, the output will be 180 degrees off.(503259)

• When VSP data is sent through this process, 5 traces areoutput for each 3 traces input, or for each VSP FFID. Alloutput traces are present except for the last trace of thelast 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 verticalaxis scales correctly to the input samples. You canrezoom the window, or more effectively, use a scaler inTrace Math going into the analysis tool to set the inputamplitudes larger. (504429)

• The labels H1,H2 in the upper right corner of the displayare the opposite of what they should be. (508717)

• Users have reported this module generating theta andphi polarization angles that make no sense. It issuggested users check the output listing closely forangles that are too large. (513376)

VSP Report

• Attempting to generate more than 7 reports causesformatting problems on the output. (515024)

• This module fails with a segmentation fault in version2003.0 (516114)



VSP/CDP Transform

• The program uses all the shot and receiver X,Ycoordinates to compute a slope and intercept of a line.The transformed data will be imaged along this line inmap view. If there are duplicate shot and receivercoordinates, an improper line gets computed, and thejob may possibly fail. (505491)

• This module may generate spikes if the datum is belowthe source elevation(513565)

VSP Geometry Spreadsheet


VSP Geometry Spreadsheet

• The values in the X and Y columns are destroyed whenStation column is filled. It is not required to fill in thiscolumn. (507633)

Vel Table From VSP

• Although the option is given in the menu to limit theoffsets used to compute the velocities, this range is notbeing used. (507635)

ProMAX MVA Problems

CRP Gather Raytracing*

• Ray tracing files cannot span disks correctly, resulting inerrors such as:

Unix error - no such file or directoryError opening file: .../xxxxxxxxTRHDCould not open table xxxxxxxxTRHD

work-arounds: There are 3 possible work-arounds: 1) In aUNIX window physically move the file to a secondarydisk that has free space and rerun the raytracing. 2)Rerun raytracing outputting the file onto the primarydisk. 3) Output to primary and then physically move thefile to a secondary disk with free space available, andcreate a link from the primary to the secondary location.(504847)



Extract 2D Table from 3D

• When you select Stacking Velocity for input this modulewill also generate an inaccurate interval velocity in depthtable. (513138)

• When running jobs from the Flow Chart you will get anerror stating that super_exec.exe is not found. The work-around is to either make a link or simply copy superExecto super_exec.exe in the $PROMAX_HOME/sys/exedirectory. (303744)

Horizon Manipulation

• You are unable convert Other Horizons to depth inProMAX MVA. There are format discrepancies betweenSeisWorks 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 toInterpreted Horizon in Time (IHT).

• If you use the option to decimate horizons this modulewill either fail with an error or complete normallyoutputting the same number of points as the inputhorizon. (511598)

• The workflow to bring in 3D SeisWorks horizons andthen add them together using Horizon Manipulationdoesn’t work at present. The work-around is to add the 2horizons 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, theassociated colors or seismic traces can be severelydistorted. The problem can be rectified by scrolling outand then back into the analysis area. (503345)

• Saving RMO picks in IHVA through the pull down menudoes not give the same results as using the Save icon(floppy disk picture). When you bring up both IHVA andthe MVA Xsection Window, send a horizon to IHVA,pick RMO, save using the pull down menu, and thenproceed to send the next horizon to IHVA, a popupappears saying the picks are not saved. When the saveicon is used the popup does not appear when the next



horizon is sent to IHVA. In either case, the RMO picksare actually saved. To save time, we recommend usingthe Save icon. (503959)

• IHVA automatic picker will not pick across gaps in a 2Dline. This causes tomographic inversion to produceinterval velocities with NAN values from the beginningtime to the time of the last horizon. The work-around isto either create horizons on each side of the gap, ormanually 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 plottedcorrectly and the time picks are no longer on thehorizon. If you iconify the plot and re-display, the plotwill be correct. (512537)

Interactive Horizon RMO

• This module is not displaying interpolated picksproperly. (144411)

MVA Flow Chart*

• The dialog box for selecting tables or datasets does notlet you create new names. To create a new name, youshould return to the general ProMAX interface. (503437)

• The Flow Chart UI contains the correct template for theVelocity Analysis Precompute. However, the VelocityAnalysis Precompute menu in the MVA flow builderitself contains a link to an incorrect process. TheProcesses.list file in the $PROMAX_HOME/port/menudirectory should be modified, substituting vaprecom forthe existing vabatch. (506089)

• SGI Only: You cannot exit the flowchart. The parmdbprocess continues to run and may try to use 100% of aCPU. You must kill the flow from the Notification windowor 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 ofhorizons being reset to 1. (503402)



MVA Xsection Window*

• When you run MVA Xsection Window in time, displayindividual time horizons, and save them to a HorizonGroup, a Depth Horizon Group table (HGP) is createdrather than a Time Horizon Group table (HGT). Thework-around is to rename or copy the HGP file to anHGT file. (503727)

• IRIX ONLY: This module may fail with some versions ofIRIX. 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 arefilled by other jobs before the TT files have time to spanto another disk. You can try lowering the size of the TTfiles by setting the environment variable TT_FILESIZE =nnn (nnn = number of mbytes). Or setting theenvironment variable TT_ZERODISK = y will actuallygrab the required disk space prior to execution. (504757)

• The User Interface crashes when this menu is selected.Contact [email protected] for a new menu. (516300)

• Will not allocate more than 2 GBytes of memory. [email protected] for a possible patch. (516481)

• Will not allocate more than 2 GBytes of memory. [email protected] for a possible patch. (516481)

• The output may be all noise if the job is run in Volumemode and the aperture in the TT Generator is set tosome small part of the survey. The work-around is to setthe grid definition to the whole survey. (137855)

• There is an option in the menu to "Output Random lineTravel Times". If you say Yes the menu asks for a pointfile. There is no mention of this line in the docs andthere is no information on what a point file is supposedto contain. The solution is to create a simple ASCII file.The first line is the number of points (n, which define therandom line), followed by n lines with the IL and XLpositions of the node. (143187)

n



IL1 XL1IL2 XL2

Software Development Problems

SDK Documentation

• 2 character module names are not processed in exectools_to_delete file. You may however, manuallycomment it out of the generated toolcall.f file. (512086)

Make System

• IRIX Only: Attempting to link a module will generate anUn-resolved text symbol error. (147596)Work-Around:

cd $PROMAX_HOME/sys/lib64ln -s ./libCio.so.1 ./libCio.so

ProMANAGER Problems

• Proloop is not interpreting the ’&’ in Disk Data Inputfrom another line. When passed "area & line & dataset",proloop is supposed to translate this to populate thepop-choose for area, line, and dataset in a Disk DataInput menu reading a dataset from another line.Currently, it is passing the input string verbatim. Theoriginal character was a pipe ’|’, but this was changed toa ’&’ to accommodate peculiarities of MsAccess. The pipestill works, but the & doesn’t. (509963)

• Submitted flows fail to honor product paths in .promax.The 1998.6 version of ProManager does not use multiplesearch paths from a user’s .promax file during jobsubmission. (512935)

work-around: Functionally equivalent to defining pathsin a PROMAX_DOT_PROMAX_HOME or$HOME/.promax file can be arranged by setting any orall of: PROMAX_SYS_EXE_HOME,PROMAX_PORT_MENU_HOME,PROMAX_PORT_HELP_HOME,PROMAX_PORT_MISC_HOME in the ProManager jobsubmission environment. These variables will need to beadded to the environment catalog first.



• Problems parameterizing multi-level menus like CreateCGM Plotfile. Menus within menus cannot beparameterized from ProManager in one pass. Somemenu options which are complicated pop-ups or whichcall programs directly will not work at all. (509880)

Partial work-around: From the ProMAX UI, edit thetemplate, open the submenu for which substitution isneeded and save the template. Then select forsubstitution in ProManager the template table. Edit thetemplate again in ProMAX UI and save with a differentsubmenu open, re-access in the ProManager UI.

• Expression parsing error. Using Template or Replicatetables in ProManager to read a dataset from anotherarea/line/ can produce a parsing error. This can happenwhen the parser does not parse concatenated variablescorrectly. (513166)

For example where replica.Name is a string andreplica.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 tableand using the String fill tool.

Another suggestion would be to avoid these types ofnames. 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 isnecessary to add the variable $HOME to theenvironment in ProManager (that is the [Env] icon in theleft toolbar). This is not possible. (513167)

• The aar_promax and ProManager do not communicatecorrectly using LP Queues (AIX). The aar_promax andowner.jar do not correctly set the USER environmentvariable needed by scripts called in their respectiveremote environments. (513145)

• If the file .promax.proloop does not exist as directed byPROMAX_DOT_PROMAX_HOME, you cannot start theProMAX UI from ProManager. A simple ’touch.promax.proloop’ solves the problem. (512141)



• The job status option to display available disk spacedoes not report the available space inPROMAX_SCRATCH_HOME. (513585)

• The auto-QC and auto-submit features will be disabledon AIX for ProManager 2003.0. This has been noted inthe documentation. (514273)

• The version of MySQL distributed with ProMAX 1998.6may not install on some IRIX 32 bit systems. (303592)

• Linux Only: User cannot kill a job from the ProManagerinterface. The error message is: /usr/bin/kill not found(516203)

• Solaris Elite and Creator 3D Graphics only: TheProMAX explorer window is not refreshing properly whenyou use the scroll bar. (304799)

• Linux Only: Chaining of flows does not work. Only theflow executes. (516192)

• IRIX Only: Set Home option does not work. (126721)

• If a chained flow has been built or executed before, itignores the host, environment, and queue you specifiedfor the flow you run before the chained flow. It insteadruns in the environment specified for the previousexecution of that flow. Work-around: Rebuild the flowusing the host, and environment, and queue you wish torun in when the chained flow is executed. (139274)

• If you have a template and you copy and rename thetemplate within the same area and use the new renamedtemplate to build a flow, the flow that is built in ProMAXhas the original template name not the new name. Thisdoesn’t happen if you copy from one area to another,only within an area. (305473)

• ProManager will allow the creation of duplicate Area andLine 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, thelabelled tape mount request does not post error messageto (re)mount. (509299)

If you mount again the following message will appear in



the job.output:

Expected VSN and the observed VSN read from the input volume do notmatch.

This error condition has no override option.

• Delete tape dataset ALWAYS prompts for catalog DSNdeletion when deleting from the Area or Line level, even ifthe 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 anexternal VSN list and the wrong labeled tape is mounted.This tape happens to be a library tape and it wasoverwritten when the operator chose to override theerror. 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 environmentvariable is not set or is set incorrectly.

work-around: The possibility of this happening may beavoided by setting the configuration flag: AEEJ

• Modifying TopCat attribute MPOOLNAM does not addadditional volumes to the media pool. (510442)

• Java.config from Solaris REMHOME install has incorrectport (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 1111for Opcon, this should be 1099 by default.

• Convert_device.txt2tts script is setting REMHOMEimproperly. When converting an existing device.txt thathas and ’fclient.exe’ stanza to be converted to aREMHOME, a ’sys/exe/’ will be appended to the



REMHOME path. You will want to delete this from yournew device.tts. The REMHOME setting is similar to aPROMAX_HOME setting which does not include asys/exe’ in the path. (513332)

• Config_file explanation for device.tts line is unclear.When editing the ’device file’ stanza in thePROMAX_HOME/etc/config_file, either your HOMEdirectory or PROMAX_HOME/etc will be prepended toyour device file name. Typing an explicit path will notwork. (513331)

• DEVICE.TTS: If the hostname entered in the device.ttsfile does not match the results from the commanduname -n ProMAX will return an error:

Unable to make socket connection between client and ProMAX

This is most often caused when fully qualifiedhostnames are used. (513479)

• In the TTS online Documentation Basic Configurationsection, the description for TMHOST is’TMHOST="terminal:0.0" This is the location to displaythe mount messages issued for this device. If this is notsupplied, mount message are sent to the location of theUser Interface where the job was submitted. If a user isusing a remote tape drive, the default mount locationonly 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 machinewith the tape drive attached. (513523)

• SGI ONLY: The REMOTE_TAPE_HOME /port/bin/scripts for TAPE_REQUEST and TAPE_NOTIFICATIONlook for ’hostname’ and ’rsh’ under /bin rather than’/usr/bsd/hostname’ and ’/usr/bsd/rsh’ which isstandard on most SGI installs. The work-around is toedit these scripts to match the correct paths on yoursystem. (513363)

• Remote Tape AIX only: In the case where the remote tapedevice is attached to an AIX system that does notcontain a full ProMAX installation you may get thefollowing error message when trying to access the device:

ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM



We believe this is due to a library missing from theremote tape distribution The work-around is to do a fullProMAX AIX install or at least the ../sys/lib directory.(303623)

• ShowCat: The documentation does not explain that inorder to run this program $PROMAX_HOME/port/binand $PROMAX_HOME/sys/bin must be in the userssearch path. Otherwise users will get an error sayingpromaxpath not found. (513506)

• The NREW (no rewind) parameter in the device.tts file isnot being honored. Use NREW + NUNL to bypass therewind and eject behavior. (514411,515409)

• SGI Only: The "Process Killed" message is NOT comingto the Opcon Tape Notification window when user kills ajob from the ProMAX UI "Notification Window". (136556)

• When a user cancels a job from the ProMAX UI, theProcess Killed message does not show up in opcon. Thework-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-fileunder $PROMAX_HOME/port/misc/remote_tape. Doesnot work. Contact [email protected] for the correctversion





landmark known problems

Documents

problems specific

discovered problems

promanager problems

promax vsp problems

promax mva problems

problems foundafter

known problems icon

d psdm problems