Managing MSC links in a TCP/IP generic resource group
When MSC is used with TCP/IP generic resources, each link that connects to the TCP/IP generic resource group has affinity to a specific IMS system in the group.
Affinity restricts all of the logical link parallel sessions on a physical link to one IMS system. Affinity is cleared in IMS when a logical link is terminated normally.
When a link has affinity, a /DISPLAY AFFIN LINK or QUERY MSLINK displays the link with a status of AFFIN. The QUERY MSLINK command also shows the IMS ID of the IMS system that has affinity.
IMS Connect manages the routing of link requests to the TCP/IP generic resource group. The definitions of the MSC links in IMS Connect correlate the shared generic IMS ID of the TCP/IP generic resource group to the individual participating IMS systems in the group.
When a link to a TCP/IP generic resource group is started by the remote IMS system, the start request is routed by IMS Connect to all available IMS systems in the group. IMS Connect passes the link request to the first IMS system to accept the link and the link affinity is set. IMS Connect then routes all logical link parallel sessions on the same physical link to that IMS system.
If a TCP/IP generic resource group contains only one IMS system, then the initial link request is always accepted by that system, regardless of which side a link is started from.
As a precaution, display the affinity status of an MSC link on its current IMS system before moving the link by restarting it on another IMS system. If the affinity is still active, shutdown the link normally, which resets the affinity status. If the link cannot be shut down normally, set the link to COLD status by issuing either the type-1 command /CHANGE LINK linknum FORCSESS | SYNCSESS COLDSESS or the type-2 command UPDATE MSLINKNAME(linkname) SET(SYNCOPT(COLDSESS)
Attention: Changing the link status from ERE to COLD or moving a link in ERE status and restarting it on another IMS system prevents the synchronization of the message sequence numbers during restart, which can cause the duplication or loss of messages.
If multiple IMS systems participate in a TCP/IP generic resource group, you can use the following methods to control which IMS system gets affinity when you start the first logical link on a physical link: