Configuring XML conversion support for IMS Connect clients
You must configure IMS Connect to convert the input and output messages between an IMS Connect client and an IMS application from XML to a language-specific structure, when the IMS Connect client is IMS Enterprise Suite SOAP Gateway.
The following information does not apply to IMS Connect clients that are IMS Universal drivers or custom-built applications that use the Distributed Relational Database Architecture™ (DRDA) protocol.
Prerequisites:
- You must have the COBOL copybook or the PL/I source files for the IMS application program that processes the input messages or issues a callout request.
- You must increase the IMS Connect region size to accommodate the storage used by the XML converters.
- You must have IMS Enterprise Suite SOAP Gateway.
IMS Connect can convert the XML data contained in the message from an IMS Connect client into the COBOL or PL/I data used by an IMS application program. The COBOL or PL/I data in the corresponding output message is also converted back to the XML data that the IMS Connect client expects. This XML conversion support enables IMS to accept IMS Connect client messages in an XML format without modifying IMS application programs to support XML natively.
The XML conversion function supports conversion of single-segment and multi-segment messages. See the SOAP Gateway and IBM® Developer for System z® documentation for the restrictions that apply to multi-segment message support.
<DFSCVTNR>
and </DFSCNVTR>
tags.- IMS Enterprise Suite SOAP Gateway is the only supported client.
- Inbound and outbound messages must be encoded in UTF-8 because IMS Enterprise Suite SOAP Gateway supports only UTF-8. This encoding must match the encoding of the XML Converter that is being requested.
- IMS Connect provides XML conversion support for commit mode 1 and sync level 0 messages.
The XML conversion function supports conversion of single-segment and multi-segment messages. See the SOAP Gateway and IBM Developer for System z documentation for the restrictions that apply to multi-segment message support.
To configure IMS Connect to convert XML data from the client into COBOL or PL/I IMS application program data, you must perform the following basic steps:
Procedure
Example IMS Connect configuration statements:
***************************************************
* HWS EXAMPLE OF INCLUDING XML ADAPTER SUPPORT
***************************************************
HWS=(ID=HWS8,RACF=Y,XIBAREA=20)
TCPIP=(HOSTNAME=MVSTCPIP,RACFID=RACFID,
PORTID=(9999,LOCAL),MAXSOC=2000,TIMEOUT=8800,
EXIT=(HWSSMPL1,HWSSOAP1))
ADAPTER=(XML=Y)
***************************************************
Example JCL to compile and link a COBOL program:
//COBLNK JOB (PLS,81038),'user',CLASS=A,REGION=4096K,
// MSGLEVEL=(1,1),MSGCLASS=A,NOTIFY=user
//*************************************************************
//* JOB TO COMPILE AND LINK A COBOL PROGRAM
//*************************************************************
//COMP EXEC PGM=IGYCRCTL
//STEPLIB DD DSN=COBOL.V3R4.X,DISP=SHR
//SYSIN DD DSN=COBOL.SOURCE(NNNNNNND),DISP=SHR
//SYSLIN DD DSN=&OBJ,SPACE=(3040,(40,40),,,ROUND),UNIT=VIO,
// DISP=(MOD,PASS),
// DCB=(BLKSIZE=3040,LRECL=80,RECFM=FBS,BUFNO=1)
//SYSUT1 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT2 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT3 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT4 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT5 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT6 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSUT7 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
/*
//**************************************************************
//LKED EXEC PGM=IEWL,COND=(4,LT,COMP),
// PARM='LIST,LET,XREF,MAP'
//SYSLIB DD DSN=CEE.SCEELKED,DISP=SHR
// DD DSN=CEE.SCEEBIND,DISP=SHR
// DD DSN=CEE.SCEEBND2,DISP=SHR
//SYSLIN DD DSN=&OBJ,DISP=(OLD,DELETE)
// DD DDNAME=SYSIN
//SYSLMOD DD DSN=IMSCONN.AUTHLIB,DISP=SHR
//SYSUT1 DD UNIT=VIO,SPACE=(1024,(120,120),,,ROUND)
//SYSPRINT DD SYSOUT=*
//LKED.SYSIN DD *
ENTRY NNNNNNND
ALIAS NNNNNNNX
NAME NNNNNNND(R)
/*
For information about the XML, COBOL, and PL/I data structures of converted input and output messages, see IMS Version 15 Application Programming.