Resolving problems with parallel RESUME TPIPE requests

Diagnosing problems with communication between IMS Connect and an OTMA tpipe that supports parallel RESUME TPIPE requests is complicated by the fact that multiple RESUME TPIPE requests can be active on a tpipe at the same time.

Also, because OTMA identifies OTMA clients by the name of the tpipe that they use, OTMA knows only the tpipe name that is specified by the client in the alternate client ID field and not the actual client ID.

To help identify the actual client ID, when parallel RESUME TPIPEs are supported, you can use the RESUME TPIPE token, the alternate client ID, and the client ID to correlate an IMS Connect client with the specific RESUME TPIPE request it has active with the OTMA tpipe.

To identify which client issued each RESUME TPIPE request that is active on an OTMA tpipe that supports parallel RESUME TPIPE requests:

Issue the IMS command /DISPLAY TMEMBER ims_connect_name TPIPE tpipe_nm OUTPUT
Note the IMS Connect instance and the relevant RESUME TPIPE tokens that are displayed in the output of the /DISPLAY TMEMBER command.
Issue the IMS Connect command QUERY IMSCON TYPE(CLIENT) RTTOKEN(rt_token_number) SHOW(ALTCID RTTOKEN)
Locate the RESUME TPIPE token in the information that is displayed by the QUERY IMSCON command. The client ID that issued the RESUME TPIPE call is displayed under the heading ClientID on the same row as its associated token.

In the following example, CLIENT03 on the IMS Connect instance HWS1 issued a RESUME TPIPE call to OTMA tpipe CLIENT99. However, because OTMA recognizes OTMA clients by the name of the tpipe that they use, only CLIENT99 is displayed, and not CLIENT03.

To determine which specific RESUME TPIPE call was issued by CLIENT03, the IMS command /DISPLAY TMEMBER is issued with the HWS1 and TPIPE ALL specified to display the RESUME TPIPE tokens of the RESUME TPIPE calls that are currently active on the tpipe. To limit the output to a specific tpipe, specify the tpipe name, CLIENT99 in this case, instead of the ALL keyword.

/DIS TMEM HWS1 TPIPE ALL OUTPUT                                                
DFS000I     MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT STATUS   
DFS000I     HWS1                                                                    
DFS000I    -CLIENT99                  0          0          0          0 PMRY
DFS000I    -CLIENT99                  0          0          0          0 HLDQ   
DFS000I    -CLIENT99              RT CBB45E89AAF02E8A   OPT A     MODE S

After the RESUME TPIPE token is determined, the QUERY IMSCON TYPE(CLIENT) command is issued with the token specified on the RTTOKEN keyword and SHOW(ALTCID) specified:

QRY IMSCON TYPE(CLIENT) RTTOKEN(CBB45E89AAF02E8A) SHOW(ALTCID RTTOKEN)

The client ID that corresponds to the RTTOKEN and the ALTCID is displayed with the RTTOKEN and ALTCID values:

ClientID MbrName            CC ALTCID   RTToken 
CLIENT03 IMSPLEX1            0 CLIENT99 CBB45E89AAF02E8A