Administering OTMA tmembers

Use the START TMEMBER and STOP TMEMBER commands to start and shut down specific OTMA tmembers and tpipes. The commands also provide parameters to change the size of the input message hold queue and timeout length for enqueued CM1 and CM0 messages.

The /STOP TMEMBER command also clears the wait state (WAIT_A, WAIT_H, or WAIT_S) of all CM0 messages on the tpipe that are waiting for either an ACK or a NAK message from the client.

You can retrieve detailed information about some or all tmembers with the DISPLAY TMEMBER command. You can specify DISPLAY TMEMBER ALL to retrieve a report for all of the configured OTMA tmembers and their associated tpipes, or qualify the command with specific tmember and tpipe names to narrow the search. The response output shows the processing mode for each tpipe, security level, status, workload statistics, and other information.

The enqueue and dequeue counts on a tpipe are updated only for CM0 output messages. The counts are not updated for CM1 messages regardless of the sync level because CM1 messages are not recoverable.

You can also retrieve a list of OTMA tmembers with stopped tpipes by using the DISPLAY STATUS TMEMBER command. This command is useful for determining whether any tmembers require administrator attention. The command also retrieves the name of the super-member for each tmember, if one is configured.

You might need to manually dequeue stalled or stale messages from an OTMA tpipe. For example, you might want to purge stale messages from a tpipe after modifying a client application so that new messages can be retrieved instead. You can use the DEQUEUE command to purge messages from a specific tpipe. The command provides options to dequeue either the first enqueued message for the tpipe or all enqueued messages.

If you need additional information about a tmember or a specific tpipe, you can enable the OTMA client activity trace with the TRACE TMEMBER command. You can also turn on tracing for an entire super member. Use the DISPLAY TRACE TMEMBER command to determine which tmembers and tpipes are currently being traced for an OTMA client. The tracing information is available in the OTMA log records.

A temporary tpipe is created when you issue a /TRACE tpipe or /STOP tpipe command against a tpipe that does not exist. A temporary tpipe is converted to a permanent tpipe if an input message reaches IMS through the tpipe or if an output message is queued to the output queue of the tpipe.

When you issue a /DISPLAY tpipe command against a temporary tpipe, the status of TMP is displayed.