Input message from client and passed to message exit

This topic contains Product-sensitive Programming Interface information.

IMS TM Resource Adapter message structure - type 1

User-written message structure - type 2

The following table shows the input message format supported by IMS Connect for user-written client applications.

The message format is supported by the HWSSMPL0 and HWSSMPL1 user message exit routines, as well as user-written user message exit routines. This message format is not supported by HWSJAVA0, HWSSOAP1, HWSCSLO0, or HWSCSLO1.

If you are using a user-written message exit routine, you can structure the message fields as required by the user exit. You can include fields that are used only by the user message exit or other fields that can be passed in the OTMA headers, such as the MID name.

The following is the data structure for all user-written client applications.

The transaction data in input messages from user-written IMS Connect client applications follows the user-defined IRM, or IRM extensions if extensions are defined, and is contained in one or more data segments. The data segments must conform to the format of LLZZDATA, where LL contains the total length of the data segment, ZZ contains binary zeros, and DATA contains the transaction code and transaction data or an IMS command.

The transaction data in input messages from user-written IMS Connect client applications follows the user-defined IRM and is contained in one or more data segments. The data segments must conform to the format of LLZZDATA, where LL contains the total length of the data segment, ZZ contains binary zeros, and DATA contains the transaction code and transaction data or an IMS command.