MSNAME duplication in an IMSplex with shared queues

For each IMS system that participates in both an MSC network and a shared queues group, MSNAMEs and their associated remote and local SYSIDs are exchanged with the other IMS systems in the shared queues group when the IMS is initialized.

Dynamic MSNAMEs are created in each IMS system for the MSNAMEs that were defined on the other IMS systems in the shared queues group.

A common MSC SYSID routing table is built in each IMS system from the remote and local SYSID values that are defined in each MSNAME. SYSIDs that are local in each IMS system are also made local to the other IMS systems in the shared queues group. The same local SYSIDs on all IMS systems in the shared queues group allow any message received from an IMS system outside the shared queues group through an MSC link to be routed and processed by any IMS system in the shared queues group.

Duplicate MSNAMEs in IMS systems in a shared queues group must have the same remote SYSID because MSNAMEs and remote SYSIDs are synonymous. The same MSNAMEs must relate to the same remote SYSIDs. Different local SYSIDs for the same MSNAME are allowed.

If the same MSNAME is defined with different remote SYSIDs in two IMS systems, the MSNAME is ignored when MSNAMEs are exchanged within the shared queues group. Dynamic MSNAMEs are not created in the IMS systems with the same MSNAME and each IMS retains its own version of the MSNAME.

Each of these two examples show valid combinations of MSNAMEs that have the same name in a shared queues group:
  • A valid MSNAME pair:
    • (On IMSA) MSN12345 MSNAME SYSID=(1,2)
    • (On IMSB) MSN12345 MSNAME SYSID=(1,2)
  • Also a valid MSNAME pair:
    • (On IMSA) MSN12345 MSNAME SYSID=(1,2)
    • (On IMSB) MSN12345 MSNAME SYSID=(1,3)
This is an example of an invalid combination of MSNAMEs that have the same name in a shared queues group:
  • (On IMSA) MSN12345 MSNAME SYSID=(1,2)
  • (On IMSB) MSN12345 MSNAME SYSID=(2,1)