/DISPLAY TMEMBER command

Use the /DISPLAY TMEMBER command to display the current target member status for IMS Open Transaction Manager Access (OTMA) clients and servers.

Subsections:

Environment
Syntax
Keywords
Usage notes
Output fields
Examples

Environment

The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the command and keywords.

Table 1. Valid environments for the /DISPLAY TMEMBER command and keywords
Command / Keywords	DB/DC	DBCTL	DCCTL
/DISPLAY	X	X	X
QCNT	X		X
TMEMBER	X		X
TPIPE	X		X

Syntax

Keywords

The following keywords can be specified for the /DISPLAY TMEMBER command.

QCNT

The /DISPLAY TMEMBER command with the QCNT parameter specifies that global queue count information is to be displayed. If the member specified is a super member, global queue count information is displayed for the super member. If the member specified is a regular member whose hold queue output is managed by a super member, the name of the super member is displayed along with the global queue count information for the regular member.

This count represents the message counts of messages that can be processed by the IMS system where the command is issued. This count includes messages that can be processed by any IMS system (messages with no affinity), plus messages that can be processed by the IMS system where the command is issued (messages with an affinity to the IMS system that issued the command).

The /DISPLAY TMEMBER QCNT form of the command is valid only in a shared-queues environment.

TPIPE

The /DISPLAY TMEMBER TPIPE command can be issued to display transaction pipe status for a member. If the member specified is a super member, transaction pipe status is displayed for the super member. If the member specified is a regular member whose hold queue output is managed by a super member, the name of the super member is displayed along with the queue count information.

The tpipe name can be ended with a generic character (*). This generic form of tpipe name can also be used with QCNT or SYNC keywords. The tpipe name with a generic character cannot be mixed with other tpipe names. The valid formats for using a tpipe name with the generic character are:

/DIS TMEMBER membername TPIPE tpipename*
/DIS TMEMBER membername TPIPE tpipename* QCNT
/DIS TMEMBER membername TPIPE tpipename* SYNC

QCNT

The /DISPLAY TMEMBER TPIPE command with the QCNT parameter specifies that global queue count information is to be displayed. If the member specified is a super member, global queue count information is displayed for the transaction pipes associated with the super member. If the member specified is a regular member whose hold queue output is managed by a super member, the name of the super member is displayed along with the global queue count information.

The /DISPLAY TMEMBER TPIPE QCNT form of the command is valid only in a shared-queues environment.

SYNC

The /DISPLAY TMEMBER TPIPE SYNC command displays:

The number of active synchronous callout messages
The number of synchronous callout messages waiting for response
The number of resume tpipe requests that are currently active on the TPIPE
The resume tpipe option
The resume tpipe mode
The tpipe status

The /DISPLAY TMEMBER TPIPE SYNC command can be considered as a superset of the /DISPLAY TMEMBER TPIPE command.

OUTPUT

The /DISPLAY TMEMBER TPIPE OUTPUT command can be used to display the output counts for both primary and holdq queues when the OTMA client is holdq-capable (for example, IMS Connect). This parameter is ignored for clients that are not holdq-capable (such as IBM® MQ) and when IMS has shared queues enabled.

When support for multiple active resume tpipe requests is enabled (MULTIRTP=Y), the output includes the unique identifier, the resume tpipe option, and the mode for each resume tpipe request that is active on a tpipe.

Important: Specifying the OUTPUT parameter can double the number of lines for the display. Take care when using the ALL or masked TPIPE names for TMEMBERs with a large number of TPIPEs.

If support for multiple active resume tpipe requests is enabled (MULTIRTP=Y), the output can include even more lines if there are many active resume tpipe requests on the tpipes.

The OUTPUT parameter is mutually exclusive with the SYNC and QCNT parameters.

Usage notes

The /DISPLAY TMEMBER command includes five variations: /DISPLAY TMEMBER QCNT, /DISPLAY TMEMBER TPIPE, /DISPLAY TMEMBER TPIPE QCNT, /DISPLAY TMEMBER TPIPE SYNC and /DISPLAY TMEMBER TPIPE OUTPUT.

