There have been requests from sites that XMS (Cross Memory Services)
support a two level server specification, primarily for a sysplex
environment where a job might be initiated on different systems.  To
have this support, the SAS Client session can define multiple
ommunication access methods.  For example:  COMAMID=XMS and COMAUX1=TCP.
In such a setup SAS can check the value specified for hostname.  If this
matches the name of the machine where the SAS Client job is running then
SAS will use XMS for the communication protocol.  Otherwise, the SAS
Client session will use the alternate communication access method TCP.

Notes about the use and  current implementation:

1) Requires that the Server environment is setup properly to support
both communication access methods (XMS and TCP).

2) The SAS system option SASCMD= if set always implies MPCONNECT for a
SIGNON.  Therefore, it should be set only when needed and reset when no
longer needed. For example:

   OPTIONS SASCMD='x:';  /* This means a SIGNON is MP */
   OPTIONS SASCMD=' ';   /* This means a SIGNON is not MP */

3)  Other options like TCPSEC= should be set properly on the Client side
in order for proper remote host authentication and resource
authorization access to be performed when XMS can not be used.

4) Currently the hostname specification must be no longer than 8 bytes
and can not be a reference to a macro variable.  If the hostname can not
be defined in 8 bytes, then this feature is currently not available to
you.

Operating System and Release Information