Verifying the setup for the IMS asynchronous callout function

To verify that SOAP Gateway is set up property to pull IMS callout requests from IMS OTMA hold queues, update the provided connection bundle in SOAP Gateway, and run the provided IMS Installation Verification Program (IVP) jobs to issue an asynchronous callout request.

See the prerequisites described in Verifying the setup for the consumer (callout) usage scenario.

To verify the proper setup for the IMS asynchronous callout function:

In SOAP Gateway, update the provided imssoapcalloutivp connection bundle to specify the IMS host system, port number, data store, and the tpipe name.
1. Navigate to the install_dir/imsserver/deploy directory.
2. Issue the following SOAP Gateway management utility command:
```
iogmgmt -conn -u -n imssoapcalloutivp -h YourHostName -p YourPortNumber 
-d YourDataStore -i  IVPPIPE5
```
  - The connection bundle must be named imssoapcalloutivp. This connection bundle name is already specified in the callout web service that is automatically deployed when the SOAP Gateway server is started.
  - YourHostName is the name or IP address of the host system where IMS Connect is running.
  - YourPortNumber is the port number to access IMS Connect.
  - YourDataStore is the data store name.
  - The tpipe name must be set to IVPPIPE5. This tpipe name is specified in the OTMA destination description that is provided in the IMS callout IVP sample.
Start the SOAP Gateway server.
- On z/OS®, use the z/OS START command:
```
/S AEWIOGPR
```
Important: If the server is already started, you must restart the server for the changes to take effect.

Wait until the SOAP Gateway server is now up and running message displays.
In IMS, run the IMS callout application by running job IV_S230J.
Job IV_S230J runs the JCL that uses the DFSDDLT0 test program to issue an ISRT ALTPCB call to send a message to tpipe IVPPIPE5.
The IVP callout application input is:
```
 THIS IS A ONE-WAY ASYNCHRONOUS CALLOUT MESSAGE FROM IMS
```
Because this request is a one-way asynchronous callout, there is no response from the web service.

From the SOAP Gateway log, if you see the following message, you have successfully issued an asynchronous callout request from IMS, through SOAP Gateway, to an external web service.

ERROR: Callout Job (*IMSRT*imssoapcalloutivp*IOG*IVPPIPE5:0): got SOAPException - IOGS0077E: An error occurred during the invocation of the external web service: cause: null, message: The input stream for an incoming message is null., fault details: null, fault reason: The input stream for an incoming message is null., fault message: The input stream for an incoming message is null., fault localized message: The input stream for an incoming message is null., fault cause: null, fault code: null, fault code element: null, fault action:null, fault node: null, fault role: null, fault type: 0, fault reason element: null

Tips:

By default, the SOAP Gateway log file imssoap.log is stored in install_dir/imsbase/logs.
In this sample, the web service is hosted on the same SOAP Gateway server.