In a shared-queues environment, use the QCNT keyword to obtain the current message queue counts on the shared queues structure. The local queue counts (ENQCT, DEQCT, and QCT) value that is returned on this command when the QCNT keyword is not specified represents the messages being processed by the IMS system where this command is issued. Do not use local queue counts for queue evaluation purposes.

Output fields

The following output fields are displayed for the /DISPLAY TMEMBER command:

DEQCT

Total number of messages that are dequeued from the OTMA tpipe for this member. If the OTMA hold queue is used for a client that is capable of the OTMA hold queue, such as IMS Connect, the number of the messages in the hold queue of this tpipe is also included. In a shared-queues environment, this field shows only the messages dequeued for the local subsystem.

DRUEXIT

The name of any OTMA Destination Resolution exit routine associated with the tmember.

ENQCT

Total number of messages that are enqueued on the OTMA tpipe for this member. If the OTMA hold queue is used for a client that is capable of the OTMA hold queue, such as IMS Connect, the number of the messages in the hold queue of this tpipe is also included. In a shared-queues environment, this field shows only the messages enqueued for the local subsystem.

GROUP/MEMBER

Each member in each z/OS® cross-system coupling facility (XCF) group.

When you issue /DISPLAY TMEMBER ALL, the server is always the first member displayed.

INPT

The maximum concurrent input message count for this member that can be waiting at the same time to be processed. If the YTIBs reach the INPT value, an OTMA FLOOD condition exists and the subsequent input messages from the member will be rejected.

MAXTP

The maximum TPIPE limit that is specified in the OTMA client descriptor. If the MAXTP parameter is specified for DFSOTMA in the OTMA client descriptor, the MAXTP limit is displayed for the OTMA server. If there are one or more OTMA clients with the MAXTP limit defined and MAXTP is not specified for DFSOTMA, the highest limit defined among the members is displayed for the OTMA server.

MODE

The resume tpipe mode, which can be one of the following:

S - Synchronous callout messages
B - Both asynchronous messages and synchronous callout messages
A - Asynchronous messages

NO-COT

The current number of ICAL messages received for this tpipe. If the number is greater than or equal to 65535, it will be reset to 1.

OPT

The resume tpipe option, which can be one of the following:

N - No auto flow of messages. When a client issues a resume tpipe call and no message is present, the resume tpipe call ends.
S - Single message. When a client issues a resume tpipe call, if multiple messages are present, only one message is retrieved. If no message is present, the call ends.
A - Auto flow of messages. The client retrieves one message at a time. If no messages exist in the tpipe, the client waits for subsequent messages from the hold queue.
W - Single message with wait option. The client will retrieve only one message. If there are no messages in the hold queue, the client will wait until a message arrives, then the call ends. Only one message is retrieved regardless of how many messages are in the hold queue.

This option is specified in the IRM_F5 field of the IRM prefix in the messages that are sent to IMS Connect.

QCT

Total number of messages that are still in the queue for OTMA tpipe for this member. If the OTMA hold queue is used for a client that is capable of the OTMA hold queue, such as IMS Connect, the number of the messages in the hold queue of this tpipe is also included. In a shared-queues environment, this field shows only the messages enqueued for the local subsystem.

RTA

The number of active Resume TPIPE requests. This field is displayed only when the SYNC keyword is specified on the command.

RTQ

The number of queued resume tpipe requests to be processed. This field is displayed only for the command issued with the SYNC keyword.

SECURITY

The security status for each member or server

The security status can be one of the following:

NONE
JOIN
CHECK
FULL
PROFILE

SYNCOT

The number of active synchronous callout messages.

TIB

The number of current input messages processed by OTMA for this member. This number will be incremented when a new transaction is received, and it will be decremented after OTMA enqueues a CM0 input transaction or OTMA completes a CM1 transaction. There are cases where orphaned transaction instance blocks (YTIBs) are created. These YTIBS will not be deleted until IMS is cold started.

TPCNT

The TPIPE count for the OTMA client or for the IMS server.

For an OTMA client, this field indicates the current TPIPE count for that member. For the IMS server, this field indicates the current global TPIPE count for the IMS server. This count value is limited to display at most 99999. When 99999 is displayed, it indicates the TPIPE count is 99999 or higher.

T/O

The timeout value for OTMA send-then-commit message responses.

