Viewing MSC connection information for IMS-to-IMS TCP/IP communications
You can view configuration and status information for IMS-to-IMS TCP/IP connections that are used for MSC by issuing IMS Connect commands.
Each MSC link requires two socket connections: a send socket connection and a receive socket connection. You display information about the send socket connections by querying RMTIMSCON connection information. You display information about the receive socket connection by querying the port information.
You can also display information about the definition and status of an MSC logical link by querying the MSC configuration information in IMS Connect.
Example: Viewing an MSC TCP/IP connection at the local and remote IMS Connect instances
nnVIEWRMT ICON2
The
example output shows that two send socket connections, MSCBB435 and
MSC84CF7, are in CONN status on the RMTIMSCON connection ICON2. The
SENDCLNT IDs are auto-generated by the local IMS Connect instance when establishing the send
socket connections to remote IMS Connect
instance. In the example, PORT=5555
shows that the
local IMS Connect expects the
remote IMS Connect to be listening
on port 5555. The presence of the LCLPLKID values indicate that these
are MSC connections and identify the local MSC physical link that
they are using.
HWSC0001I RMTIMSCON=ICON2 STATUS=ACTIVE
HWSC0001I IP-ADDRESS=009.030.221.055 PORT=5555
HWSC0001I HOSTNAME=ECSER14.VMEC.SVL.IBM.COM
HWSC0001I AUTOCONN=N PERSISTENT=Y
HWSC0001I IDLETO=0
HWSC0001I RESVSOC=2 NUMSOC=2
HWSC0001I SENDCLNT LCLPLKID STATUS SECOND SENDPORT
HWSC0001I MSCBB435 MSC12 CONN 6 1028
HWSC0001I MSC84CF7 MSC12 CONN 56 1027
HWSC0001I TOTAL SENDCLNTS=2 RECV=0 CONN=2 XMIT=0 OTHER=0
nnVIEWPORT 9999
The example output shows the receive socket connections, MSCC73E0 and MSC0EBB0, that are in RECV state on port 9999 at the local IMS Connect instance. Again, the presence of the LCLPLKID values indicate that these connections are being used for MSC, as well as the local MSC physical link that they are using.
HWSC0001I PORT=9999 STATUS=ACTIVE KEEPAV=0 NUMSOC=3 EDIT= TIMEOUT=0
HWSC0001I CLIENTID LCLPLKID STATUS SECOND CLNTPORT IP-ADDRESS
HWSC0001I MSCC73E0 MSC12 RECV 6 1026 0:0:0:0:0:FFFF:91E:DD37
HWSC0001I MSC0EBB0 MSC12 RECV 56 1025 0:0:0:0:0:FFFF:91E:DD37
HWSC0001I TOTAL CLIENTS=2 RECV=2 READ=0 CONN=0 XMIT=0 OTHER=0
The following examples for a remote IMS Connect instance correspond to the preceding examples for a local IMS Connect instance.
nnVIEWPORT 5555
The output for the VIEWPORT command shows two receive socket connections, MSCBB435 and MSC84CF7, on port 5555. These CLIENTID values match the SENDCLNT values shown in the preceding example of the VIEWRMT command at the local IMS Connect instance.
HWSC0001I PORT=5555 STATUS=ACTIVE KEEPAV=0 NUMSOC=3 EDIT= TIMEOUT=0
HWSC0001I CLIENTID LCLPLKID STATUS SECOND CLNTPORT IP-ADDRESS
HWSC0001I MSCBB435 MSC21 RECV 18 1028 0:0:0:0:0:FFFF:91E:7326
HWSC0001I MSC84CF7 MSC21 RECV 69 1027 0:0:0:0:0:FFFF:91E:7326
HWSC0001I TOTAL CLIENTS=2 RECV=2 READ=0 CONN=0 XMIT=0 OTHER=0
nnVIEWRMT ICON1
The
example output shows that two send socket connections, MSCC73E0 and
MSC0EBB0 under SENDCLNT, are in CONN status on the RMTIMSCON connection
ICON1. These SENDCLNT values match the CLIENTID values shown in the
preceding example of the VIEWPORT command at the local IMS Connect instance. In the example, PORT=9999
shows
that the remote IMS Connect expects
the local IMS Connect to be listening
on port 9999. The presence of the LCLPLKID values indicate that these
are MSC connections and identify the local MSC physical link that
they are using.
HWSC0001I RMTIMSCON=ICON1 STATUS=ACTIVE
HWSC0001I IP-ADDRESS=009.030.115.038 PORT=9999
HWSC0001I HOSTNAME=ECSER13.VMEC.SVL.IBM.COM
HWSC0001I AUTOCONN=N PERSISTENT=Y
HWSC0001I IDLETO=0
HWSC0001I RESVSOC=2 NUMSOC=2
HWSC0001I SENDCLNT LCLPLKID STATUS SECOND SENDPORT
HWSC0001I MSCC73E0 MSC21 CONN 18 1026
HWSC0001I MSC0EBB0 MSC21 CONN 69 1025
HWSC0001I TOTAL SENDCLNTS=2 RECV=0 CONN=2 XMIT=0 OTHER=0