User`s guide

9030971 E17 SAS Exports

5-3

SAS Export Errors

Leftover SAS Processes

When an export fails, it is possible that a child process running SAS still

remains in the background. This process should be killed and the output data

set(s) and the log ﬁle(s) should be examined for completeness (see Checking

Export Output on Page 4-7 and SAS Log Files on Page 5-3).

Incomplete impoinfo File Update

If two or more exports are running concurrently, it is possible but unlikely,

that they will attempt to write to the impoinfo data set at the same time. If

this should happen, only one export process will obtain the write lock on the

impoinfo data set and be able to update it. The other process will not get a

lock, and will not update the ﬁle. There are no indicators of this problem (e.g.,

error messages) unless you create a SAS log ﬁle and examine it for error

messages (see SAS Log Files on Page 5-3).

The solution to this problem is to run multiple exports in succession rather

than concurrently. See SAS reference material on the FILELOCKS system

option in the UNIX environment.

SAS Log Files

If examination of data sets and export log ﬁles does not indicate the source of

an export problem, you can create a SAS log ﬁle by setting the environment

variable, SASLOGFILE, to the full path of the desired SAS log ﬁle prior to

executing SDE. When SDE executes SAS, it will write the results of the

export, including error messages, to that ﬁle. The resulting log ﬁle can then be

checked for error messages, etc. (This mechanism works for exports executed

with the Export Now command only.)

It should be noted that while the SASLOGFILE environment variable is set,

the Data Export SAS process will continue to append runtime information to

it. The resulting ﬁle can become large.

SAS Work Area

If the SAS work area (e.g., /tmp) becomes so full that SAS cannot allocate

adequate space, it is possible that the child process running SAS will hang

without any messages or indications of the problem. Under this circumstance,

the dataexp task will also hang, while waiting for the child process running

SAS to exit. Therefore, it will be necessary to cancel the dataexp task and

clean up any temporary ﬁles left over.