MSC statement

The MSC statement defines a one-way send path for an MSC physical link between a local IMS system to a remote IMS system.

The physical link send path uses a TCP/IP socket connection established by this IMS Connect instance with a remote IMS Connect instance. The connection used by the physical link must be defined to this IMS Connect instance by an RMTIMSCON statement.

The remote IMS Connect instance must define corresponding RMTIMSCON and MSC statements. Each MSC logical link assigned to a physical link requires two socket connections: one established by the local IMS Connect to send transaction messages and one established by the remote IMS Connect instance to return the reply messages.

MSC statement syntax

Read syntax diagramSkip visual syntax diagramMSC(B)
B
Read syntax diagramSkip visual syntax diagramGENIMSID=genericimsidIMSPLEX=(MEMBER= icon_imsplex_name,TMEMBER= imsplex_sci_name),LCLIMS=( IMS_ID, XRFALTID),LCLPLKID= local_physical_link_id,RMTIMS= remote_IMS_ID,RMTIMSCON= rmt_imscon_name,RMTPLKID= remote_physical_link_id

MSC statement parameters

GENIMSID=
This is an optional parameter. The MSC TCP/IP generic IMS ID that each participating IMS system in the local IMSplex also specifies on the GENIMSID parameter of the DFSDCxxx member of the IMS PROCLIB data set.

The GENIMSID parameter accepts a 1 - 8 character alphanumeric name that begins with an alphabetic character. The value of GENIMSID cannot be the same name as the values specified on either the LCLIMS or RMTIMS parameters.

IMSPLEX=()
Enables IMSplex communications between IMS Connect and MSC. IMSplex communications are managed by the Structured Call Interface (SCI) component of the IMS Common Service Layer (CSL).
If another IMSPLEX statement in this member of the IMS PROCLIB data set already joins IMS Connect to the IMSplex in which the MSC-enabled IMS system is a member, then this IMSPLEX substatement is optional; however, at least one IMSPLEX statement must be specified in the HWSCFGxx member of the IMS PROCLIB data set to enable IMSplex communications between this IMS Connect instance and MSC.
If an IMSPLEX substatement is not included on the MSC statement, and more than one IMSPLEX statement is specified elsewhere in this HWSCFGxx member of the IMS PROCLIB data set, IMS Connect uses the first IMSPLEX statement in the HWSCFGxx member of the IMS PROCLIB data set for communications between IMS Connect and MSC.
MEMBER=
A 1- to 8-character alphanumeric name that identifies IMS Connect in the IMSplex. IMS Connect registers this name with SCI. For MSC communications, this name must match the name specified on the LCLICON parameter of the MSPLINK macro definition of the local IMS system. The name must start with an alphabetic character.
Note: An IMS Connect instance can register only a single name in an IMSplex. If the same IMSplex name is specified on two or more TMEMBER parameters in the HWSCFGxx member of the IMS PROCLIB data set, then the same IMS Connect name must be specified on each of the corresponding MEMBER parameters. If the MEMBER parameters differ on two or more IMSplex statements that specify the same IMSplex name, IMS Connect issues an error message and abends on startup.
TMEMBER=
The name of the IMSplex that IMS Connect is joining, as specified on the IMSPLEX(NAME=) statement of the CSLSIxxx member of the IMS PROCLIB data set of the SCI instance that is managing communications between IMS Connect and the IMSplex.
Restriction: The name specified on the TMEMBER parameter cannot be the same as a name specified on the ID parameter of any DATASTORE statement.
LCLIMS=
For a link to a non-XRF IMS system, specifies the IMS ID of the local IMS system as registered with SCI in the IMSplex. It is a 1- to 8-character alphanumeric name that begins with an alphabetic character.

For a link to IMS systems that form an XRF pair, specifies either the IMS ID of one of the IMS systems in the pair, or, optionally, the IMS IDs of both of the IMS systems in the pair. If the IMS ID of only one of the IMS systems in the XRF pair is specified, a separate MSC statement must be coded for the other IMS system in the pair.

For example, to define a link to an XRF pair by using one MSC statement, you might code the following statement:
MSC=(LCLPLKID=MSC13,RMTPLKID=MSC,LCLIMS=(IMS1,IMS2),RMTIMS=IMS3,GENIMSID=IMS)
Alternatively, to define a link to an XRF pair by using two MSC statements, you might code the following MSC statements:
MSC=(LCLPLKID=MSC13,RMTPLKID=MSC,LCLIMS=IMS1,RMTIMS=IMS3,GENIMSID=IMS)
MSC=(LCLPLKID=MSC13,RMTPLKID=MSC,LCLIMS=IMS2,RMTIMS=IMS3,GENIMSID=IMS)

You can determine the IMS ID that is registered with SCI by issuing the QUERY IMSPLEX command in the local IMSplex.

LCLPLKID=
The local name of the MSC physical link. The name specified on the LCLPLKID parameter identifies the MSC physical link to IMS Connect. The name also associates the definitions in this MSC statement with the physical link definitions in an MSPLINK macro statement on the local IMS system.

This name must match the name specified on the LCLPLKID parameter of the MSPLINK macro.

The name must start with an alphabetic character and can be 1 - 8 alphanumeric characters in length.

RMTIMS=
This is the IMS ID of the remote (target) IMS system as registered with SCI in the remote IMSplex. It is a 1- to 8-character alphanumeric name that begins with an alphabetic character.

You can determine the IMS ID that is registered with SCI by issuing the QUERY IMSPLEX command in the remote IMSplex.

RMTIMSCON=
The remote IMS Connect connection to use for MSC messages. The value of RMTIMSCON must match the value of the ID parameter of one of the RMTIMSCON statements specified in the local IMS Connect configuration.
RMTPLKID=
The remote name of the MSC physical link as specified on the LCLPLKID parameters of both the MSC statement of the remote IMS Connect and the MSPLINK macro of the remote IMS system. The name must start with an alphabetic character and can be 1 - 8 alphanumeric characters in length.