Retrieve information about work requests in the local CICS region.
INQUIRE WORKREQUEST >>-INQUIRE WORKREQUEST(data-value)------------------------------> >--+-------------------------+--------------------------------->< +-WORKTYPE(cvda)----------+ +-CLIENTIPADDR(data-area)-+ +-CORBASERVER(data-area)--+ +-LISTENERPORT(data-area)-+ +-OAPPLID(data-area)------+ +-OTASK(data-area)--------+ +-OTRANSID(data-area)-----+ +-REQUESTID(data-area)----+ +-STACK(data-area)--------+ +-TASK(data-area)---------+ +-TRANSID(data-area)------+ '-TSYSTEM(data-area)------'
Conditions: ILLOGIC, NOTAUTH, NOTFND
This command is threadsafe.
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE WORKREQUEST command allows you to track tasks that are started as a result of action by a request receiver.
A listener region in CICS is an example of a RequestReceiver. A single RequestReceiver can start one RequestProcessor which in turn can start more RequestReceivers or RequestProcessors.
The RequestReceiver and RequestProcessor relationship is not the same as any other type of transaction relationship. A RequestReceiver need not remain in the system after it has initiated a RequestProcessor; if there are no more requests to be received it terminates. A RequestProcessor may create RequestReceivers during the course of its processing - outbound and loopback requests.
INQUIRE WORKREQUEST enables you to inquire about a single work request in the local region, or to browse through all the work requests in the local region. The information returned by INQUIRE WORKREQUEST allows you to:
Work Requests are identified by tokens. Each token is unique in the local system for the lifetime of the request, but subsequently, tokens can be reused.
You can use the browse options (START, NEXT, and END) on INQUIRE WORKREQUEST commands, to browse through all of the work requests present in the local region. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
The work requests are not returned in a defined order, so you cannot use START AT to specify a start point.
Each time a request receiver creates a work request it sets up a stack, and records a value of ‘1’. Then, when the request receiver issues a method request it increments the stack, and each time that a bean in this "chain of requests" issues a method request to another bean it increments this stack. There is one stack created for each request receiver, and the stack applies across the sysplex. The stack is decremented each time a bean that has incremented it terminates.