130 IMS Connectivity in an On Demand Environment: A Practical Guide to IMS Connectivity
9.4.2 Input message returned from message exit
This section describes input messages from the message exit of IMS Connector for Java and
non-IMS Connector for Java message structures.
IMS Connector for Java message structure, type 1
The IMS Connector for Java exit output message format that is supported by IMS Connect is
the same message format of the input message. See Table 9-8 on page 127.
Non-IMS Connector for Java message structure, type 3
Table 9-10 shows the output message format supported by IMS Connect from the supplied
HWSIMSO0 and HWSSMPL0 exits (non-IMS Connector for Java client exits). Variable length
OTMA headers are supported, and therefore, the OTMA header length can be other than 466
bytes. The following example contains 466 bytes as used by the supplied exits.
Table 9-10 Non-IMS Connector for Java message structure, type 3
ZZ 2 (binary) Reserved (set to binary zeros).
DATA n User data.
LL 2 (binary) Length of data segment.
ZZ 2 (binary) Reserved (set to binary zeros).
DATA n User data.
Repeat LL, ZZ, DATA for all segments.
LL 2 (binary) Length of data segment.
ZZ 2 (binary) Reserved (set to binary zeros).
DATA n User data.
LL 2 (binary) End of message (set to X
'0004').
ZZ 2 (binary) Reserved (set to binary zeros).
Field Length (bytes) Meaning
Field Length
(bytes)
Meaning
The first 64 bytes represent the fixed BPE header.
IIII 4 (binary) Length of entire buffer.
CHAIN PTR 4 (binary) Chain pointer to next BPE header.
STORAGE TYPE 8 (character) Storage type.
TYPE ACCESS 4 (character) Type access.
SUBPOOL 1 (binary) Subpool number.
RESV 43 Reserved.
End of BPE header.
Start of user data for this BPE header.

Get IMS Connectivity in an On Demand Environment: A Practical Guide to IMS Connectivity now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.