Verifying the setup for the consumer (callout) usage scenario

To verify that SOAP Gateway is set up properly to pull IMS callout requests from IMS OTMA hold queues, create a connection bundle in SOAP Gateway with the correct connection information, and run the provided IMS Installation Verification Program (IVP) jobs to issue the callout requests from the provided IMS program.

An IMSSOAPCalloutIVPService web service is shipped with SOAP Gateway that receives and processes the callout requests from the IMS IVP jobs. When the SOAP Gateway starts, this web service is automatically deployed.

Prerequisites:

You must complete the configuration steps in Configuring IMS Connect for SOAP Gateway.

For IMS Version 12, you must apply the callout IVP sample APAR PM31536.

The callout IVP sample provides the IVP jobs and tasks in the S series to set up the environment. IV_S230J and IV_S231J are jobs that run the IMS BMP applications by using the IMS DL/I testing program, DFSDDLT0, to issue the callout messages.

Job IV_S230J, when run, issues an asynchronous callout request to a predefined tpipe (IVPPIPE5).
Job IV_S231J, when run, issues a synchronous callout request to a predefined tpipe (IVPPIPE6).

The callout requests are placed in the resume tpipes (hold queues) until they are pulled by SOAP Gateway. Introduction information for the S series is in IV_S001T. Task IV_229T contains information about the COBOL converter samples that you must compile and link-edit into the IMS.SDFSRESL data set before submitting jobs in IV_S230J and IV_S231J.

Table 1. The callout IVP samples on the IMS host system
Type of callout requests	Job	Tpipe	Part name for the COBOL converter source
Asynchronous	IV_S230J	IVPPIPE5	DFSACCBL
Synchronous	IV_S231J	IVPPIPE6	DFSSCCBL

Note: In IMS Version 14, DFSACCBL and DFSASCBL are located in the SDFSISRC data set. In IMS Version 13, DFSACCBL is located in the SDFSISRC data set, and DFSASCBL is located in the SDFSMAC data set. In IMS Version 12, DFSACCBL and DFSASCBL are located in the SDFSSMPL data set.

To compile and link-edit the converters into a data set concatenated with IMS Connect STEPLIB:

The converter must have an alias that is linked with the converter code, using the same name as the converter, with an X suffix. If the converter name is eight-character long, the last character for the alias must be changed to an X.
The converter and the load module name must end with the letter D.

For example, by default the program ID for the provided asynchronous COBOL converter source file is IOGIVPAD. Your link-edit JCL would contain ENTRY, ALIAS, and NAME statements as follows:

//LKED.SYSIN DD * 
INCLUDE RESLIB(CBLTDLI) 
INCLUDE RESLIB(DFSLI000) 
ENTRY IOGIVPAD 
ALIAS IOGIVPAX 
NAME IOGIVPAD(R)

Verify that the static OTMA destination descriptors for IVPPIPE5 and IVPPIPE6 in DFSYDTx reflect the correct converter module names generated above. Changes require an IMS cold start, or use the following command to make effective:
```
UPDATE OTMADESC NAME(IVPDTOR5) SET(TYPE(IMSCON)  +                     
ADAPTER(HWSXMLA0) CONVRTR(IOGIVPAD)) 
```
If you have changed the default SOAP Gateway server HTTP port number, the callout IVP WSDL file, IMSSOAPCalloutIVP.wsdl, must be updated with the port number. Modify the IMSSOAPCalloutIVP.wsdl file in the server WSDL directory and restart the server.

To verify the proper setup for the consumer scenario, you need to update the provided connection bundle to instruct the SOAP Gateway server where to pull the callout request from the tpipe, start the SOAP Gateway server, and then run the two jobs, IV_S230J and IV_S231J, in IMS to issue the callout request.