Retrieve information about a TRANSACTION definition.
INQUIRE TRANSACTION >>-INQUIRE TRANSACTION(data-value)------------------------------> .------------------------------. V | >----+--------------------------+-+---------------------------->< +-BREXIT(data-area)--------+ +-CMDSEC(cvda)-------------+ +-DTIMEOUT(data-area)------+ +-DUMPING(cvda)------------+ +-FACILITYLIKE(data-area)--+ +-INDOUBT(cvda)------------+ +-INDOUBTMINS(data-area)---+ +-INDOUBTWAIT(cvda)--------+ +-ISOLATEST(cvda)----------+ +-PRIORITY(data-area)------+ +-OTSTIMEOUT(data-area)----+ +-PROFILE(data-area)-------+ +-PROGRAM(data-area)-------+ +-PURGEABILITY(cvda)-------+ +-REMOTENAME(data-area)----+ +-REMOTESYSTEM(data-area)--+ +-RESSEC(cvda)-------------+ +-ROUTING(cvda)------------+ +-ROUTESTATUS(cvda)--------+ +-RTIMEOUT(data-area)------+ +-RUNAWAY(data-area)-------+ +-RUNAWAYTYPE(cvda)--------+ +-SCRNSIZE(cvda)-----------+ +-SHUTDOWN(cvda)-----------+ +-STATUS(cvda)-------------+ +-STORAGECLEAR(cvda)-------+ +-TASKDATAKEY(cvda)--------+ +-TASKDATALOC(cvda)--------+ +-+-TCLASS(data-area)----+-+ | '-TRANCLASS(data-area)-' | +-TRACING(cvda)------------+ +-TRPROF(data-area)--------+ '-TWASIZE(data-area)-------'
Conditions: END, ILLOGIC, INVREQ, NOTAUTH, TRANSIDERR
For more information about the use of CVDAs, see CICS-value data areas (CVDAs).
The INQUIRE TRANSACTION command retrieves information about a particular transaction installed in your CICS system.
Most of the values come from the TRANSACTION resource definition, but a few come from the profile definition to which it points (these are noted in the descriptions). See the CICS® Resource Definition Guide for full details about the attributes of these two types of resources.
Many of the values produced by an INQUIRE TRANSACTION command are the same as those produced by the same-named options in an INQUIRE TASK command, when the task is executing the transaction, because a task acquires most of its characteristics from the definition of the transaction. However, as noted in the description of that command, the values for a task also reflect the CICS system environment.
Furthermore, when a task is routed from one CICS to another, the transaction specified in the sending region may be different from the one executed in the receiving region, so that an inquiry about its TRANSACTION value can produce different results in the sending and receiving regions. Indeed, in the case of dynamic routing, the transaction specified in the sending CICS (and shown as the TRANSACTION value in an INQUIRE TASK there) need not even be defined if the default processing for an undefined transaction code is dynamic routing.
You can also browse through all of the TRANSACTION definitions in your system by using the browse options (START, AT, NEXT, and END) on INQUIRE TRANSACTION commands. In browse mode, the definitions are returned in alphabetic order, and you can specify a starting point with the AT option if you wish. See Browsing resource definitions for general information about browsing, including syntax, exception conditions, and examples.
If BREXIT is not defined, blanks are returned.
This DATAvalue applies only to abend dumps and has no effect on DUMP TRANSACTION commands.
If FACILITYLIKEis not defined, blanks are returned.
The action depends on the values returned in INDOUBTWAIT and INDOUBTMINS; if INDOUBTWAIT returns WAIT, the action is not normally taken until the time returned in INDOUBTMINS expires. (For exceptions to this rule, see INDOUBTWAIT.)
CVDA values are:
For further information about the meaning of the ACTION and WAIT attributes of the TRANSACTION definition, see the CICS Resource Definition Guide.
Isolation limits the access, for both read and write, of user-key programs to task storage. A program executing in user key on behalf of an isolated task can access the task storage of only that task, and this storage cannot be accessed by programs executing in user key on behalf of other tasks. Isolation does not affect access by CICS-key programs and does not apply to storage with the SHARED attribute or any other non-task storage.
Isolation must be turned on for the system as well as the transaction in order for a task to run isolated. (See the TRANISOLATE option of the INQUIRE SYSTEM command.) CVDA values are:
The PURGEABILITY value is set initially by the SPURGE option in the definition of the TRANSACTION this task is executing.
If the remote transaction is defined as DYNAMIC=YES, and remotesystem is omitted, CICS returns the name of the local region.
Blanks are returned if the transaction is not remote.
For details of the enhanced and "traditional" methods of routing transactions invoked by EXEC CICS START commands, see the CICS Intercommunication Guide.
CVDA values are:
The TCLASS option is retained for compatibility with earlier releases of CICS, where transaction classes were numbered from 1 to 10. In this release, transaction classes have 8-character names, specified by the TRANCLASS value in the definition (see that option in this command).
A class is numbered only if its name is of the form DFHTCLnn, where nn is a number from 00 to 10, and it is this number that is returned by the TCLASS option in this command. (The TRANSACTION definition can contain a TCLASS value as well, to allow the same definition to be installed in a system running under an earlier release, but the TCLASS value is ignored in this release and does not need to correspond to the TRANCLASS value.)
If this value is other than SPRSTRACE and the task has a principal facility, the tracing value for the task is determined from a combination of the TRACING values for its terminal and the transaction it is executing. In this case, tracing is special if either the terminal or the transaction specifies SPECTRACE, standard if both specify STANTRACE.
A TRACING value of STANTRACE is assigned when the transaction is defined. You can specify other values only with a SET TERMINAL command or the CICS-supplied CETR transaction.