Verifying the system definition status online

You can check the consistency of your system definitions or ETO MSC descriptors using the /MSVERIFY command when each of the component systems of your network is operational.

Recommendation: Use the /MSVERIFY command during the system test phase, rather than during production. The /MSVERIFY command generates considerable traffic.
The /MSVERIFY command validates that:
  • Logical terminals exist for the remote LTERMs defined.
  • Transactions are defined and have the same attributes in their remote system as in the local system.
  • Logical path definitions are consistent and usable.
Recommendation: Define your remote LTERMs using ETO MSC descriptors. Otherwise, the Multiple Systems Verification utility recognizes remote LTERMs, but not the corresponding local LTERM in the target system.

The /MSVERIFY command verifies consistent definition between the local system and one remote system for each command. Verification begins with local SYSIDs and then proceeds to remote SYSIDs. As each segment of the processing begins, the MTO is notified of the local and remote SYSIDs to be verified. This message, DFS2234I or DFS2236I, also is time-stamped. As the specific local and remote SYSIDs are verified, the MTO receives verification-completed notifications with corresponding time stamps. If a definition or assignment error is discovered, error messages are returned.

During command processing, the local system sends all its own locally defined MSC elements (SYSIDs) to the remote IMS system specified in the /MSVERIFY command. The remote system responds by returning all destinations and their attributes that belong to the local system (as the remote system definition or assignments have them described). The command input system checks local and remote definitions for consistency.

The response list should be checked for completeness using the listing of SYSIDs that are to be verified given in the DFS2234I or DFS2236I IN PROGRESS messages and the correspondence of time stamps in responses.

The local system then sends all MSC elements to the remote system expecting them to be defined in that remote system with corresponding attributes (as the local system has them defined). The remote system performs consistency checks and routes error messages to the command input terminal.

MSC path consistency is only checked for current operational assignments of logical link paths to logical links, and logical links to physical links.

Recommendation: Ensure that the MSC definition and assignments are accurate, even when receiving favorable responses (that return no errors). Definition and assignment errors can prevent the return of a command response for some SYSIDs. Regard the absence of a response for a particular SYSID as significant.
Reviewing these error responses from the /MSVERIFY command might help you to avoid these definition and assignment errors: 
DFS2235I SYSID __ is defined as local in both systems
DFS2241I __ is defined as remote transaction in both systems
DFS2242I __ is not defined as LTERM in both systems
DFS2243I __ is not defined as transaction in both systems
DFS2245I Multisegment transaction flag for __ not consistent
DFS2246I Non-inquiry only flag for __ not consistent
DFS2247I Conversational flag for __ not consistent
DFS2248I Irrecoverable flag for __ not consistent
DFS2249I Fixed length SPA flag for __ is not consistent
DFS2250I The SPA length for __ is not the same

The /MSVERIFY command cannot detect errors caused by improper use of MSC directed routing.