CICS Manual do Usuário - INQUIRE TRANSACTION
Retrieves information about a transaction definition.
Sintaxe:
INQUIRE TRANSACTION >>-INQUIRE TRANSACTION(data-value)------------------------------> .------------------------------. V | >----+--------------------------+-+---------------------------->< +-CMDSEC(cvda)-------------+ +-DTIMEOUT(data-area)------+ +-DTB(cvda)----------------+ +-DUMPING(cvda)------------+ +-ISOLATEST(cvda)----------+ +-PRIORITY(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)-------+ +-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)-------'
Condições: END, ILLOGIC, TRANSIDERR
For more information about the use of CICS-value data areas (CVDAs), see Appendix F, CVDAs recognized by the translator.
Descrição:
The INQUIRE TRANSACTION command retrieves information about a particular transaction that is installed in your CICS system.
When the task is executing the transaction, many of the values that are produced by an INQUIRE TRANSACTION command are the same as those that are produced by the same-named options in an INQUIRE TASK command because a task acquires most of its characteristics from the definition of thetransaction. However, as noted in the description of the INQUIRE TASK command, the values for a task also reflect the CICS system environment.
Furthermore, when a task is routed from one CICS region to another, the transaction that is specified in the sending region possibly can be different from the one that is executed in the receiving region. As a result, an inquiry about the value of a TRANSACTION option can produce different results in the sending and receiving regions. If the default processing for an undefined transaction code is dynamic routing, the transaction that is specified in the sending CICS (and shown as the TRANSACTION value in an INQUIRE TASK command that is issued there) does not need to be defined.
Comentários:
You can also browse through all 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 sequence, and you can specify a starting point with the AT option if you want. See Using the CICS API commands for general information about browsing, syntax, exception conditions, and examples.
Opções:
Condições: