User`s guide

Minimum Requirements for Exports to SAS Data Sets
SAS Exports Data Export User’s Guide
5-2 Version 5.0rev1
Minimum Requirements for Exports to SAS
Data Sets
To export SPECTRUM data to SAS data sets, the SAS core components must
be installed and executable from the machine from which the export is run.
This does not imply that the SAS core components must actually reside on the
machine itself, merely that they be executable from that machine.
SAS Export Errors
There are several indicators that may arise during an export which point to
incomplete SAS exports or other SAS-related problems. The following sections
discuss these indicators and suggest some solutions.
Leftover Pipes
On the Solaris platform, the export process uses UNIX-named pipes to send
SAS source code and data to the child process running SAS. These pipes are
zero-length files created in the output directory, with names that are a
combination of the literal ‘ctron’, the type of export, and the child process id
(e.g., ctronmt_1234, ctronsta_4543, and ctroneve_35875).
These pipes are removed when a successful export is completed, and under
most error conditions. Situations may arise, however, when they are not
removed. Leftover pipes indicate an unsuccessful export. Output data should
be examined, as well as the log file, for indications of errors (see Checking
Export Output on Page 4-7).
Leftover Lock Files
With the release of SAS 6.09, the default for the system option FILELOCKS is
FAIL (The default for SAS 6.07 is NONE). Thus, when a data set is opened for
output, a lock is placed on the data set. This shows up as a file with an ‘.lck’
extension on the data set name. If, after an export, one or more .lck files
exists, one or more of the exports was incomplete. As with leftover pipes, you
should check the output data set(s) and any log files created to determine
where the problem arose (see Checking Export Output on Page 4-7 and SAS
Log Files on Page 5-3). The lock file(s) should be removed and the export
rerun.