The connection process

The process of connecting to CICSPlex SM varies according to what type of program you write and where it runs.

For programs written using the command-level interface, keep in mind the following requirements:
CICS
A program written to run as a CICS application must be linked with the proper stub routine and must run in a CICS® system that is being actively managed by CICSPlex SM as a local MAS.

A connection is established first to the MAS agent code that resides in the CICS system and then to the CMAS that controls that MAS. On the CONNECT command, you must specify a CONTEXT of the local CMAS.

Batch, NetView®, or TSO
A program written to run as a batch job or under NetView or TSO must be linked with the proper stub routine and must run in the same MVS image as the CMAS to which you want to connect.
In these environments, if there is more than one CMAS in the MVS™ image, the API selects a suitable CMAS and establishes a connection. The following rules apply to the selection of a CMAS:
  • The CMAS must be running the same version of CICSPlex SM as the run-time module (EYU9AB00).
  • If the context specified on the CONNECT command is a CMAS, CICSPlex SM connects to that CMAS. If that CMAS is either not active or not running the appropriate version of CICSPlex SM, the CONNECT command fails.
  • If the context specified on CONNECT is a CICSplex, CICSPlex SM selects a CMAS running the appropriate version that participates in the management of the CICSplex.
  • If no context is specified on CONNECT, CICSPlex SM connects to the CMAS that was most recently started, provided it is running the appropriate version of CICSPlex SM>.
The CICSPlex SM API also supports another type of batch environment. A program can issue API commands from an address space that is running a CICS system without itself being a CICS transaction. In other words, the program can run as a separate MVS task in the same address space as the CICS system. This type of program must be linked with the batch environment stub routine and the connection process is the same as for other batch programs.
Note: A program that is a CICS transaction must be run in a CICS system that is a CICSPlex SM local MAS.
For details on the stub routines that are required for each of these environments, see Link editing your program.
Note: For programs written in REXX, the connection process is the same as for a command-level program that runs in the same environment (batch, TSO, or NetView). No stub routine is required, but the REXX function package that is supplied by CICSPlex SM must have been properly installed.
MVS restrictions: Upon successful completion of a CONNECT request, a thread token is returned to the user. All subsequent commands referring to this thread token must be issued from the same MVS TCB that issued the connection request