Monitoring IMS Connect connections
IMS manages TCP/IP connections through IMS Connect, which serves as the TCP/IP gateway to IMS. The IMS Connect function can also be viewed as a TCP/IP socket server.
- IMS DB client connections, where the client is accessing IMS DB.
- IMS TM client connections, where the client is accessing IMS TM.
- IMS-to-IMS TCP/IP connections, where one IMS Connect instance connects to another IMS Connect instance for communications between two geographically remote IMS systems.
In addition to the TCP/IP connections that can be made to IMS Connect, you must also consider the connections between IMS Connect and the IMS server. IMS Connect runs in a separate address space from IMS and connects with certain components of IMS by using different communications methods.
For IMS DB client support, IMS Connect uses the Structured Call Interface (SCI) component of the IMS Common Service Layer (CSL) to connect to the IMS Open Database Manager (ODBM) component of CSL. ODBM communicates directly with IMS DB through the IMS Open Database Access (ODBA) interface.
IMS Connect also uses SCI for direct communications with IMS when IMS-to-IMS TCP/IP connections are used to support Multiple Systems Coupling (MSC) TCP/IP links.
For IMS TM client support, IMS Connect uses the z/OS® cross-system coupling facility to connect to the Open Transaction Manager (OTMA) component of IMS.
To monitor and verify the status of each type of the connection managed by IMS Connect, you might need to use different commands or facilities.
The following subsections describe only some of the commands that you can use to check the status of IMS Connect connections.