In SAS 9.4 TS1M5, when you specify a high value for the PAGESIZE= SAS system option, you might encounter the following issues:
- The available memory is exhausted.
- Excessive CPU time is used.
- The output might be incomplete even though the job completes with RC=0.
When you run a PRINT procedure step that uses PAGESIZE=MAX and does not define sufficient REGION (REGION=64M is defined in this example), you might see messages similar to the following:
NOTE: Cleanup disabled for task PRINT since $RTHIEF=0
NOTE: There were 860977 observations read from the data set WORK.SEARCH.
NOTE: The PROCEDURE PRINT printed page 1.
NOTE: The PROCEDURE PRINT used 4.38 CPU seconds and 55145K.
When you run a PROC PRINT step with the same conditions as above except that you set REGION=256M, you might see the following messages:
NOTE: There were 860977 observations read from the data set WORK.SEARCH.
NOTE: The PROCEDURE PRINT printed pages 1-53.
NOTE: The PROCEDURE PRINT used 148.85 CPU seconds and 167251K.
When all the memory has been exhausted, you might encounter other symptoms not related to PAGESIZE, such as the following error:
ERROR: Unable to allocate sufficient memory. At least 3K bytes were requested, but only 0K were available. You must either increase the amount of memory available, or approach the problem differently.
There are two possible circumventions:
- Increase the REGION= setting for the job.
- Reduce the size specified for the PAGESIZE= SAS system option.
Two hot fixes must be installed for the fix to be complete. If both hot fixes are not installed, you might get an abnormal termination. Under z/OS, this issue might surface the following error:
ERROR: System abend 0C4 occurred in module SASODS function append_recs at offset 0001B4.
Note: The offset might vary.
For this issue, ensure that you install both hot fixes. When you click the link for the hot fix download on the Hot Fix tab, the downloads page contains a note that states that you must also install an additional hot fix.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | N/A | Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M5 | |
Microsoft Windows 8 Pro 32-bit | 9.4 TS1M5 | |
Microsoft Windows 8 Pro x64 | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise x64 | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M5 | |
z/OS 64-bit | 9.4 TS1M5 | |
Microsoft® Windows® for x64 | 9.4 TS1M5 | |
z/OS | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro x64 | 9.4 TS1M5 | |
Microsoft Windows 10 | 9.4 TS1M5 | |
Microsoft Windows Server 2008 | 9.4 TS1M5 | |
Microsoft Windows Server 2008 R2 | 9.4 TS1M5 | |
Microsoft Windows Server 2008 for x64 | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Datacenter | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Std | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Std | 9.4 TS1M5 | |
Microsoft Windows Server 2016 | 9.4 TS1M5 | |
Windows 7 Enterprise 32 bit | 9.4 TS1M5 | |
Windows 7 Enterprise x64 | 9.4 TS1M5 | |
Windows 7 Home Premium 32 bit | 9.4 TS1M5 | |
Windows 7 Home Premium x64 | 9.4 TS1M5 | |
Windows 7 Professional 32 bit | 9.4 TS1M5 | |
Windows 7 Professional x64 | 9.4 TS1M5 | |
Windows 7 Ultimate 32 bit | 9.4 TS1M5 | |
Windows 7 Ultimate x64 | 9.4 TS1M5 | |
64-bit Enabled AIX | 9.4 TS1M5 | |
64-bit Enabled Solaris | 9.4 TS1M5 | |
HP-UX IPF | 9.4 TS1M5 | |
Linux for x64 | 9.4 TS1M5 | |
Solaris for x64 | 9.4 TS1M5 | |
*
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.