IMS Connect XML message conversion

For some IMS Connect client application programs, IMS Connect can convert XML messages into either COBOL or PL/I, so that you do not need to modify existing IMS application programs to process messages submitted to IMS in XML.

IMS Connect conversion support converts the XML user data to the language structures expected by the IMS application program, which can then process the message as a normal IMS transaction message.

The IMS Connect XML conversion support is provided by an XML adapter function and an HWSSOAP1 message exit with a COBOL XML converter.

The actual conversion of XML messages is performed by an XML converter, which is called by IMS Connect.

IMS Connect supports XML conversion into the following languages for the following clients:

COBOL
  • IMS Enterprise Suite SOAP Gateway
  • IMS Web 2.0 Solution for IBM® Mashup Center
PL/I
  • IMS Web 2.0 Solution for IBM Mashup Center

IMS Connect also supports the conversion of multi-segment messages between SOAP Gateway and IMS application programs that function as Web service providers and that use multiple language structures. Restrictions apply to the multi-segment message support. These restrictions are detailed in the SOAP Gateway and IBM Developer for System z® documentation.

The IMS Connect HWSSOAP1 exit routine also supports XML conversion and you can specify an XML adapter name and an XML converter name in OTMA destination descriptors.

In the IMS request message (IRM) header of the input message, the IMS Connect client requests XML conversion support by specifying an XML adapter name and an XML converter name. IMS Connect reads the IRM when it receives an input message and, if XML conversion is required, IMS Connect calls the XML adapter. The XML adapter then calls the XML converter to perform the actual conversion. After the message is converted from its XML format, IMS Connect then sends the resulting message to IMS.

When IMS Connect receives the response message from IMS, IMS Connect calls the XML adapter, which in turn calls the XML converter to convert the user data in the response message into XML. IMS Connect then sends the output message to the IMS Connect client.

Using control data in synchronous callout messages to override the XML converter name: In outbound synchronous callout requests that are sent via SOAP Gateway, you can override the XML converter name that is used by IMS Connect. You can do so by having the IMS application program specify a different converter name in the control data area of the DL/I ICAL call when the application program issues the callout request. When the converter name is specified in the control data area, the name must be specified in uppercase EBCDIC characters and enclosed in the <DFSCVTNR> and </DFSCNVTR> tags.