OLE automation servers are SAS^® sessions that are started programmatically from an external program using some tool such as Microsoft Visual Basic. Code submitted to the OLE automation server session is handled differently than code in an interactive SAS session.

When you submit a SAS/CONNECT^® RSUBMIT/ENDRSUBMIT block to an OLE automation server, the interface can submit each line individually only. Ideally, the ENDRSUBMIT statement should go with the remote SAS session and not to the SAS session executing the RSUBMIT statement. However, with OLE automation submission, the ENDRSUBMIT statement is submitted to the session that is performing the process of remote submission. For example, the problem occurs when you submit the following code to an OLE automation server:

When this code is submitted, the following error is generated:

6    endrsubmit;
     ----------
     180

ERROR 180-322: Statement is not valid or it is used out of proper order.

There is no known way to handle this properly. The best approach is to change the SAS code that is submitted so that all of the code from the RSUBMIT statement to the ENDRSUBMIT statement is on one line. Here is an example:

Tip: When all of the statements on one line this way, it is helpful to use a %INCLUDE statement between the RSUBMIT and ENDRSUBMIT statements if there is a lot of code between the two statements.

For example, suppose you have a DATA step that contains many statements as part of the RSBUMIT block. You can put all of the DATA step code in a flat SAS file on your operating system, and then use the %INCLUDE statement in the one RSUBMIT/ENDSUBMIT statement line, as shown below:

For SAS users that use interactive display mode: Try submitting the code from the first example above ONE LINE AT A TIME in SAS. Doing so will help you understand how code is handled by submitting an entire block of code from the editor versus submitting it line by line (as is done by the OLE automation server interface).

Operating System and Release Information