Exit XWSRQRWO

Use the XWSRQRWO exit to access containers on the current channel before they are passed to the transport to be processed. This exit runs after CICS® has converted the application's language structure into a Web services request body and before CICS processes the optional XWSRQROO exit point.

You can use this exit to issue API and SPI commands to examine and update any information in the containers on the current channel. This information is available to any instance of the XWSRQRWO exit and also to the outbound Web services provider. You cannot issue a SOAP fault. A return code can be put in register 15 to indicate that CICS does not continue the pipeline after the global user exit program finishes.

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.
UEPPROG
Address of the 8-byte application program name. The application program name is that of the program which 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.
UERCRPIP
Do not continue on the pipeline.
Start of change

XPI calls

No XPI interfaces are available.

End of change

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