Specifying a remote transaction code
OTMA messages sent to a remote IMS system can include a transaction code to schedule a transaction to process the message in the remote IMS system.
The transaction code can be specified by the sending application program, an OTMA destination descriptor, or both.
If a transaction code is specified by the application program, it is included in the first 8 bytes of the data portion of the outgoing message.
If a transaction code is specified by an OTMA destination descriptor, IMS Connect increases the length of the message by 8 bytes and inserts the transaction code into the message between the length field and the data section. If the transaction code is less than 8 bytes, the remainder is padded with blanks.
The specification of a transaction code by an OTMA destination descriptor is independent of the specification of a transaction code by a sending application program. If both the application program and the OTMA destination descriptor specify a transaction code, both are included in the outgoing message and the remote IMS system must be able to process both.
For example, if an application specifies a transaction code, the format of the message is LLZZMSGDATA, where the LLZZ section contains the length of the message and the MSGDATA section contains both the transaction code and the message data. If an OTMA destination descriptor also specifies a transaction code, the message length is increased by 8 bytes and the format of the message becomes LLZZTRANCODEMSGDATA, where TRANCODE contains the transaction code specified on the OTMA destination descriptor.