USER-STATUS

The user status for each member.

The status can be one of the following:

ACCEPT TRAFFIC
DISCONNECTED
IN SLOWDOWN
MAX TPIPE: MAX TPIPE indicates that the OTMA member's TPIPE count has reached the limit set. This status is cleared when the global TPIPE count falls below 50%.
SERVER
SUPER MEMBER
WAIT BID
WAIT RESPONSE

If the member specified is a regular member whose member name is displayed as part of the command output. If the member specified is a super member, the character string 'SUPER MEMBER' is displayed for the user status. Since a super member does not interface with XCF, the XCF-STATUS field is left blank. Since super members do not process input messages, OTMA security authorization is not performed.

XCF-STATUS

The XCF status for each member.

The status can be one of the following:

ACTIVE
CREATED
FAILED
FLOOD
NOT DEFINED
QUIESCED
STO-INPUT
UNKNOWN

If the server leaves the XCF group (for example, because of a /STOP OTMA command), then the XCF status is displayed as NOT DEFINED.

The output from the /DISPLAY TMEMBER QCNT or /DISPLAY TMEMBER TPIPE QCNT command includes the following:

AFFINITY: The IMSID (or the first 7 bytes of the RSENAME, if XRF capable) of the IMS to which the output messages have affinity.
GBLQCT: The total number of OTMA output messages on the global queue. The global queue count includes messages that were placed on the global queue before the latest cold start of the owning IMS. Synchronous and asynchronous OTMA output messages are included in the global queue count. Messages on an OTMA asynchronous hold queue for IMS Connect are also included in the global queue count.
MEMBER/TPIPE: OTMA member name. If the TPIPE keyword is specified, the transaction pipe name is also displayed. The first line displays the OTMA member name. The second and subsequent lines display the names of the transaction pipes associated with the OTMA member.

One of the following status terms is displayed for the /DISPLAY TMEMBER command specified with the TPIPE keyword:

DQF: Dequeue request for OTMA REPresynch command failed.
FLOOD: Input from this tmember is suppressed because of a message flood condition.
HLDQ: Queue counts for the holdq queue.
INPCT: The current number of input messages received for this tpipe.
MCP: In a shared-queues environment, the transaction pipe has output messages on the global queue.
PMRY: Queue counts for the primary queue.
REP: IMS is waiting for an OTMA REPresynch command from the client.
REQ: IMS is sending an OTMA REQresynch command to the client.
RSF: Reset request failed for an OTMA REPresynch command.
STO: The transaction pipe is stopped.
STO-INPUT: Input from this tmember is stopped.
SYN: The transaction pipe is being synchronized.
TBR: IMS is waiting for an OTMA TBResynch command from the client.
TMP: The transaction pipe is temporary.
TRA: The transaction pipe is being traced.
WAIT_A: The transaction pipe is waiting for an ACK or NAK for a commit-then-send (CM0) output response.
WAIT_H: The transaction pipe is waiting for an ACK or NAK for a commit-then-send (CM0) output response from the asynchronous hold queue.
WAIT_R: The transaction pipe is waiting for an ACK or NAK response to a commit-then-send (CM0) output message that was sent to a remote IMS system through a TCP/IP connection managed by IMS Connect.
WAIT_S: The transaction pipe is waiting for an ACK or NAK for a synchronous callout message.

Examples

The following are examples of the /DISPLAY TMEMBER command.

Example 1 for /DISPLAY TMEMBER command

Entry ET:

  /DISPLAY TMEMBER ALL

Response ET:

GROUP/MEMBER XCF-STATUS USER-STATUS    SECURITY  TIB INPT SMEM 
               DRUEXIT  T/O           
 HARRY                                          
 IMS1         ACTIVE     SERVER           FULL   
 HWS001       ACTIVE     ACCEPT TRAFFIC   FULL    0   0   SM01 
 HWS001        HWSYDRU0   5                         
 SM01                    SUPER MEMBER                     SM01 
 MQS001       ACTIVE     ACCEPT TRAFFIC   FULL    0   0   
 MQS001        MQSYDRU0  10

