Using Compute Services

Using the SAS Windowing Environment to Control Remote Processing

Overview of Remote Processing Control Using the SAS Windowing Environment

The SAS windowing environment includes menu selections that enable you to control remote processing during a SAS session. The following Compute Services menu selections are available from the Run menu:

Remote Submit: enables you to submit one or more statements to a SAS/CONNECT server session for remote processing.
Remote Get: merges the spooled Log and Output lines from the asynchronous remote submit operation with the client's Log and Output windows for viewing.
Remote Display: enables you to view the spooled Log and Output lines that are created by the asynchronous remote submit operation in the Log and Output windows that are created for the specific remote server session.

Remote Submit

To submit one or more statements to a SAS/CONNECT server session for remote processing, open the SAS Program Editor window and select Run Remote Submit from the menu bar.

The Remote Submit dialog box appears.

Remote Submit Dialog Box

[Remote Submit Dialog Box]

Here are explanations of the fields:

Remote session name

specifies the server session that the statements are executed in. If only one session is active, this field can be empty. If multiple server sessions are active, omitting the remote session name causes the program statements to be run in the session that is specified in the CONNECTREMOTE= option. You can find out which server session is current by examining the value that is specified in the CONNECTREMOTE system option.

For information about the CONNECTREMOTE= option, see RSUBMIT Statement and Command.

Remote session macro variable name

associates a macro variable with a specific RSUBMIT block. Macro variables are especially useful for controlling the execution of multiple asynchronous RSUBMIT operations.

For information about the CMACVAR= option, see RSUBMIT Statement and Command.

Display transfer status (yes/no)

specifies whether the status window for file transfers is displayed for the current remote submit operation.

If this field is empty, the default value is obtained from the CONNECTSTATUS= system option or the CONNECTSTATUS= option in the SIGNON= statement for this server.

For information about the CONNECTSTATUS= option, see RSUBMIT Statement and Command.

Execute remote submit synchronously (yes/no):

specifies whether the remote submit operation executes synchronously or asynchronously. Synchronous processing means that server processing must be completed before control is returned to the client session. Asynchronous processing permits the client and one or more server session processes to execute in parallel. Control is returned to the client session immediately after a remote submit begins execution to allow continued processing in the client session.

If the field is empty, the default value is obtained from the CONNECTWAIT= system option or the CONNECTWAIT= option in the SIGNON= statement for this server.

For information about the CONNECTWAIT= option, see RSUBMIT Statement and Command.

CAUTION:

Remote Submit Limitation:

The Remote Submit menu cannot be used if a CARDS statement, a CARDS4 statement, a DATALINES statement, a DATALINES4 statement, or a PARMCARDS statement is included in the remote submit operation.

The Remote Submit menu is prohibited from processing data because of its implementation as a macro. A macro definition cannot contain a CARDS statement, a DATALINES statement, a PARMCARDS statement, or data lines.

However, you can use any of the following methods to execute a remote submit that contains any of these statements.

Enter the RSUBMIT command in the command window.
Enter the RSUBMIT and ENDRSUBMIT statements in the editor window.
Submit the statements for local execution, and then use PROC UPLOAD to transfer the created output to the server session.

Remote Get

To merge the spooled log and output from the asynchronous remote submit operation with the client's Log and Output windows for viewing, open the SAS Program Editor window and select Run Remote Get from the menu bar.

Here are explanations of the fields:

Remote session name

specifies the server session whose spooled log and output lines are to be merged into the client's Log and Output windows. If only one session is active, this field can be empty. If multiple server sessions are active, omitting the remote session name causes RGET to execute for the session that is specified in the CONNECTREMOTE= option.

For more information, see RGET Command and RGET Statement.

Note: Remote Get applies only to asynchronous remote submit operations. If you execute Run Remote Get while the asynchronous remote submit operation is in progress, the operation is automatically converted to synchronous processing so that all of the lines from the server session can be merged. [cautionend]

Note: To view the spooled Log and Output lines that are created by the asynchronous remote submit operation (does not merge with the client's Log and Output windows), select Remote Display. [cautionend]

Remote Display

To view only the spooled Log and Output lines from the asynchronous remote submit operation, open the SAS Program Editor window and select Run Remote Display from the menu bar.

Here are explanations of the fields:

Remote session name

specifies the session name of the server whose Log and Output lines are to be viewed. If only one session is active, this field can be empty. If multiple server sessions are active, omitting the remote session name causes RDISPLAY to execute in the session that is specified in the CONNECTREMOTE= option.

For more information, see RDISPLAY Command and RDISPLAY Statement.

Note: Remote Display applies only to asynchronous remote submit operations. [cautionend]

Note: To merge the spooled Log and Output lines that are created by the asynchronous remote submit operation with the client's Log and Output windows, select Remote Get. [cautionend]

Top of Page