/DISPLAY OTMA command
Use the /DISPLAY OTMA command to display the current status for IMS™ Open Transaction Manager Access (OTMA) clients and servers.
Subsections:
Environment
The /DISPLAY OTMA command is valid in DB/DC and DCCTL environments.
Usage notes
This command is functionally equivalent to the /DISPLAY TMEMBER ALL command.
If a super member is defined, information about the super member is also displayed. Because a super member does not interface with z/OS® cross-system coupling facility (XCF), the XCF_STATUS field is left blank. Because super members do not process input messages, OTMA security authorization is not performed. The SECURITY field is also left blank.
Output fields
This command displays the following output fields:
- ACEEAGE
- The accessor environment element (ACEE) aging value for the OTMA client. This value is used to
perform the refresh for cached OTMA ACEEs for all user IDs.
If the /SECURE OTMA ACEEAGE command is issued to specify a global ACEE aging value, this field displays the aging value that is specified with the /SECURE OTMA ACEEAGE command for the OTMA server.
ACEECT
- The total number of cached OTMA ACEEs for the OTMA server.
- DRUEXIT
- The name of any OTMA Destination Resolution exit routine that is associated with the tmember.
- GROUP/MEMBER
- Each member in each XCF group. The server is always the first member that is displayed.
- INPT
- The maximum number of input messages
from this tmember that can be waiting at the same time to be processed.
This value is primarily used for send-then-commit or CM1 messages.
- 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.
- SECURITY
- The security status for each member or server. The security status
can be one of the following:
- NONE
- CHECK
- FULL
- PROFILE
- SMEM
- The name of the super member.
- TIB
- For an OTMA target member (tmember), the current number of input
messages from this tmember that IMS is
processing. For an OTMA server, the total number of input messages
from all tmembers that IMS is
processing plus the reserved message blocks for message processing.
This value is primarily used for send-then-commit or CM1 messages.
- For the OTMA internal member DFSYICAL, this
field shows the number of IMS regions
that are waiting for responses to synchronous program switch requests.
- T/O
- The timeout value for OTMA to wait
for an ACK or NACK for an OTMA output message.
- TOACEE
- Indicates whether the TOACEE= parameter on the DFSOTMA client descriptor is YES to enable ACEE
flood control or NO to disable ACEE flood control. This status is valid only for the OTMA
server.
- TPCNT
- The maximum TPIPE count for each OTMA client.
For an OTMA client other than the IMS server, this field indicates the current TPIPE count for that member. For the IMS server, this field indicates the global TPIPE limit, which is the highest TPIPE limit set for the OTMA clients. IMS displays a nonzero value only when the MAXTP= keyword is specified for this member in the OTMA client descriptor DFSYDTx member of the IMS PROCLIB data set. If the MAXTP= keyword is not specified for any of the members in the OTMA client descriptor, the TPCNT field of the IMS server member is zero.
- USER-STATUS
- The user status for each member. The status can be one of the
following:
- ACCEPT TRAFFIC
- DISCONNECTED
- FLOOD
- IN SLOWDOWN
- MAX TPIPE
- SERVER
- SERVER+FLOOD
- SMQ BACKEND
- SYNC P2P
- SYNC P2P+FLOOD
- WAIT BID
- WAIT RESPONSE
- XCF-STATUS
- The XCF status
for each member. The status can be one of the following:
- ACTIVE
- CREATED
- FAILED
- NOT DEFINED
- QUIESCED
- STO-INPUT
- UNKNOWN
Examples
The following are examples of the /DISPLAY OTMA command.
Example 1 for /DISPLAY OTMA command
/DISPLAY OTMAGROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
DRUEXIT T/O
HARRY
-IMS1 ACTIVE SERVER FULL
-IMS1 N/A
-HWS001 ACTIVE ACCEPT TRAFFIC FULL 0 0 SM01
-HWS001 HWSYDRU0 5
-SM01 SUPER MEMBER SM01
-SM01 N/A
-MQS001 ACTIVE ACCEPT TRAFFIC FULL 0 0
-MQS001 MQSYDRU0 10Explanation: The /DISPLAY OTMA command can be issued to display the status of IMS server and members. This command is functionally equivalent to the /DIS TMEMBER ALL command. The member information is displayed in random order. In the previous example, HARRY is the XCF group name for IMS and its OTMA clients. IMS1 is the server member running with OTMA activated. HWS001 and MQS001 are OTMA client members. The SM01 is an OTMA super member for asynchronous output messages. Each OTMA client has two-line status information.
Example 2 for /DISPLAY OTMA command
/DISPLAY OTMAGROUP/MEMBER XCF-STATUS USER-STATUS SECURITY
HOANG
-APPL8 NOT DEFINED SERVER FULL
-CLIENT1 ACTIVE ACCEPT TRAFFIC
*94165/165753*Example 3 for /DISPLAY OTMA Command
/DISPLAY OTMAROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
HARRY
-HWS001 ACTIVE ACCEPT TRAFFIC FULL 0 0 SM01
-HWS002 ACTIVE ACCEPT TRAFFIC FULL 0 0 SM01
-SM01 SUPER MEMBER SM01
-HWS003 ACTIVE ACCEPT TRAFFIC FULL 0 0Explanation: The /DISPLAY OTMA command can be issued to display the status for OTMA clients and servers. This command is functionally equivalent to the /DIS TMEMBER ALL command. The member information is displayed in random order.
Example 4 for /DISPLAY OTMA command
/DISPLAY OTMAGROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
DRUEXIT T/O ACEEAGE
XCFGRP1
-IMS1 ACTIVE SERVER FULL 8000
-IMS1 N/A 0
-HWS1 ACTIVE ACCEPT TRAFFIC FULL 0 5000
-HWS1 HWSYDRU0 239 3600
-HWS2 ACTIVE ACCEPT TRAFFIC FULL 0 5000
-HWS2 HWSYDRU0 239 7200
-HWS3 ACTIVE ACCEPT TRAFFIC FULL 0 5000
-HWS3 HWSYDRU0 239 0
*09121/172200* IMS1 Explanation: The /DISPLAY OTMA command can be issued to display the ACEE aging value for the OTMA client or member. OTMA uses this value to determine if a cached ACEE for a user ID needs to be refreshed. In this example, the aging value for HWS1 is 3600 seconds, and the aging value for HWS2 is 7200 seconds. Any cached ACEE that only HWS1 uses has an aging value of 3600 seconds, and any cached ACEE that only HWS2 uses has an aging value of 7200 seconds. If a cached ACEE is used by both HWS1 and HWS2, the aging value is 3600 seconds, which is the lowest value between 3600 and 7200 seconds. Because no aging value is specified for HWS3, IMS always creates a non-cached ACEE for users from HWS3.
Example 5 for /DISPLAY OTMA command
/DISPLAY OTMAGROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
DRUEXIT T/O TPCNT ACEEAGE
XCFGRP1
-IMS1 ACTIVE SERVER FULL 0 8000
-IMS1 N/A 200 3000
-HWS1 ACTIVE MAX TPIPE FULL 0 5000
-HWS1 200 1000 999999
-HWS2 ACTIVE ACCEPT TRAFFIC FULL 0 5000
-HWS2 200 500 999999Explanation: In this example, the TPCNT field indicates the current TPIPE count for each member. For the IMS server, this field indicates the global TPIPE limit, which is the highest TPIPE limit set for the OTMA clients. MAX TPIPE indicates that the TPIPE count for the OTMA client has reached the limit set. This status is cleared when the global TPIPE count falls below 50%.
Example 6 for /DISPLAY OTMA command
Entry ET:
/DISPLAY OTMAResponse ET:
GROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
DRUEXIT T/O
IMSXCFGP
-IMS1 ACTIVE SERVER FULL 30 8000
-IMS1 N/A
-HWS001 ACTIVE ACCEPT TRAFFIC FULL 20 5000
-HWS001 HWSYDRU0 5
-DFSYICAL SYNC P2P FULL 10 5000
-DFSYICAL N/A 5 In this example, IMSXCFGP is the XCF group name for IMS and its OTMA clients. The server member name for OTMA is IMS1. HWS001 and DFSYICAL are the names of the OTMA client members. The DFSYICAL member is an internal OTMA client that processes synchronous program switch requests initiated by DL/I ICAL calls from application programs. The DFSYICAL member has the USER-STATUS of SYNC P2P. The TIB field for the DFSYICAL member shows that there are 10 IMS regions waiting for responses to DL/I ICAL synchronous program switch requests. The HWS001 member is a standard OTMA client member, connected via XCF, that has 20 active messages. The total TIB for this IMS system is 30. None of the members are using an OTMA Destination Resolution exit routine.
Example 7 for /DISPLAY OTMA command
Entry ET:
/DISPLAY OTMAResponse ET:
GROUP/MEMBER XCF-STATUS USER-STATUS SECURITY TIB INPT SMEM
DRUEXIT T/O ACEEAGE
XCFGRP1
-IMS1 ACTIVE SERVER+FLOOD FULL 11000 10000
-IMS1 N/A 0
-HWS1 ACTIVE ACCEPT TRAFFIC FULL 3000 5000
-HWS1 HWSYDRU0 120 0
-HWS2 ACTIVE ACCEPT TRAFFIC FULL 3000 5000
-HWS2 HWSYDRU0 120 0
-HWS3 ACTIVE ACCEPT TRAFFIC FULL 4000 5000
-HWS3 HWSYDRU0 120 0
*09121/172200* IMS1 The /DISPLAY OTMA command can be issued to display the active OTMA messages (TIB) in the system and in each OTMA client. The flood limit (INPT) for the entire system and each OTMA client can also be displayed. In this example, because the global flood limit of the system is set to 10000, the total active OTMA messages (3000 + 3000 + 4000) is 11000, which is over the global limit. The USER-STATUS shows SERVER+FLOOD to indicate that the global flood limit was specified in client descriptor or in the /START TMEMBER ALL INPUT command, and IMS has reached this OTMA global flood limit. The applications that use OTMA clients HWS1, HWS2, and HWS3 must reroute the OTMA transaction to a different IMS. All the new input transactions from all the OTMA clients are rejected with OTMA sense code x’0030’ and reason code x’0002’.