Explanation: The /DISPLAY TMEMBER ALL command can be issued to display the current status of IMS server and members. This command is functionally equivalent to the /DIS OTMA command. The member information is displayed in random order. In the above example, HARRY is the XCF group name for IMS and its OTMA members. IMS1 is the server running with OTMA activated. HWS001 and MQS001 are OTMA client members. The SM01 is an OTMA super member for asynchronous output messages. Each OTMA member has two-line status information

Example 2 for /DISPLAY TMEMBER command

Entry ET:

  /DISPLAY TMEMBER MQS001

Response ET:

GROUP/MEMBER XCF-STATUS USER-STATUS    SECURITY TIB INPT SMEM 
              DRUEXIT  T/O                                   
MQS001       ACTIVE     ACCEPT TRAFFIC   FULL    0   0       
MQS001        MQSYDRU0  10

Explanation: In the above example, MQS001 is an OTMA member without using super member function. There are two-line status information for the MQS001.

Example 3 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS001 HWS002 HWS003

Response ET:

 GROUP/MEMBER XCF-STATUS USER-STATUS    SECURITY TIB INPT SMEM
               DRUEXIT  T/O                         
 HWS001       ACTIVE     ACCEPT TRAFFIC   FULL    0    0  SM01
 HWS001        HWSYDRU0   5                           
 HWS002       ACTIVE     ACCEPT TRAFFIC   FULL    0    0  SM01
 HWS002        HWSYDRU1   5                          
 HWS003       ACTIVE     ACCEPT TRAFFIC   FULL    0    0 
 HWS003        HWSYDRU2   5

Explanation: In the above example, HWS001, HWS002 and HWS003 are all regular OTMA members. OTMA hold queue output for HWS001 and HWS002 is managed by super member SM01. HWS003 manages its own OTMA hold queue output without using the super member.

Example 4 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS001 SM01

Response ET:

GROUP/MEMBER XCF-STATUS USER-STATUS    SECURITY TIB INPT SMEM     
HWS001         ACTIVE   ACCEPT TRAFFIC   FULL    0   0   SM01     
SM01                    SUPER MEMBER                     SM01

Explanation: HWS001 is a regular member whose hold queue output is managed by super member SM01. SM01 is a super member. The XCF-STATUS field and the SECURITY field are left blank. The super member name is repeated in the SMEM field.

Example 5 for /DISPLAY TMEMBER command

Entry ET:

  /DISPLAY TMEMBER CLIENT1 TPIPE ALL

Response ET:

MEMBER/TPIPE          ENQCT      DEQCT        QCT STATUS
CLIENT1                                           TRA
-TPIPE1                   0          0          0 TRA,STO
-TPIPE2                   2          2          0 TRA,STO
-TPIPE3                   1          0          1 TRA,STO
*94165/170756*

Example 6 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEMBER CLIENT1 QCNT

Response ET:

MEMBER/TPIPE     GBLQCT     AFFINITY
CLIENT1              34     SYS3
*03203/124035*

Example 7 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEMBER CLIENT1 TPIPE TPIPE3 TPIPE1 QCNT

Response ET:

MEMBER/TPIPE     GBLQCT     AFFINITY
CLIENT1
-TPIPE3              16     SYS3
-TPIPE1               8     SYS3
*03202/143253*

Example 8 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEMBER CLIENT1 TPIPE ALL QCNT

Response ET:

MEMBER/TPIPE     GBLQCT     AFFINITY
CLIENT1
-TPIPE3              16     SYS3
-TPIPE2              16         SYS3
-TPIPE1               2     SYS3
*03202/143253*

Example 9 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEMBER HWS001 QCNT

Response ET:

MEMBER/TPIPE          GBLQCT  AFFINITY      SMEM     
 HWS001                    1  SYS3          SM01     
 *03203/124035*

Explanation: HWS001 is a regular member whose hold queue output is managed by super member SM01. There is one CM0 output message on the OTMA output queue for member HWS001. That message has affinity to SYS3. The /DIS TMEMBER QCNT command can be issued with the super member name (SM01) specified as the member name to determine the number of messages on the super member's output queue.

Example 10 for /DISPLAY TMEMBER command

Entry ET:

 /DIS TMEMBER SM01 QCNT

Response ET:

