When a service requester pipeline sends a request to a service
provider, there is normally an expectation that there will be a response,
and that, following the sending of the request, the message handlers in the
pipeline will be invoked again when the response arrives. Some Web services
do not send a response, and so you must take special action to indicate that CICS® should
not wait for a response before invoking the message handlers for a second
time.
To do this, ensure that container DFHNORESPONSE is present at
the end of pipeline processing in the request phase. Typically, this is done
by application level code, because the knowledge of whether a response is
expected is lodged in the application:
- For applications deployed with the CICS Web services assistant, CICS code will
create the container.
- Applications that are not deployed with the assistant will typically create
the container before invoking the application.
If you create or destroy container DFHNORESPONSE in a message handler,
you must be sure that doing so will not disturb the message protocol between
the service requester and the provider.