DFS2165 ROUTING LOOP DETECTED I: sss1/name1, D: sss2/name2
Explanation
There is a routing loop in the IMS multiple systems coupling configuration. A routing loop can be created by either an incorrect system definition (the offline verification utility points that out), or by improper use of the /MSASSIGN command. A routing loop exists when a SYSID is not defined as local anywhere on the logical link path. For example: in IMS System A, SYSID 3 is defined as remote, and is assigned to a logical link connecting System A to System B. In IMS System B, SYSID 3 is again defined as remote, but is assigned to a logical link connecting System B to System A.
- sss1/name1
- The source SYSID and source LTERM name for the input system.
- sss2/name2
- The destination SYSID and destination LTERM or TRAN code of the processing system.
System action
IMS logs the message in error, using log record type '64', and removes the message from the system.
Operator response
(terminal operator) Notify the master terminal operator.
(master terminal operator) This is probably a user error. Use the /DISPLAY ASSIGNMENT command to display the current SYSID assignments involved. If the looping message is a response destined for an inputting terminal that is in response, conversation, or exclusive mode, this error can result in the terminal remaining locked until restarted with a /START command or until the conversation is terminated with an /EXIT command.