MEMBER/TPIPE          GBLQCT  AFFINITY      SMEM    
 SM01                     46                SM01    
 *03203/124035*

Explanation: SM01 is a super member. There are 46 CM0 output messages on the output queue for SM01. These messages do not have affinity to any IMS subsystem. Any member whose hold queue output is managed by SM01 can retrieve the output messages.

Example 11 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS003 TPIPE TPIPE1

Response ET:

MEMBER/TPIPE          ENQCT   DEQCT    QCT    STATUS      SMEM    
HWS003                                                            
-TPIPE1                   3       2      1    TRA

Explanation: HWS003 is a regular member that manages its own hold queue output. There is one output message queued for TPIPE1. This message is either on the I/O PCB output queue or the hold queue.

Example 12 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS001 TPIPE TPIPE1

Response ET:

MEMBER/TPIPE          ENQCT   DEQCT    QCT    STATUS      SMEM 
HWS001                                                    SM01 
-TPIPE1                   0       0      0    TRA

Explanation: HWS001 is a regular member whose hold queue output is managed by super member SM01. There are no output messages queued to HWS001, but there might be some messages queued to the hold queue of super member SM01.

Example 13 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER SM01 TPIPE TPIPE1 TPIPE2

Response ET:

MEMBER/TPIPE          ENQCT   DEQCT    QCT    STATUS      SMEM 
SM01                                                      SM01 
-TPIPE1                   3       2      1    TRA              
-TPIPE2                   2       2      0    TRA

Explanation: SM01 is a super member with transaction pipes defined for TPIPE1 and TPIPE2. Local queue count information is displayed for TPIPE1 and TPIPE2. There is one output message on the hold queue for TPIPE1.

Example 14 for /DISPLAY TMEMBER command

Entry ET:

 /DIS TMEMBER SM01 TPIPE ALL QCNT

Response ET:

MEMBER/TPIPE          GBLQCT  AFFINITY      SMEM    
 SM01                                       SM01   
 -TPIPE1                    2                       
 -TPIPE2                    5                       
 -TPIPE3                   16                       
 *03202/143253*

Explanation: SM01 is a super member. There are 23 CM0 output messages on the output queues for SM01. Two messages are queued for TPIPE1, five for TPIPE2 and sixteen for TPIPE3. These messages do not have affinity to any IMS subsystem. Any member whose hold queue output is managed by super member SM01 can retrieve the output messages.

Example 15 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEMBER HWS1 TPIPE ALL SYNC

Response ET:

(screen 1)
 MMR/TPIP         ENQCT      DEQCT        QCT      INPCT OPT MODE 
 HWS1                                                             
-TPIPE1               0          0          0          0  W    S  

(scrolled to the right, screen 2)
SYNCOT NO-COT RTA RTQ STATUS  SMEM    IMS1

     1      1   1   1 WAIT_S  IMS1

Explanation: HWS1 is a regular member with a transaction pipe defined for TPIPE1. The resume tpipe call is to retrieve only synchronous callout messages from the hold queue ("S" for MODE). The request message (from the hold queue) has been sent to the client, IMS Connect, which in turn will send the message to the application client as a result of the resume tpipe call with MODE of "S" and OPT of "W". This accounts for the count of 1 under the column heading SYNCOT. The count of 1 under the column heading NO-COT indicates that the accumulated ICAL count for this OTMA tpipe is 1. Because OTMA is waiting for ACK or NAK, WAIT_S is displayed under column heading STATUS.

To extend the processing, assuming that the client application sends an ACK, the WAIT_S under column heading STATUS will no longer be displayed, and the count of 1 under column heading NO-COT will still be displayed. This output indicates that OTMA has processed one ICAL message for the IMS callout application. Once the OTMA has received the message response and passed it back to the IMS callout application, SYNCOT will show 0, and NO-COT will still show 1. And, when OTMA has completed processing the message response, the resume tpipe call ends, and the output display should show OPT='-', MODE='-', SYNCOT=0, NO-COT=1, and STATUS=' '.

The number of queued tpipe requests is 1.

Entry ET:

/DISPLAY TMEMBER HWS1 TPIPE TPIPE1

Response ET:

MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT STATUS   SMEM    IMS1
 HWS1                                                                      
