In SAS® 9.3, when the ODS output destination is full, the task goes into a loop.
This problem can be identified by the following conditions.
The SASLOG shows ERROR messages like the following and the task is still clocking CPU usage:
ERROR: Out of space detected at CLOSE for file QSAS0000. The file may not have been saved or may be incomplete.
ERROR: Out of space writing to file Out of space detected at CLOSE for file QSAS0000.
The file may not have been saved or may be incomplete.
ERROR: Fatal ODS error has occurred. Unable to continue processing this output destination.
From the job, log messages such as the following also indicate a space problem:
11.53.18 JOB07659 IEC032I E37-04,IFG0554P,MW$#D99,SAS,QSAS0000,7014,SM7191, 166
166 ods.output.dest.dsname(member)
11.53.18 JOB07659 IEC032I E37-04,IFG0554P,MW$#D99,SAS,QSAS0000,7014,SM7191, 168
168 ods.output.dest.dsname(member)
11.53.18 JOB07659 IEC217I B14-0C,IGG0201Z,MW$#D99,SAS,QSAS0000,7014,SM7191, 170
170 ods.output.dest.dsname(member)
In the above, ods.output.dest.dsname(member) is the name of the output destination file.
If the problem is not noticed right away, the task might fail due to CPU time-out.
13.32.45 JOB07659 IEA995I SYMPTOM DUMP OUTPUT 949
949 SYSTEM COMPLETION CODE=EC6 REASON CODE=0000FD1D
In SAS®9, due to threaded kernel architecture, SAS runs as a BPX thread. Certain system failures
arise as system abend code EC6, and the Reason Code identifies the specific reason. A Reason Code
FD1D is a CPU time-out.
To circumvent the problem, increase the space allocation for the ODS output destination file.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.3 TS1M0 | 9.4 TS1M0 |
Z64 | 9.3 TS1M0 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.