Product: IESX
Version: 10.2
Application: CPS-3 Link
Search Type: FAQ
Topic:
Why is IESX to CPS-3 Link hanging up?
Description:
Solution:
The IESX to CPS-3 Link is known to take time for large 2D data sets and the
workaround is to run the link from standalone. Please refer to the section on
'How to invoke stand-alone CPS-3 Link'. Here are some notes regarding this
problem and possible workarounds.
1. If the CPS-3 Link appears to hang or aborts after hanging,
check the following possible reasons:
a. Sending across interpretation where some or all of the
interpretation does not have location information.
Interpretation outside of x,y locations should be removed.
b. Sending across seismic locations which have no navigation
information. (The workaround here is to copy the locations
which have no navigation data to another dummy survey,
then removing them from the survey you want to transfer.)
c. DSL's that have mixed protection for files. (Try setting
all files in these directories to protection = 666.)
d. 2D survey interpretations transfer much slower.
Make sure to allow enough time for the link to
complete. To obtain the fastest response, you
may want to try the stand-alone CPS Link.
e. Sending across interpretation attributes that do not
exist.
f. Corrupt data paths to CPS-3 projects. Check that
project paths in the following files are correct:
The user's file "project.lst" in their ~/.cps directory
The user's file "prj_pth.lst" in the project directory
to which the IESX data is to be sent.
Note: If you can't figure out why something doesn't transfer,
do "setenv CPSDM_LOG on" in the xterm from which the
CPS-3 Link (IESX) is invoked. Real-time status info will
appear in this window during data transfer, and can be
analyzed for possible solutions.
2. If a transfer is very slow, the local network connections
may be the cause.
Last Modified on: 10-FEB-99