-TPIPE1                   0          0          0          0 WAIT_S   IMS1

Explanation: TPIPE1 is waiting for a NAK or ACK for a synchronous callout message.

Example 16 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS1

Response ET:

GROUP/MEMBER      XCF-STATUS   USER-STATUS    SECURITY  TIB
INPT SMEM
                    DRUEXIT  T/O TPCNT ACEEAGE
XCFGRP1
-HWS1             ACTIVE       MAX TPIPE      FULL        0
5000
-HWS1                        200  1000  999999

Explanation: In this example, the TPCNT field indicates the current TPIPE count for member HWS1. MAX TPIPE indicates that the TPIPE count for the OTMA member HWS1 has reached the limit set. This status is cleared when the global TPIPE count falls below 50%.

Example 17 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS1

Response ET:

GROUP/MEMBER      XCF-STATUS   USER-STATUS    SECURITY  TIB
INPT SMEM
                    DRUEXIT  T/O TPCNT ACEEAGE MAXTP
XCFGRP1
-HWS1             ACTIVE       ACCEPT TRAFFIC FULL        0
5000
-HWS1                        200  500      120     0

Explanation: In this example, the TPCNT field indicates that the current TPIPE count for member HWS1 is 500 and that there is no MAX TPIPE limit set for this member in the OTMA client descriptor.

Example 18 for /DISPLAY TMEMBER command

Entry ET:

/DISPLAY TMEMBER HWS2

Response ET:

GROUP/MEMBER      XCF-STATUS   USER-STATUS    SECURITY  TIB
INPT SMEM
                    DRUEXIT  T/O TPCNT ACEEAGE MAXTP
XCFGRP1
-HWS2             ACTIVE       ACCEPT TRAFFIC FULL        0
5000
-HWS2                        200  500     120  10000

Explanation: In this example, the TPCNT field indicates that the current TPIPE count for member HWS2 is 500 and that there is a MAX TPIPE limit of 10000 set for this member.

Example 19 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEM HWS1 TPIPE ALL

Response ET:

DFS000I     MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT  STATUS   SMEM
DFS000I     HWS1                                                         
DFS000I    -9999                      0          0          0          1 
DFS000I    -CLIENT02                  3          2          1          2 
DFS000I    -CLIENT01                  8          5          3          5

Example 20 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEM HWS1 TPIPE ALL OUTPUT

Response ET:

DFS000I     MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT  STATUS   SMEM
DFS000I     HWS1                                                         
DFS000I    -CLIENT03                  1          1          0          1  PMRY 
DFS000I    -CLIENT03                  1          0          1          0  HLDQ
DFS000I    -9999                      0          0          0          1  PMRY
DFS000I    -CLIENT02                  1          1          0          1  PMRY  
DFS000I    -CLIENT04                  1          1          0          1  PMRY 
DFS000I    -CLIENT04                  1          0          1          0  HLDQ

Example 21 for /DISPLAY TMEMBER command

Entry ET:

/DIS TMEM HWS1 TPIPE CLIENT* OUTPUT

Response ET:

DFS000I     MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT  STATUS   SMEM
DFS000I     HWS1                                                         
DFS000I    -CLIENT02                  2          2          0          2  PMRY
DFS000I    -CLIENT02                  1          0          1          0  HLDQ
DFS000I    -CLIENT01                  5          5          0          5  PMRY
DFS000I    -CLIENT01                  3          0          3          0  HLDQ

Example 22 of /DISPLAY TMEMBER command for TPIPEs that support multiple active resume TPIPE requests

Entry ET:

/DIS TMEM HWS1 TPIPE OTMACL* OUTPUT

Response ET:

DFS000I     MEMBER/TPIPE          ENQCT      DEQCT        QCT      INPCT  STATUS
DFS000I     HWS1 
DFS000I    -OTMACL99                  0          0          0          0  PMRY WAIT_S
DFS000I    -OTMACL99                  0          0          0          0  HLDQ
DFS000I    -OTMACL99              RT 1234567890123456   OPT A     MODE B 
DFS000I    -OTMACL99              RT 1234567890123457   OPT A     MODE B  WAIT_S 
DFS000I    -OTMACL99              RT 1234567890123458   OPT A     MODE B