MP CONNECT might fail when you use the XMS Access Method in Base SAS. This situation occurs when the CONFIG file is not passed or allocated to the client session.

The root problem is that the CONFIG file might be freed after it has been closed. During SAS initialization, the CONFIG file is opened. SAS then processes options and closes the CONFIG file.

This situation creates a problem for MP CONNECT sessions that are forked by the SAS client session using the XMS Access Method. During MP CONNECT sign-on, values are built and are based on the setup of the SAS client environment. One of the values which passes to the MP CONNECT server session is CONFIG=, and the value of the CONFIG file.

However, if the CONFIG file has been freed after it was closed during initialization of the SAS client session, there will be no value passed for the CONFIG= parameter. This will cause the MP CONNECT session to not start. Only the following message will return to the SAS client session:

   NOTE: Remote signon to MP1 commencing (SAS Release 9.01.01M3P020206).
   ERROR: A communication subsystem partner link setup request failure has occurred.
   ERROR: XMS Communication Failure: DMR session did not complete
       initialization within the default time period. Check any options     
       passed to DMR with the sascmd option. Any data following a : in the
       sascmd option text is passed as is to the forked DMR session. Also
       check length of options since there is a limit of 4096 characters 
       for the options parameter.  This options parameter includes not only
       the options you specify but also options that are supplied for you.
   ERROR: Remote signon to MP1 cancelled.

In addition, an S0C4 abend might appear in the system log for the userid if the parameter passed is next to a page boundary. The S0C4 abend occurs in SASVDMRX.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at: