You can use the SAS Output Delivery System
(ODS) to format the SAS output that is generated in a SAS session
that runs on a server either synchronously or asynchronously. For
details about ODS, see the
SAS Output Delivery System: User's Guide.
Here are four typical
programming scenarios for using Compute Services with ODS to manage
output that is produced in a server session.
-
Remotely submit procedure statements
without any ODS statements.
Any output that is
produced by the remote submit produces a node in the Results window
that has the name
Rsubmit: (server-ID). The Results window uses ODS to generate pointers
(nodes) to various positions in the Output window. The resulting node
is a record of the output that is generated during a SAS server session.
-
Precede and end the remote submit
block (RSUBMIT through ENDRSUBMIT) with the appropriate ODS opening
statement (such as ODS HTML or ODS PDF) and the corresponding ODS
closing statement (such as HTML CLOSE or PDF CLOSE). Appropriate results
are produced in the SAS session at the client. For example, ODS HTML
produces output in the Results Viewer. ODS PDF produces output in
the Results window.
-
Precede RSUBMIT with the ODS OUTPUT
statement.
The output from the
RSUBMIT appears in the Results window and is saved as a SAS data set.
-
Remotely submit ODS statements
and procedures and DATA step statements to produce the ODS output
in the server session.
The output is processed
and generated entirely in the server session. Therefore, the results
(for example, a SAS data set or HTML output) must be downloaded from
the server session to the client session.
For all scenarios that use asynchronous
processing, use the
RGET Command and RGET Statement . The output is not available until
the results are retrieved. The accumulated output is retrieved and
transferred to the client session.