Server-Available and Client-Bid commands
The state data for the Server-Available and Client-Bid commands section of the OTMA message prefix is mapped by the TMAMHDR DSECT of the DFSYMSG macro.
The following table summarizes the format for state data for command messages, including byte offset, length, content, hexadecimal value, the meaning, and usage comments.
| Byte | Length | Content | Value | Meaning |
|---|---|---|---|---|
| 0 | 2 | Length | Specifies the total length of the state-data section of the message prefix, including the length field. | |
| 2 | 16 | Member name | Specifies the z/OS® cross-system coupling facility (XCF) member name of originating server. | |
| 18 | 8 | Originator's token | Specifies the XCF-member token of the originator (either client or server) of the message. | |
| 26 | 8 | Destination token | Specifies the XCF-member token of the destination (either client or server) of the message. | |
|
Note: The following fields are present only for client-bid commands.
|
||||
| 34 | 8 | DRU exit name | Specifies the name of the OTMA Destination Resolution exit routine. | |
| 42 | 2 | MaxBlocksize | Specifies the maximum block size for XCF conversations between the server and the client. This field is optional | |
| 44 | 1 | Client-Bid flag | X'80' | Hold Queue: Specifies that a hold queue for a tpipe is needed. The hold queue can hold commit-then-send output that is receives a NAK response, as well as alternate PCB output for an OTMA client. The output messages in the queue will not be delivered until the client requests that those messages be delivered. Use of the hold queue is optional. Without the hold queue, a regular queue for the tpipe will be used to hold and deliver all the Commit-then-send output messages. The default is no hold queue for a tpipe. OTMA resynchronization protocol currently does not support the hold queue. |
| X'40' | Reserved for OTMA Callable Interface. | |||
| X'20' | Reserved for IMS Connect. | |||
| X'10' | Reserved for IBM® MQ. | |||
| X'08' | Reserved for synchronous program switch. | |||
| 45 | 1 | Additional client-bid flags | X'80' | Message flood control: specifies that OTMA use the maximum number of input messages provided by the client-bid command at byte 62 for message flood control. |
| X'20' | Member timeout: specifies that OTMA use the member timeout value for send-then-commit messages provided by the client-bid command at byte 65. | |||
| X'10' | Cascaded transaction support: specifies support for cascading global RRS transactions (synchlevel=2 or syncpoint) from an OTMA client on one LPAR to OTMA on another LPAR. | |||
| X'08' | Super member flag: activates the super member function for this member or client. To use this optional super member function, the member or client needs to set this flag and to specify the super member name, see the super member name at byte 54 below. |
|||
| X'04' | Synchronous callout support: specifies support for synchronous callout messages that are issued by IMS applications. | |||
| X'02' | CM0 timeout queue name: Set CM0 timeout queue name. | |||
| X'01' | IMS-to-IMS TCP/IP communications: Set by IMS Connect to indicate that IMS Connect supports IMS-to-IMS TCP/IP communications. | |||
| 46 | 4 | Aging value | Specifies the accessor environment element (ACEE) aging value in seconds. If the age of an existing ACEE for a user ID is greater than this value, IMS creates a new ACEE. If the aging value specified is less than the supported minimum value, IMS creates a non-cached ACEE. The minimum value for caching support is 300 seconds (5 minutes). |
|
| 50 | 4 | Hash table size | Defines the size of the IMS OTMA hash table for processing multi-segment messages input. The hash table is used to correctly chain all the input segments together. The suggested value is X'00000065'. |
|
| 54 | 4 | Super member name | Specifies a 1-4 byte super member name. When the super member function is activated, all of the asynchronous output messages for hold queue capable member or client, such as IMS Connect, will be shared by a set of clients specifying the same super member name. |
|
| 58 | 2 | Offset to callout token | Specifies the offset in the user data section at which this client expects the synchronous callout token to be placed by OTMA. | |
| 60 | 2 | Offset to remote destination definitions | Specifies the offset in the user data section at which the definitions that are required for delivering the message to a remote IMS system can be found. | |
| 62 | 2 | Message flood threshold value | 0-9999 | Specifies the maximum number of concurrent input messages from this member or client. If 0 is specified, the OTMA default is 5000. Values between 1 and 200 are treated as 200. |
| 64 | 1 | Client-bid flags | X'80' | MULTIRTP=Y is set for this tpipe. The tpipe supports multiple active resume tpipe requests. |
| X'40' | MULTIRTP=N is set for this tpipe. The tpipe supports only one active resume tpipe request at a time. | |||
| X'10' | SENDALTP=Y is set for the IMS Connect data store. The SENDALTP function is activated. IMS delivers an ALTPCB output without RESUME TPIPE calls for IMS Connect. | |||
| X'08' | SENDALTP=N is set for the IMS Connect data store. The SENDALTP function is not activated. IMS queues an ALTPCB output to an OTMA TPIPE hold queue until a RESUME TPIPE call is issued to retrieve it. | |||
| X'04' | TRANORCH=Y is set by the IMS Connect datastore | |||
| X'02' | TRANORCH=N is set by the IMS Connect datastore. | |||
| 65 | 1 | Timeout value for acknowledgments from client | Specifies the member level timeout value in seconds for both commit-then-send (CM0) and send-then-commit (CM1) OTMA messages. For CM1 messages, this timeout value applies only when synclevel=confirm or synclevel=syncpt. Valid timeout intervals are 1 to 255 seconds. If no time out value is specified, the OTMA default is 120 seconds. The timeout value specified in this field cannot be greater than the timeout value set OTMA; otherwise, the value is ignored. The time out value is set in OTMA either by the /START TMEMBER command or the OTMA client descriptor. |
|
| 66 | 8 | CM0 timeout queue name | Specifies an 8-byte name for a tpipe timeout queue for commit-then-send (CM0) output. | |