Retrieve information about a queued request.
INQUIRE REQID >>-INQUIRE REQID(data-value)--+---------------+-----------------> '-REQTYPE(cvda)-' >--+-------------------+--+--------------------+----------------> '-TERMID(data-area)-' '-TRANSID(data-area)-' >--+--------------------------------------------+---------------> +-INTERVAL(data-area)------------------------+ +-TIME(data-area)----------------------------+ +-AFTER--| hours |--| minutes |--| seconds |-+ '-AT--| hours |--| minutes |--| seconds |----' >--+------------------------------------------------------+-----> '-SET(ptr-ref)--LENGTH(data-area)--+-----------------+-' '-FMHSTATUS(cvda)-' >--+---------------------+--+--------------------+--------------> '-RTRANSID(data-area)-' '-RTERMID(data-area)-' >--+------------------+--+-------------------+----------------->< '-QUEUE(data-area)-' '-USERID(data-area)-' hours: |--HOURS(data-area)---------------------------------------------| minutes: |--MINUTES(data-area)-------------------------------------------| seconds: |--SECONDS(data-area)-------------------------------------------|
Conditions: END, ILLOGIC, INVREQ, NOTAUTH, NOTFND
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE REQID command returns information about a queued request. A queued request results from a DELAY, POST, ROUTE, or START command with a nonzero expiry time, and it lasts until that time. For a DELAY command, expiry time is the end of the delay; for a POST, it is the time at which posting is to occur; for a ROUTE, it is the time at which the message is to be delivered; and for a START, it is the time at which CICS is to create the requested task.
After a request expires, you cannot inquire about it with INQUIRE REQID, even if the action requested is not complete. For example, a request to START a transaction may be delayed beyond expiry time, waiting for the terminal it requires.
Requests are identified by the REQID value in the originating command (or assigned by CICS, if omitted in the command). REQID values should be and normally are unique; however, if there is more than one queued request with the same identifier, INQUIRE REQID returns information about the one that will expire soonest.
Expiry time can be expressed either as an interval (the length of time from your INQUIRE to expiry) or as an absolute value (the length of time after the midnight previous to your INQUIRE). If expiry is before midnight of the current day, absolute time is the same as time-of-day, using a 24-hour clock. You can request either form, regardless of how the time was specified in the command that created the request.
There are also two formats for expiry time, whether it is an absolute value or an interval:
Expiry time and request type (the type of command that produced it) are available for any queued request. For START requests additional information is available, including data passed from the starting to the started task.
START commands have four options for passing data. The FROM option is primary, and allows you to pass data of variable length, but three others--QUEUE, RTERMID, and RTRANSID--allow you to pass small items of fixed length. They are intended for convenience in conveying resource names to the started transaction, but are not restricted to that purpose. All four data items are kept in temporary storage, and consequently are subject to explicit deletion by another task. If data that you request in an INQUIRE REQID command has been deleted from temporary storage or cannot be read because of an I/O error, CICS raises the INVREQ condition.
You also can browse through all of the queued requests by using the browse options (START, NEXT, and END) on INQUIRE REQID commands. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
For
a START command: