Problem Note 17038: Limited support in SAS® 9.1.3 SP4 for DSNTYPE=LARGE data sets when running under z/OS Releases V1R7 and later
 |  |  |  |  |
To create a direct access bound library that resides in a DSNTYPE=LARGE data set, you must externally allocate the library data set with the DSNTYPE=LARGE parameter, as shown in the following example:
//jobname JOB acct-info
//STEP01 EXEC SAS
//LARG01 DD DSN=dataset-name,DISP=(NEW,CATLG),
// UNIT=DISK,SPACE=(CYL,(5000,5000)),DSNTYPE=LARGE
//SYSIN DD *
data larg01.memb01;
do obs = 1 to 200000000;
output;
end;
run;
/*
//
Once you create a library using the DSNTYPE=LARGE parameter, you can
assign it via either a LIBNAME statement or an external allocation (Job
Control Language (JCL) or the TSO ALLOCATE command), the same as any
other direct access bound library. No additional allocation options are
required.
Compatibility Issues:
A prior release of SAS cannot process a library created using DSNTYPE=LARGE. Any attempt to do so will result in a S213 error; however, SAS will recover from the abnormal ending and will issue an appropriate diagnostic message.
These libraries cannot be processed under z/OS operating system releases V1R6 and earlier, even at the required level of SAS maintenance.
Note that this hot fix does not provide DSNTYPE=LARGE data set support for the following:
- external files (for example, those processed via the FILENAME statement, and so on)
- sequential access bound libraries (tape format) on disk
- V5SEQ libraries on disk
- the DLTEST procedure
- LIBNAME statements and LIBNAME functions.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | N/A | z/OS | 9.1 TS1M3 | 9.2 TS1M0 |