|Initializing and Configuring SAS Software|
in interactive mode under TSO using the SAS CLIST
in interactive mode under TSO using the SASRX exec
in batch mode with the SAS cataloged procedure
by logging on to SAS directly and bypassing the TSO terminal monitor program.
|Invoking SAS under TSO: the SAS CLIST|
At each site, the name of the command that you use and the SAS CLIST might have been modified by your on-site support personnel. Ask your support personal for site-specific information about the CLIST.
The SAS CLIST starts a SAS windowing environment session, an Explorer session, an interactive line mode session, or a noninteractive session, depending on the defaults that have been specified in the CLIST. To override the mode of running SAS that is specified in the CLIST, you use commands similar to those shown in Commands for Invoking SAS. (Again, the exact commands that you use might be site-specific.)
|Invoking SAS under TSO: the SASRX exec|
SASRX is a REXX program that you can use to invoke SAS. It is provided as an alternative to the SAS CLIST. SASRX supports the same command-line syntax as the SAS CLIST. It also supports these additional features:
mixed-case option values
UNIX style option specification
direct specification of SAS system options
UFS file and directory names as option values
Throughout this document, references to the SAS CLIST apply equally to the SASRX exec.
|Commands for Invoking SAS|
The following table contains examples of commands that you can use to invoke SAS.
|Mode||To Invoke||To Terminate||Description|
|SAS windowing environment||
||enables you to write and execute SAS programs and to view the SAS log and SAS procedure output in an interactive windowing environment. If this is the default at your site, then you can invoke it by entering sas (or sasrx) with no options.|
|bye or endsas||enables you to manipulate SAS data and files visually, launch SAS applications, and access SAS windowing environment windows and Output Delivery System hierarchies.|
|interactive line mode||
|/* or endsas; statement||prompts you to enter SAS statements at your terminal, one line at a time.|
|not applicable||executes interactively, but it is called noninteractive because the program runs with no intervention from the terminal.|
|Invoking SAS in Batch Mode: the SAS Cataloged Procedure|
By specifying parameters in the JCL EXEC statement, you can modify the way in which SAS is invoked.
At each site, the JCL EXEC statement that you use and the cataloged procedure itself might have been modified by your on-site SAS support personnel. Ask your support personnel for site-specific information.
|Logging On to SAS Software Directly|
z/OS sites can choose to substitute SAS for the standard TSO terminal monitor program, enabling users to log on to SAS directly. If SAS comes up automatically when you log in, then your system might have already been set up to log on to SAS directly.
By automatically invoking SAS software or a SAS application when users log on, site administrators can insulate users from the TSO environment. Because SAS is running as its own terminal monitor program, TSO commands are not accessible to users. This reduces memory usage slightly.
|What If SAS Does Not Start?|
If SAS does not start, the SAS log might contain error messages that explain the failure. Any error messages that SAS issues before the SAS log is initialized are written to the SAS Console Log, which is the SASCLOG ddname destination. Under TSO, the SASCLOG ddname destination is normally the terminal, but the destination might be changed by the on-site SAS support personnel by changing the CLIST or SASRX exec that invoked SAS. Similarly, a batch job or started task normally assigns the SASCLOG ddname to a spooled SYSOUT class, but the destination might have been changed by the on-site SAS support personnel by changing the catalog procedure used to invoke SAS. Spooled SYSOUT data can be printed or viewed online with a JES spool viewer such as SDSF, IOF, or EJES.