z/OS-Specific Information
Restricted Features
Access to permanent z/OS data sets and UFS files and directories is not permitted unless
enabled in the lockdown list. This restriction applies to all SAS features, most notably
FILENAME and LIBNAME statements in SAS programs that are submitted for
execution on the server. This restriction also applies to the ability to list files on the
server through SAS clients such as SAS Enterprise Guide. When SAS is in the locked-
down state, SAS does not permit access to uncataloged z/OS data sets except through
externally allocated ddnames that are established by the server administrator. However,
there are no restrictions on creating temporary z/OS data sets and UFS files, and
processing them within the context of a single client session. The z/OS data sets are
considered temporary if they are allocated DISP=(NEW,DELETE). External files are
considered temporary if they are assigned using the FILENAME device of TEMP. All
members of the client WORK library are considered temporary.
The SAS server administrator at your installation is responsible for the content of the
lockdown list. Therefore, if you need to access a z/OS data set or UFS file that is
unavailable in the locked-down state, contact your server administrator.
Disabled Features
The following SAS procedures, which are specific to z/OS, cannot be executed when
SAS is in the locked-down state:
PDS SOURCE
PDSCOPY TAPECOPY
RELEASE TAPELABEL
The following DATA step functions, which are specific to z/OS, cannot be executed
when SAS is in the locked-down state:
ZVOLLIST ZDSATTR
ZDSLIST ZDSRATT
ZDSNUM ZDSXATT
ZDSIDNM ZDSYATT
The following access method, which is specific to z/OS, cannot be executed when SAS
is in the locked-down state:
VTOC
Specifying Functions in the Lockdown Path List
If the SAS session in which you are specifying a function is in a locked-down state, and
the pathname specified in the function has not been added to the lockdown path list, then
the function will fail. A file access error related to the locked-down data will not be
generated in the SAS log unless you specify the SYSMSG function.
The SYSMSG function can be placed after the function call in a DATA step to display
lockdown-related file access errors.
This condition is true for the following functions, as well as for any other functions that
take physical pathname locations as input:
SAS Processing Restrictions for Servers in a Locked-Down State 19