The structure of input messages passed to and returned
from a user message exit routine differs based on a number of factors,
including whether the user message exit routine supports the IMS TM
Resource Adapter or
a user-written IMS Connect client.
The following table shows the structure for input messages
received from the client by IMS Connect.
The table provides information about the input message structure type,
if the OTMA header is present or not, if the exit data is translated
by the client code, the exit type flag, and the supporting message
type.
Table 1. Input message structure
| Input message structure
type |
OTMA header present |
Exit data translated
by client code |
Exit type flag (IRMHDR_FLG5) |
Supporting message type |
| 1 |
Y |
Y |
11000000 |
HWSJAVA0 |
| 1 |
Y |
N |
10000000 |
HWSSMPL0 and HWSSMPL1
modified not to build OTMA headers when the client/server builds OTMA
headers |
| 2 |
N |
Y |
01000000 |
HWSSMPL0 and HWSSMPL1
modified not to translate data |
| 2 |
N |
N |
00000000 |
HWSSMPL0 HWSSMPL1 HWSCSLO0 |
The following table shows the structure for input messages
returned by the exit based on the input structure received by the
exit. The table provides information about the input message structure
type, the exit output message structure type, the exit type flag,
and the supporting message type.
Table 2. Input message structure returned
by the exit
| Input message structure
type |
Exit output message structure
type |
Exit type flag (IRMHDR_FLG5) |
Supporting message type |
| 1 |
1 |
11000000 |
HWSJAVA0 |
| 1 |
1 |
10000000 |
HWSSMPL0 and HWSSMPL1
modified not to build OTMA headers when the client/server builds OTMA
headers |
| 2 |
3 |
01000000 |
HWSSMPL0 and HWSSMPL1
modified not to translate data |
| 2 |
3 |
00000000 |
HWSSMPL0 and HWSSMPL1 |