Menu principal                 [Fechar]


CICS Manual do Usuário - INQUIRE TRANSACTION


Volta a página anterior

Volta ao Menu Principal


Desenvolvido por DORNELLES Carlos Alberto - Analista de Sistemas - Brasília DF. - cad_cobol@hotmail.com

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:

    CMDSEC(cvda)
  • Returns a CVDA value that indicates whether command security checking is to be performed for tasks that are executing this transaction.
  • The CVDA values are:
    • CMDSECNO
      • Command security checking is to be performed.
      • TXSeries for Multiplatforms always returns this value.
    • CMDSECYES
      • Command security checking is not to be performed.
    DTB(cvda)
  • Returns a CVDA value that indicates how uncommitted changes that are made to recoverable resources by a task that is executing this transaction are to be handled if the task fails.
  • The CVDA values are:
    • BACKOUT
      • Uncommitted changes are to be backed out. TXSeries for Multiplatforms always returns this value.
    • COMMIT
      • Uncommitted changes are to be committed.
    • WAIT
      • The disposition of uncommitted changes is to be deferred until further information is available.
    DTIMEOUT(data-area)
  • Returns a 32-bit binary field that gives the deadlock timeout value (in seconds) for a task that is executing this transaction.
    DUMPING(cvda)
  • Returns a CVDA value that indicates whether CICS is to take a transaction dump if a task that is executing this transaction terminates abnormally.
  • The CVDA values are:
    • NOTRANDUMP
      • No dump is to be taken.
    • TRANDUMP
      • A dump is to be taken.
  • This value applies only to abend dumps and has no effect on DUMP TRANSACTION commands.
    ISOLATEST(cvda)
  • Returns a CVDA value that indicates whether a task that is executing this transaction is to be run in isolation when isolation is active in the system.
  • The CVDA values are:
    • ISOLATE
      • Tasks are to be run in isolation. TXSeries for Multiplatforms always returns this value.
    • NOISOLATE
      • Tasks are not to be run in isolation.
    PRIORITY(data-area)
  • Returns a 32-bit binary field that gives the priority of this transaction relative to other transactions that are in the CICS system, in the range 1 through 255.
    PROFILE(data-area)
  • Returns the eight-character name of the profile definition for this transaction.
  • TXSeries for Multiplatforms always returns a null for this value.
    PROGRAM(data-area)
  • Returns the eight-character name of the first program that is invoked by a task that is executing this transaction.
    PURGEABILITY(cvda)
  • Returns a CVDA value that indicates whether CICS is allowed to purge this task; that is, to terminate it abnormally.
  • Purge requests come from SET TASK PURGE commands (or CEMT equivalents).
  • The CVDA values are:
    • NOTPURGEABLE
      • The task cannot be purged.
    • PURGEABLE
      • The task can be purged.
  • The PURGEABILITY value is set initially by the Purgeability option in the transaction definition.
    REMOTENAME(data-area)
  • Returns the four-character name by which this transaction is known in the remote system, if it is defined as a remote transaction.
  • A null value is returned if the transaction is not remote.
    REMOTESYSTEM(data-area)
  • Returns the four-character name of the remote system on which this transaction is defined, if it is defined as a remote transaction.
  • A null value is returned if the transaction is not remote.
    RESSEC(cvda)
  • Returns a CVDA value that identifies whether resource-level security checking is to be performed for a task that is executing this transaction.
  • The CVDA values are:
    • RESSECNO
      • Resource-level checking is not to be performed.
    • RESSECYES
      • Resource-level checking is to be performed.
    ROUTING(cvda)
  • Returns a CVDA value that indicates whether a task that is executing this transaction is subject to dynamic routing.
  • The CVDA values are:
    • DYNAMIC
      • The task can be routed dynamically.
    • STATIC
      • The task cannot be routed dynamically.
    RTIMEOUT(data-area)
  • Returns a 32-bit binary field that gives the read timeout value, in seconds, for a task that is executing this transaction.
  • TXSeries for Multiplatforms always returns a zero for this value.
    RUNAWAY(data-area)
  • Returns a 32-bit binary field that gives the "runaway task" time, in milliseconds, for tasks that are executing this transaction.
    RUNAWAYTYPE(cvda)
  • Returns a CVDA value that indicates the source of the RUNAWAY option value for this transaction.
  • The CVDA values are:
    • SYSTEM
      • The value is the current default for the system.
    • USER
      • The value was defined explicitly in the transaction definition.
    SCRNSIZE(cvda)
  • Returns a CVDA value that indicates whether a task that is executing this transaction is to use the alternate or the default screen size.
  • This value is specified in the transaction definition.
  • The CVDA values are:
    • ALTERNATE
      • The alternate screen size is to be used.
    • DEFAULT
      • The default screen size is to be used. TXSeries for Multiplatforms always returns this value.
    SHUTDOWN(cvda)
  • Returns a CVDA value that indicates whether this transaction can be executed during CICS shutdown by a task that is created to process unsolicited input.
  • The CVDA values are:
    • SHUTDISABLED
      • The transaction cannot be executed.
    • SHUTENABLED
      • The transaction can be executed.
    STATUS(cvda)
  • Returns a CVDA value that indicates whether the transaction is available for use.
  • The CVDA values are:
    • DISABLED
      • The transaction is not available for use.
    • ENABLED
      • The transaction is available for use.
    STORAGECLEAR(cvda)
  • Returns a CVDA value that indicates whether CICS is to clear storage that is released from a task that is executing this transaction (to prevent other tasks from accidentally viewing confidential data).
  • The CVDA values are:
    • CLEAR
      • Storage is to be cleared.
    • NOCLEAR
      • Storage is not to be cleared. TXSeries for Multiplatforms always returns this value.
    TASKDATAKEY(cvda)
  • Returns a CVDA value that indicates the key of the storage that CICS assigns to a task that is executing this transaction.
  • This storage includes task-lifetime storage, which is the transaction work area (TWA) and the EXEC interface block (EIB), and the storage that CICS obtains on behalf of programs that run under the task.
  • The CVDA values are:
    • CICSDATAKEY
      • CICS-key storage is assigned. TXSeries for Multiplatforms always returns this value.
    • USERDATAKEY
      • User-key storage is assigned.
    TASKDATALOC(cvda)
  • Returns a CVDA value that indicates whether task-lifetime storage for a task that is executing this transaction is to be above or below the 16 MB line.
  • Task-lifetime storage includes the EIB and TWA.
  • The CVDA values are:
    • ANY
      • Task-lifetime storage can be above or below the 16 MB line.
      • TXSeries for Multiplatforms always returns this value.
    • BELOW
      • Task-lifetime storage must be below the 16 MB line.
    TCLASS(data-area)
  • Returns a 32-bit binary field that gives the number of the transaction class to which the transaction belongs, if the task belongs to a numbered class.
  • Zero is returned if the transaction does not belong to any class.
    TRACING(cvda)
  • Returns a CVDA value that indicates the type of tracing that is to be done for tasks that are executing this transaction.
  • The CVDA values are:
    • SPECTRACE
      • Tracing is to be special.
    • SPRSTRACE
      • Tracing is suppressed.
    • STANTRACE
      • Tracing is to be standard.
  • TXSeries for Multiplatforms always returns this value.
    TRANCLASS(data-area)
  • Returns the eight-character name of the transaction class to which this transaction belongs.
  • If the transaction does not belong to any class, the value DFHTCL00 is returned.
  • If the transaction belongs to a numbered class, the value returned is DFHTCLnn, where nn is the two-digit class number (01 through 10).
    TRANSACTION(data-value)
  • Specifies the four-character name of the transaction definition about which you are inquiring.
    TRPROF(data-area)
  • Returns the eight-character name of the profile definition that is used to define attributes that are associated with the session that is used for routing, if transaction routing occurs.
  • TXSeries for Multiplatforms always returns a null for this value.
    TWASIZE(data-area)
  • Returns a 32-bit binary field that gives the size, in bytes, of the transaction work area (TWA) for this transaction.

Condições:

    END
  • RESP2 values:
    • No more resource definitions of this type (RESP2=2) exist.
    ILLOGIC
  • RESP2 values:
    • You have issued a START command when a browse of this resource type is already in progress, or you have issued a NEXT or an END command when a browse of this resource type is not in progress (RESP2=1).
    TRANSIDERR
  • RESP2 values:
    • The transaction was not found (RESP2=1).

© Copyright IBM Corp.