SAS(R) 9.1.3 Companion for z/OS

Using SAS Data Libraries Direct Access Bound Libraries 41
These SAS statements use the V9 engine to create a library named
prefix.STUDY1.SASLIB where prefix is the value of the SYSPREF system option. The
amount of space allocated to the library is derived from the value of the FILEUNIT,
FILESPPRI, and FILESPSEC system options. SAS automatically sets the appropriate
DCB attributes. In an interactive session, it is possible to omit the DISP option; in this
case, SAS assumes a status of NEW and prompts for the value of the normal disposition.
The following example creates an external assignment using JCL:
Example Code 2.2 External Assignment Using JCL
//jobname JOB ...
// EXEC SAS
//STUDY DD DSN-USER489.STUDY1.SASLIB,DISP=(NEW,CATLG),
// UNIT=DISK,SPACE=(CYL,(200,50)),DCB=DSORG=PS
data study.run1;
...
run;
Assuming that the ENGINE system option uses the default of V9, these SAS
statements create a library named USER489.STUDY1.SASLIB.
As in the previous example, SAS automatically sets the appropriate DCB attributes.
Note that it is not necessary to specify the LIBNAME statement.
The following example explicitly specifies the V6 compatibility engine:
Example Code 2.3 External Assignment Using JCL to Specify a Compatibility Engine
//jobname JOB ...
// EXEC SAS
//HIST DD DSN=USER489.HISTORY1.SASLIB,DISP=(NEW,CATLG),
// UNIT=3390,SPACE=(CYL,(10,10)),
// DCB=(DSORG=PS,BLKSIZE=27648)
libname hist V6;
data hist.analysis;
...
run;
Like the previous JCL example, this example uses external assignment; however, the
V6 compatibility engine is explicitly specified in the LIBNAME statement. This library
can now be processed by SAS Version 6. In addition, the DD statement in the JCL
explicitly specifies the library block size.
General Usage Notes
3 Only one SAS session can open a direct access bound library for update at a given
time. It is necessary to specify a disposition status of NEW, OLD, or MOD in order
to update a SAS data library. However, multiple SAS sessions can share a SAS
data library for read-only access using DISP=SHR. Except for a special case of
relevance only during the installation of the SAS product, SAS will not open to
update a library that is allocated DISP=SHR.
3 The data set in which a direct access library resides is itself a simple physical
sequential data set. Therefore, the library data set can be copied or backed up
(subject to the restrictions below) to disk or to tape using standard z/OS utilities
such as IEBGENER, ISPF/PDF 3.3, or DF/HSM. However, the copy of the library
data set cannot be opened by SAS unless it resides on DASD.
3 The library data set for a direct access bound library must not be copied or backed
up while SAS has the library open for update. Failure to respect this restriction