IRM structures for IMS Connect client messages

IMS Connect expects all client messages that it receives to start with a four byte total length field, followed by an IMS request message (IRM) header, followed by the message data segments.

After the four-byte length field, all IRMs begin with a 28 byte fixed-format section that is common to all messages from all IMS Connect client applications. You cannot modify the format of the fixed section of the IRM.

User-written client applications can include a user-defined section in the IRM after the fixed-format section. The user-defined section of the IRM allows you to specify additional options. If you add or delete any fields in the user-defined section of the IRM, you must also adjust the user message exits that you use, or provide your own user message exits. The user-defined section of the IRM is only supported by the HWSSMPL0 and HWSSMPL1 user message exit routines.

If you are using either the HWSSOAP1 user message exit, which is not provided as source, or the HWSJAVA0 user message exit, you cannot change the user portion of the IRM.

Note: The user message exits HWSCSLO0 and HWSCSLO1 do not have any message definitions because HWSCSLO0 and HWSCSLO1 cannot be modified or replaced.