Exit XWSRQRWI
Use the XWSRQRWI exit to access containers on the current channel after they have been processed by the transport as a web services response. The XWSRQRWI exit is invoked directly after CICS® has processed the inbound web service response. It is also invoked after any instance of the XWSRQROI exit.
You can use this exit to issue API and SPI commands to examine and update any information in the containers. This information is processed by the outbound web services provider and is received by the associated web services requester application. You cannot issue a SOAP fault. CICS ignores any return code specified in register 15 after the global user exit program has finished.
Exit-specific parameters
- UEPTRANID
- Address of the 4-byte transaction ID. The exit or task runs under this transaction ID.
- UEPUSER
- Address of the 8-byte user ID. The user ID is the one associated with the transaction ID.
- UEPTERM
- Address of the 4-byte terminal ID.
- UEPPROG
- Address of the 8-byte application program name. The application program name is that of the program that issued the INVOKE SERVICE or INVOKE WEBSERVICE command.
- UEPCHANN
- Address of a 16-byte field that contains the name of the current channel. You can identify the channel explicitly using this parameter.
- UEPCONTR
- Address of a 16-byte field that contains the name of the data container on the channel named by UEPCHANN. This container holds the application data structure.
Return codes
- UERCNORM
- Continue processing.
XPI calls
No XPI interfaces are available.
API and SPI commands
You can use the following commands:- EXEC CICS DELETE CONTAINER
- EXEC CICS GET CONTAINER
- EXEC CICS INQUIRE WEBSERVICE
- EXEC CICS PUT CONTAINER