SET TRANSACTION

Change a TRANSACTION definition.

SET TRANSACTION

Conditions: INVREQ, NOTAUTH, TRANSIDERR

For more information about the use of CVDAs, see CICS-value data areas (CVDAs).

Start of change This command is threadsafe. End of change

Description

The SET TRANSACTION command allows you to change some attributes of a transaction definition.

You can change only the definitions in the local CICS system with this command. If you change a transaction that executes remotely (that is, one that specifies a REMOTESYSTEM value), your changes are made, but they have no effect on the definition in the remote system to which the local definition points, and therefore no effect on tasks that execute the transaction.

Changing a transaction definition affects only future tasks; to change a task already executing the transaction, use the SET TASK command.

You cannot use the SET TRANSACTION command for TRANSACTION resources that were defined and installed in a CICS® bundle. If you attempt to modify a dynamically generated TRANSACTION resource that was installed by a CICS bundle, an INVREQ response with a RESP2 value of 300 is issued.

You can control the status of dynamically generated TRANSACTION resources by enabling or disabling the BUNDLE resources that installed them.
You can modify the definition of dynamically generated TRANSACTION resources using the resource editor in the CICS Explorer®. To update the definition, replace the old version of the CICS bundle with the new one, following the instructions in Working with bundles in the CICS Explorer product documentation. CICS bundles that were deployed on their own or with a platform can be updated individually. If the CICS bundle was deployed as part of an application or with an application binding, update the whole application.

Options

DUMPING(cvda)

specifies whether CICS should take a transaction dump if a task executing this transaction terminates abnormally. CVDA values are:

NOTRANDUMP: No dump should be taken.
TRANDUMP: A dump should be taken.

This value applies only to abend dumps and has no effect on DUMP TRANSACTION commands.

OTSTIMEOUT(data-area)

returns a fullword data-area containing the default period in seconds an OTS transaction, created in an EJB environment executing under this CICS transaction, is allowed to execute before syncpoint.

PRIORITY(data-value)

specifies, as a fullword binary value, the priority of this transaction relative to other transactions in the CICS system. The value must be in the range 0–255.

PURGEABILITY(cvda)

returns a CVDA value indicating 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), and CICS can generate them internally to reclaim resources to relieve a system stall condition. CVDA values are:

NOTPURGEABLE: The task cannot be purged.
PURGEABLE: The task can be purged.

The PURGEABILITY value is set initially by the SPURGE option in the definition of the transaction this task is executing.

RUNAWAY(data-value)

specifies, as a fullword binary value, the runaway task time, in milliseconds, for tasks executing this transaction. The value must be 0, or in the range 500–2700000. When checking whether a task is in a runaway condition, CICS rounds the value you specify downwards, to a multiple of 500. If a task keeps control of the processor for more than this interval, CICS assumes it is in a loop and abends it. If the value is zero, CICS does not monitor the task for a runaway condition.

Note: If you specify RUNAWAY, you must set RUNAWAYTYPE to USER in the same SET command, even if RUNAWAYTYPE already has a value of USER.

RUNAWAYTYPE(cvda)

specifies where the runaway task time for a task executing this transaction should be obtained. CVDA values are:

SYSTEM: The system default for runaway task time should be used. (An INQUIRE SYSTEM command with the RUNAWAY option tells you what the system value is.)
USER: The RUNAWAY value for this transaction should be used. You must specify a value for RUNAWAY when you specify USER.

SHUTDOWN(cvda)

specifies whether this transaction can be executed during CICS shutdown by a task created to process unsolicited terminal input. (The transaction also can be executed in this situation if it appears in the transaction list table (XLT) for shutdown.) CVDA values are:

SHUTDISABLED: The transaction cannot be executed.
SHUTENABLED: The transaction can be executed.

STATUS(cvda)

specifies whether the transaction is to be available for use. CVDA values are:

DISABLED: The transaction is not available for use.
ENABLED: The transaction is available for use.

Transactions beginning with the letter “C” are CICS-supplied and cannot be disabled.

TCLASS(data-value)

specifies, as a fullword binary value, the transaction class to which the transaction is to belong. SET TRANSACTION TCLASS sets the TRANCLASS value in a TRANSACTION definition.

TCLASS is provided only for compatibility with earlier releases of CICS, where transaction classes were numbered rather than named, and you can use it only to assign a name of the form DFHTCLnn, where nn is the number you specify, in the range 0-10. (It does not change the TCLASS value in the TRANSACTION definition, which CICS maintains for situations in which the same TRANSACTION definition is used for several different releases. See the descriptions of TCLASS and TRANCLASS in the INQUIRE TRANSACTION command for more information.)

TRACING(cvda)

specifies the type of tracing to be done for tasks executing this transaction. See Using traces in problem determination for definitions of tracing types. CVDA values are:

SPECTRACE: Tracing is to be special.
SPRSTRACE: Tracing is to be suppressed.
STANTRACE: Tracing is to be standard.

TRANCLASS(data-value)

specifies the 8-character name of the transaction class to which this transaction is to belong.

TRANSACTION(data-value)

specifies the 4-character name of the transaction definition that you are changing.

Conditions

INVREQ

RESP2 values:

2: PURGEABILITY has an invalid CVDA value.
3: STATUS has an invalid CVDA value.
4: DISABLED has been specified for a CICS-supplied transaction.
5: The TCLASS or TRANCLASS name is not known.
7: TRACING has an invalid CVDA value.
8: DUMPING has an invalid CVDA value.
9: The PRIORITY value is out of range.
10: RUNAWAYTYPE has an invalid CVDA value.
11: SHUTDOWN has an invalid CVDA value.
12: USER has been specified without a RUNAWAY value.
13: RUNAWAY has been specified without a RUNAWAYTYPE value of USER.
14: The RUNAWAY value is out of range.
300: A SET TRANSACTION SPI command was issued against a TRANSACTION resource that was created by a CICS bundle (BUNDLE).

NOTAUTH

RESP2 values:

100: The user associated with the issuing task is not authorized to use this command.
101: The user associated with the issuing task is not authorized to access this particular resource in the way required by this command.

TRANSIDERR

RESP2 values:

1: The transaction cannot be found.