Displaying and interpreting output message counts

You can use IMS Connect commands to display output message counts when you want to monitor or troubleshoot the proper retrieval of asynchronous output messages.

About this task

For commit mode 0 interactions, the tpipe name is the client ID that is used for the interaction. For commit mode 0 interactions, the IMS OTMA asynchronous hold queue that is associated with the tpipe has the same name as the client ID.

For commit mode 1 interactions, the tpipe name is the IMS Connect port number that is used for the interaction. Each port has a tpipe that is used for all clients that run commit mode 1 interactions on that port.

Procedure

  1. To view counts of the output messages that are sent to the IMS TM resource adapter, as well as messages that are inserted to Alternate Program Communication Blocks (Alternate PCBs), use the IMS Connect command /DISPLAY TMEMBER IMSConnect_Name TPIPE ALL.

    The following sample output is from a /DISPLAY TMEMBER HWS1 TPIPE ALL command. The types of tpipes and counts for the command output are also described.

    DFS000I     MEMBER/TPIPE       ENQCT   DEQCT     QCT  STATUS     IMS1
DFS000I     HWS1                                                 IMS1
DFS000I    -9999                   0       0       0             IMS1
DFS000I    -HWSMIJRC               2       2       0             IMS1
DFS000I    -CLIENT01               3       2       1             IMS1
DFS000I    -ALTPCB1                2       1       1             IMS1
DFS000I    -HWS$DEF                1       0       1             IMS1
DFS000I    -RRNAME                 1       0       1             IMS1
  2. To interpret the command output, determine which tpipe is the queue of interest, and the corresponding QCT column contain the message count.
    The tpipe name is determined by the type of interactions and connections.
    • For commit mode 1 interactions on a shareable persistent socket:
      • The tpipe name is the port number used for the interaction. In this sample, tpipe 9999 indicates that this queue is for a commit mode 1 interaction on a shareable persistent socket.
      • The enqueue count (ENQCT) and dequeue count (DEQCT) are the same, and the queue count (QCT) is 0, because undelivered output messages are not recoverable for commit mode 1 transactions.
    • For commit mode 0 interactions on a shareable persistent socket:
      • The tpipe name is generated by the IMS TM resource adapter and has a prefix of HWS. In this example, tpipe name HWSMIJRC is generated by the IMS TM resource adapter.
      • The enqueue count (ENQCT) and dequeue count (DEQCT) are the same, and the queue count (QCT) is 0 if all messages are delivered to the IMS TM resource adapter.
      • The enqueue count (ENQCT) and dequeue count (DEQCT) are the same, the queue count (QCT) is 0, and all undelivered output messages are discarded if both the following conditions are met:
        • Output messages are not delivered to the IMS TM resource adapter on SYNC_SEND_RECEIVE interactions.
        • The default values for the reRoute property (false) and the purgeAsyncOutput property (true) are used.
      • The enqueue count (ENQCT) is greater than the dequeue count (DEQCT), and the queue count (QCT) is the number of messages that were not delivered to the IMS TM resource adapter if both the following conditions are met:
        • Output messages are not delivered to the IMS TM resource adapter on SYNC_SEND_RECEIVE interactions.
        • The reRoute property is set to true and the purgeAsyncOutput property is set to false
        The tpipe name is the value specified for the reRouteName property. For example, RRNAME, or a default value, for example, HWS$DEF.
      • For SYNC_SEND interactions, output is not expected, and undelivered output does not apply. If SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions are unsuccessful, the queue count does not change.
    • For commit mode 0 interactions on a dedicated persistent socket:
      • Typically, the tpipe name is provided by the Java™ application and does not include a prefix of HWS. For example, CLIENT01. However, you might occasionally see a tpipe name of HWS$DEF, which is the default value for the reRouteName property.
      • The enqueue count (ENQCT) and dequeue count (DEQCT) are the same, and the queue count (QCT) is 0 if all messages are delivered to the IMS TM resource adapter, and no undelivered messages were rerouted from interactions on shareable persistent socket connections.
      • If output messages are not delivered to the IMS TM resource adapter, or rerouted from interactions on shareable persistent socket connections, the enqueue count (ENQCT) is greater than the dequeue count (DEQCT), and the queue count (QCT) is the number of messages that were not delivered. The tpipe name is the client ID name that the user specified. For example, CLIENT01.
    • For output messages inserted to Alternate PCBs:
      • The tpipe name is the name of the Alternate PCB, for example, ALTPCB1.