Retrieve information about a user task.
INQUIRE TASK .-----------------. V | >>-INQUIRE TASK(data-value)----+-------------+-+--------------->< '-| options |-'
Conditions: INVREQ, NOTAUTH, TASKIDERR
This command is threadsafe.
options: .---------------------------------. V | |----+-----------------------------+-+--------------------------| +-ACTIVITY(data-area)---------+ +-ACTIVITYID(data-area)-------+ +-ATTACHTIME(data-area)-------+ +-BRFACILITY(data-area)-------+ +-BRIDGE(data-area)-----------+ +-CMDSEC(cvda)----------------+ +-CURRENTPROG(data-area)------+ +-DB2PLAN(data-area)----------+ +-DTIMEOUT(data-area)---------+ +-DUMPING(cvda)---------------+ +-FACILITY(data-area)---------+ +-FACILITYTYPE(cvda)----------+ +-IDENTIFIER(data-area)-------+ +-INDOUBT(cvda)---------------+ +-INDOUBTMINS(data-area)------+ +-INDOUBTWAIT(cvda)-----------+ +-ISOLATEST(cvda)-------------+ +-PRIORITY(data-area)---------+ +-PROCESS(data-area)----------+ +-PROCESSTYPE(data-area)------+ +-PROFILE(data-area)----------+ +-PROGRAM(data-area)----------+ +-PURGEABILITY(cvda)----------+ +-REMOTENAME(data-area)-------+ +-REMOTESYSTEM(data-area)-----+ +-RESSEC(cvda)----------------+ +-ROUTING(cvda)---------------+ +-RTIMEOUT(data-area)---------+ +-RUNAWAY(data-area)----------+ +-RUNSTATUS(cvda)-------------+ +-SCRNSIZE(cvda)--------------+ +-STARTCODE(data-area)--------+ +-STORAGECLEAR(cvda)----------+ +-SUSPENDTIME(data-area)------+ +-SUSPENDTYPE(data-area)------+ +-+-SUSPENDVALUE(data-area)-+-+ | '-RESNAME(data-area)------' | +-TASKDATAKEY(cvda)-----------+ +-TASKDATALOC(cvda)-----------+ +-TCB(cvda)-------------------+ +-+-TRANCLASS(data-area)-+----+ | '-TCLASS(data-area)----' | +-TRACING(cvda)---------------+ +-TRANPRIORITY(data-area)-----+ +-TRANSACTION(data-area)------+ +-TRPROF(data-area)-----------+ +-TWASIZE(data-area)----------+ +-UOW(data-area)--------------+ '-USERID(data-area)-----------'
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE TASK command returns information about a specific user task. User tasks are those associated with user-defined transactions or with CICS-supplied transactions that are normally invoked by an operator.
Many of the options available on this command are the same as those available on the INQUIRE TRANSACTION command, because a task obtains most of its characteristics from the definition of the transaction it is executing. However, these properties are determined at task initiation.
If the transaction definition is changed after the task begins, the task may have a different value for a property than the current transaction definition. Task values can also be changed with a SET TASK command or its CEMT equivalent.
In addition, the INQUIRE TASK command always produces information about the task you specify on the local CICS system. You need to keep this in mind for tasks that are subject to routing or that issue LINK commands that may be shipped to another system.
Whenever a task is executed wholly or in part on a system other than the one on which it originates, there is a matching task on the remote system. The task on the originating system takes its characteristics from the definition on that system of the transaction it is to execute. The corresponding task on the remote system (if routing takes place or the task issues distributed program links) takes its characteristics from the definition of whatever transaction on the remote system that the originating system tells the remote system to use. This remote transaction may have different properties from those of the transaction on the originating system. (It may or may not have a different name; in the case of static transaction routing, the name of the transaction in the remote system comes from the REMOTENAME option of the transaction in the local system.)
Consequently, an inquiry about the task on the originating system may produce entirely different results from an inquiry about the corresponding task on the remote system. For the same reason, a task that issues distributed program links may get a different result from an INQUIRE TASK about itself (taking the task number from the EIB) in a program executing remotely than from the same command in a program executing locally.
When a task being checked issues a system programming command, CICS calls the external security manager (ESM) to verify that the user associated with the task has authority to use these commands.
A task is command-checked only when an ESM is active and either the CMDSEC value for the task is CMDSECYES or the system initialization option CMDSEC value is ALWAYS (see the SECURITYMGR option of the INQUIRE SYSTEM command in topic INQUIRE SYSTEM options, SDTRAN and the CICS Resource Definition Guide for more information).
The action is dependent on the values returned in INDOUBTWAIT and INDOUBTMINS; if INDOUBTWAIT returns WAIT, the action is not taken until the time returned in INDOUBTMINS expires.
CVDA values are:
See also INDOUBT and INDOUBTWAIT.
For further information about the meaning of the ACTION and WAIT attributes of the TRANSACTION definition, see the CICS Resource Definition Guide.
The value of ISOLATEST is taken from the definition of the TRANSACTION the task is executing when the task is created. For a task defined as isolated to execute isolated, transaction isolation for the system must also be active (see the TRANISOLATE option of the INQUIRE SYSTEM command on page TRANISOLATE). CVDA values are:
The PURGEABILITY value is set initially by the SPURGE option in the definition of the transaction this task is executing.
CICS returns blanks if the transaction definition does not specify REMOTENAME.
CICS returns blanks if the TRANSACTION definition does not specify REMOTESYSTEM.
When a task is being checked, CICS verifies on each command that the user associated with the task has authority to access the resource named in the way requested.
A task is checked only when an external security manager is active and either the RESSEC value for the task is RESSECYES or the system initialization option RESSEC value is ALWAYS (see the SECURITYMGR option of the INQUIRE SYSTEM command in topic INQUIRE SYSTEM options, SDTRAN and the CICS Resource Definition Guide for more information).
The SCRNSIZE value is set by the same-named option in the PROFILE definition associated with the transaction this task is executing.
For information on the values that can appear in the SUSPENDTYPE and SUSPENDVALUE options, and how they can be used as an aid in problem determination, see the "resource type" and "resource name" details in the CICS Problem Determination Guide.
See the description of the TASKDATAKEY option in a TRANSACTION resource definition in the CICS Resource Definition Guide for more information.
CVDA values are:
The value returned for TASKDATAKEY is taken from the definition of the TRANSACTION that the task is executing. To determine whether storage protection is active (that is, whether user-key has a different value from CICS-key), you need to issue an INQUIRE SYSTEM command with the STOREPROTECT option.
For further information on the types of tracing, see the CICS Problem Determination Guide and the description of the CETR transaction in the CICS Supplied Transactions.