SAS Companion for the CMS Environment

Running SAS in Batch Mode

The details of how to submit programs to CMS batch machines depend on whether you are using the native CMS batch facility, or a batch facility that was developed by a third-party vendor. Ask your system manager or other coworkers for details about batch processing at your site.

In CMS batch mode, you can execute either a noninteractive SAS session or an interactive SAS session:

A noninteractive SAS session is identical to invoking and executing a noninteractive SAS session in CMS interactive mode, except that there is no terminal attached. Not having an attached terminal affects only windowing procedures. Some windowing procedures provide different functionality when no terminal is available. For information about particular windowing procedures, see SAS Procedures Guide, SAS Language and Procedures: Usage, or specific product documentation. You can route SAS system messages to the console log by specifying TERMINAL as the value of the LOG= system option when you invoke SAS.
Note: This is the preferred method of operation in a CMS batch machine.
An interactive SAS session requires that all SAS statements be queued on the console stack before you invoke SAS. You can queue SAS statements by using the QUEUE instruction in a REXX EXEC. This method is useful if you want to route all SAS system messages to the console log without specifying LOG=TERMINAL.

SAS programs that are run in a CMS batch machine or in any disconnected virtual machine run the same way as SAS programs that are run in other modes; no special SAS statements or rules are needed.

Chapter Contents
Previous
Next
Top of Page