Exit XWSSRRWI

Use the XWSSRRWI exit to access containers on the current channel, with CICS® acting as a secured Web services requester, after they have been processed by the transport as a Web services response. This exit runs after CICS processes the Web service response and after any instance of the XWSSRROI 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 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.

If the pipeline does not contain a security handler, this exit is not driven. See the Exit XWSRQRWI topic for instances of the pipeline not containing a security handler.

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.
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