Displaying output message counts

Using IMS Connect commands, you can choose to display output message counts. This topic describes how to display those message counts.

In IMS™ and OTMA terminology, a transaction pipe (TPIPE) is a logical connection between a client, such as IMS Connect, and the server, such as IMS OTMA. For commit mode 0 interactions, the TPIPE name is the clientID used for the interaction. For commit mode 0 interactions the IMS OTMA Asynchronous Hold Queue associated with the TPIPE has the same name as the clientID.

For commit mode 1 interactions, the TPIPE name is the IMS Connect port number used for the interaction, or in the case of Local Option the TPIPE name is the word, LOCAL. Therefore, each port will have a TPIPE which will be used for all clients running commit mode 1 interactions on that port.

You can use the IMS Connect command /DISPLAY TMEMBER IMSConnect_Name TPIPE ALL to view counts of the output messages sent to IMS Connector for Java, as well as messages inserted to ALTPCBS (Alternate Program Communication Blocks). The following sample output is from a /DISPLAY TMEMBER HWS1 TPIPE ALL command. A brief description of the types of TPIPEs and counts for the command output is also provided.

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
Commit Mode 1 interactions on a shareable persistent socket
  • The TPIPE name is the port number used for the interaction. For example, 9999.
  • The enqueue count (ENQCT) and dequeue count (DEQCT) will be equal and the queue count (QCT) will be 0, because undelivered output messages are not recoverable for commit mode 1 transactions.
Commit Mode 0 interactions on a shareable persistent socket
  • The TPIPE name is generated by IMS Connector for Java and will have a prefix of "HWS". For example, HWSMIJRC.
  • The enqueue count (ENQCT) and dequeue count (DEQCT) will be equal and the queue count (QCT) will be 0 if all messages are delivered to IMS Connector for Java.
  • If output messages are not delivered to IMS Connector for Java on SYNC_SEND_RECEIVE interactions and the default values of reRoute FALSE and purgeAsyncOutput TRUE are used, the enqueue count (ENQCT) and dequeue count (DEQCT) will be equal and the queue count (QCT) will be 0. All undelivered output messages are discarded.
  • If output messages are not delivered to IMS Connector for Java on SYNC_SEND_RECEIVE interactions and reRoute is set to TRUE and purgeAsyncOutput is set to FALSE, then the enqueue count (ENQCT) will be greater than the dequeue count (DEQCT) and the queue count (QCT) will be the number of messages that were not delivered to IMS Connector for Java. 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, so undelivered output does not apply. If SYNC_RECEIVE_ASYNCOUTPUT, SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT and SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT interactions are unsuccessful, the queue count does not change.
Commit Mode 0 interactions on a dedicated persistent socket
  • Typically, the TPIPE name is provided by the Java application and will not have a prefix of "HWS". For example, CLIENT01. However, you may occasionally see a TPIPE name of "HWS$DEF". This is the default value for the reRouteName property.
  • The enqueue count (ENQCT) and dequeue count (DEQCT) will be equal and the queue count (QCT) will be 0 if all messages are delivered to IMS Connector for Java, and no undelivered messages were rerouted from interactions on shareable persistent socket connections.
  • If output messages are not delivered to IMS Connector for Java or rerouted from interactions on shareable persistent socket connections, the enqueue count (ENQCT) will be greater than the dequeue count (DEQCT) and the queue count (QCT) will be the number of messages that were not delivered. The TPIPE name is the user specified clientID name, for example, CLIENT01.
Output messages inserted to ALTPCBs (Alternate Program Communication Blocks)
  • The TPIPE name is the name of the Alternate PCB. For example, ALTPCB1.
Related concepts
Overview of commit mode processing
SYNC_SEND programming model
SYNC_SEND_RECEIVE programming model
Retrieving asynchronous output
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.