Report
contains the results of DATA step processing. Although you usually generate a report
by using a PROC step, you can generate the following two types of reports from the
DATA step:
Procedure
output file
contains printed results of DATA step processing, and
usually contains headers and page breaks.
HTML file contains results that you can display on the World Wide
Web. This type of output is generated through the Output
Delivery System (ODS).
The PROC Step
What Does the PROC Step Do?
The PROC step consists of a group of SAS statements that call and execute a procedure,
usually with a SAS data set as input. Use PROCs to analyze the data in a SAS data set,
produce formatted reports or other results, or provide ways to manage SAS files. You
can modify PROCs with minimal effort to generate the output that you need. PROCs can
also perform functions such as displaying information about a SAS data set. For more
information about SAS procedures, see Base SAS Procedures Guide.
PROC Step Output
The output from a PROC step can provide univariate descriptive statistics, frequency
tables, crosstabulation tables, tabular reports consisting of descriptive statistics, charts,
plots, and so on. Output can also be in the form of an updated data set. For more
information about procedure output, see Base SAS Procedures Guide and the SAS Output
Delivery System: User’s Guide.
SAS Processing Restrictions for Servers in a
Locked-Down State
General Information
If you are running SAS in a client/server environment (for example, you are using SAS
Enterprise Guide), the SAS server administrator can restrict access to files and
directories on the host system. Additionally, when a SAS session is in a locked-down
state, certain access methods, functions, CALL routines, and procedures are restricted by
default. For more information, see “Sign On to Locked-Down SAS Sessions” in
SAS/CONNECT User’s Guide.
When SAS is in a locked-down state, the following SAS language elements are not
available by default:
SAS Processing Restrictions for Servers in a Locked-Down State 17
Functions and
CALL Routines Access Methods Procedures Other
ADDR function
ADDRLONG
function
CALL MODULE
CALL POKE routine
CALL POKELONG
routine
PEEK function
PEEKC function
PEEKCLONG
function
PEEKLONG
function
EMAIL
FTP
HADOOP
HTTP
SOCKET
TCPIP
URL
GROOVY procedure
HADOOP procedure
HTTP procedure
JAVAINFO procedure
SOAP procedure
DATA step Java object
The ENABLE_AMS= option in the LOCKDOWN statement allows administrators to re-
enable access methods and procedures that are restricted by default when LOCKDOWN
is in effect. The following access methods and procedures can be re-enabled using the
ENABLE_AMS= option in the LOCKDOWN statement:
ENABLE_AMS= Option Values
FTP
EMAIL
HADOOP (enables PROC HADOOP)
HTTP (enables PROC HTTP and PROC SOAP)
SOCKET
TCPIP
URL (enables PROC HTTP and PROC SOAP
If you attempt to use a resource that is locked down, SAS issues an error message to the
SAS log. If the SAS session is configured for the SAS logging facility, SAS issues an
error message to the Audit.Lockdown logger.
For more information, see the following resources:
• “LOCKDOWN system option” and “LOCKDOWN statement” in SAS Intelligence
Platform: Application Server Administration Guide on the SAS Intelligence Platform
Documentation page at support.sas.com/documentation/onlinedoc/intellplatform.
• “Locked-Down Servers” in SAS Intelligence Platform: Security Administration
Guide on the SAS Intelligence Platform Documentation page at support.sas.com/
documentation/onlinedoc/intellplatform.
• For a list of products that do not support LOCKDOWN, see “TS2m1 products and
solutions that do not support the lockdown feature” (SAS Usage Note 51644).
18 Chapter 2 • SAS Processing
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
• DCREATE
• FILEEXIST
• FILENAME
• RENAME
• DSNCATLGD (z/OS-specific)
20 Chapter 2 • SAS Processing
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.