Transaction definitions - TRANDEF
The Transaction definition (TRANDEF) views display information about how transactions are to run in CICS systems.
Supplied views
To access from the main menu, click:
| View | Notes |
|---|---|
| Transaction definitions EYUSTARTTRANDEF.ADDTOGRP |
Add one or more transaction definitions to a resource group. |
| Transaction definitions EYUSTARTTRANDEF.CREATE |
Create a transaction definition and add it to the data repository. |
| Transaction definitions EYUSTARTTRANDEF.DETAILED |
Detailed information about a selected transaction definition. |
| Transaction definitions EYUSTARTTRANDEF.INSTALL |
Install a transaction definition in an active system. |
| Transaction definitions EYUSTARTTRANDEF.REMOVE |
Remove a transaction definition from the data repository. |
| Transaction definitions EYUSTARTTRANDEF.TABULAR |
Tabular information about all transaction definitions for the current context. |
Actions
| Action | Description |
|---|---|
| ADDTOGRP | Add one or more transaction definitions to a resource group. |
| CREATE | Create a transaction definition and add it to the data repository. |
| CSDCOPY | Copy a CICS CSD resource definition. |
| CSDINSTALL | Install a CICS CSD resource definition into an active system. |
| INSTALL | Install a transaction definition in an active system. |
| REMOVE | Remove a transaction definition from the data repository. |
| UPDATE | Update a transaction definition in the data repository. |
Fields
| Field | Attribute name | Description |
|---|---|---|
| Alias name for transaction | ALIAS | An alias transaction name for this transaction. The name may be up to four characters in length. |
| Bridge exit name | BREXIT | The 8-character name that defines the default bridge exit to be associated with this transaction, if it is started in the 3270 bridge environment with a START BREXIT command and BREXIT specifies no name. The presence of a value identifies the transaction as a bridge transaction. This should not be specified for a user transaction. If you specify a value, you must not also specify a value for Remotename or Remotesystem. You also must not specify Dynamic(YES) or Restart(YES). |
| Last modification agent | CHANGEAGENT | The change agent identifier that made the last modification.
|
| Last modification agent release | CHANGEAGREL | The CICS release level of the agent that made the last modification. |
| Last modification time | CHANGETIME | The local date and time when the definition was last changed. |
| Last modification user ID | CHANGEUSRID | The user ID that made the last modification. |
| Command level security option | CMDSEC | Indicates whether command security checking should be performed for tasks executing this transaction:
|
| Suppress user data in trace entries | CONFDATA | Specifies whether CICS is to suppress user data from CICS trace entries when the CONFDATA system initialization parameter specifies HIDETC. |
| Time created | CREATETIME | When browsing or updating a transaction definition, indicates the date and time at which the definition was created and last updated (using the time zone of the maintenance point CMAS). |
| CSD group | CSDGROUP | The name of the CSD group for this CICS resource definition. This field is ignored for BAS definitions. |
| Version | DEFVER | The version number of the BAS resource definition, from 1 to 15. This field is ignored for CICS CSD resource definitions. |
| Description code page | DESCCODEPAGE | The code page of the description field. This field is ignored for CICS CSD resource definitions. |
| Description | DESCRIPTION | A description of the transaction definition. |
| Deadlock timeout value | DTIMOUT | Specifies whether deadlock time-out is be applied to the task. If the execution of the task gets suspended (for example,
through lack of storage), a purge of the task is initiated if the task stays suspended for longer than the
DTIMOUT value. If the purge leads to a transaction abend, the abend code used depends on which part of CICS
suspended the task. When using CEDF, the user task should, if possible, specify DTIMOUT(NO), or a large value. This is
also now used as the timeout on all RLS file requests if DTIMOUT is non-zero, otherwise the request gets the
SIT FTIMEOUT value. FTIMEOUT applies to transactions that do not have a deadlock timeout interval active. If the DTIMOUT keyword
of the TRANSACTION definition is specified, it is used as the file timeout value for that transaction. Note: When using CEDF, if any DTIMOUT value has been specified for the user task, the DTIMOUT value is ignored while the user task is suspended and a CEDF task is active. Therefore the suspended user task cannot terminate with a deadlock timeout (abend AKCS) while a CEDF task is waiting for a user response. For DTIMOUT to be effective in non-RLS usage, SPURGE must be set to YES. CICS inhibits deadlock time-out at certain points. DTIMOUT is not triggered for terminal I/O waits. Because the relay transaction does not access resources after obtaining a session, it has little need for DTIMOUT except to trap suspended allocate requests. However, for I/O waits on a session, the RTIMOUT attribute can be specified on PROFILE definitions for transaction routing on MRO sessions and mapped APPC connections. It is important that you define some transactions with a DTIMOUT value, because deadlock time-out is the mechanism that CICS uses to deal with short-on-storage (SOS) situations. Valid values are:
|
| Transaction dump option | DUMP | Specifies whether a call is to be made to the dump domain to produce a transaction dump if the transaction terminates abnormally. |
| Dynamic routing option | DYNAMIC | Indicates whether the transaction can be dynamically routed to a remote region, using the CICS dynamic transaction routing facility:
|
| External security manager option | EXTSEC | This attribute is obsolete. |
| CICS failure action | FAILACTION | The failure action that CICS takes on the failure of the transaction. The default value is BACKOUT. |
| In-doubt failure processing action | INDOUBT | This attribute is obsolete. |
| Transaction isolation option | ISOLATE | Specifies whether CICS is to isolate the transaction's user-key task-lifetime storage to provide transaction-to-transaction protection. Isolation means that the user-key task-lifetime storage is protected from both reading and writing by the user-key programs of other transactions-that is, from programs defined with EXECKEY(USER). |
| Queueing on local system | LOCALQ | Specifies whether queuing on the local system is to be performed:
|
| Name | NAME | The name of the transaction definition. |
| Object transaction service (OTS) timeout (HHMMSS) | OTSTIMEOUT | The default period in hours, minutes and seconds that an OTS transaction created in an EJB environment executing under this
CICS transaction, is allowed to execute prior to syncpoint.
|
| Default application partition set | PARTITIONSET | Specifies the name of the partition set that is to be the default application partition set. The name can be
up to eight characters in length. Special values are
|
| Primed storage allocation | PRIMEDSIZE | This attribute is obsolete. |
| Transaction priority | PRIORITY | The priority of a transaction relative to other transactions. When a transaction is running as a CICS task, the priority of a task is the sum of the transaction priority, the terminal priority, and the operator priority. The 'value' must be in the range 0-255, where 255 is the highest priority. |
| Transaction profile | PROFILE | The 8-character name of the profile definition for this transaction. The profile defines attributes that govern the interaction between a task executing the transaction and the terminal or session which is its principal facility. |
| First program name | PROGRAM | The name of the program to which CICS gives control to process this transaction. The name can be up to eight characters in length. If this transaction definition is for use on a remote program link request, the program name you specify in this attribute must be the name of the CICS mirror program, DFHMIRS. |
| Remote transaction name | REMOTENAME | The name of this transaction as it is known in a remote system, if it is to be executed in a remote system or region using intersystem communication. The remote system can be another CICS region or an IMS system. REMOTENAME can be 1 through 4 characters in length if the REMOTESYSTEM attribute specifies another CICS region, or 1 through 8 characters in length if REMOTESYSTEM specifies an IMS system. If you specify a remote name, CICSPlex SM uses that name when assigning the transaction to a related system. If you specify a remote system but not a remote name, the local name (that is, the name of this transaction definition) is used in both the target and related systems. |
| Remote system name | REMOTESYSTEM | (Optional) The name of the connection that links the target system to the related system where the transaction resides. If
this parameter is not supplied, the connection name is derived directly from the CICS system ID of the related system.
The name may be up to 4 characters in length. CICSPlex SM uses this system ID only if the transaction
is part of a resource group that is directly associated with a resource description (via RESINDSC). If the transaction is
being assigned by a resource assignment (RASGNDEF), CICSPlex SM uses the actual CICS system ID of the related system.
|
| Resource security checking | RESSEC | Indicates whether resource security checking is required for the transaction. |
| Transaction restart facility | RESTART | Specifies whether the transaction restart facility is to be used to restart those tasks that terminate abnormally and are subsequently backed out by the dynamic transaction backout facility. If YES is specified, the task that failed is restarted from the beginning of the initial program. If dynamic transaction backout fails, or if restart is suppressed dynamically, DFHPEP is invoked in the normal way. The transaction restart facility is especially useful in such situations as a program isolation deadlock, where the task can be restarted automatically rather than resubmitted manually. |
| Dynamic routing status | ROUTABLE | Indicates whether, if the transaction is the subject of an eligible START command, it is routed using the enhanced routing
method. Values are:
|
| Resource security value | RSL | This attribute is obsolete. |
| Resource security level check | RSLC | Indicates security checking is required for resources accessed by this transaction. |
| Runaway timeout value | RUNAWAY | The amount of time, in milliseconds, for which any task running under this transaction definition can have control of the
processor before it is assumed to be in a runaway condition (logical loop). When this interval expires, CICS can abnormally
terminate the task.
|
| Operator sign-on required | SECURE | Specifies whether operators have to sign on to access the transaction. |
| Shutdown run status | SHUTDOWN | Indicates whether the transaction can be run during CICS shutdown. This supplements the XLT option on EXEC CICS PERFORM SHUTDOWN.
For a transaction to be attached during shutdown, it must either be defined as SHUTDOWN(ENABLED) or be named in the
XLT specified in the EXEC CICS SHUTDOWN command.
|
| System purgeable option | SPURGE | Specifies whether the transaction is initially system purgeable or not:
|
| Enabled status | STATUS | Indicates whether the transaction is available for use:
|
| Storage clearance status | STORAGECLEAR | Specifies whether task-lifetime storage for this transaction is to be cleared on release. This can be used to prevent other tasks accidentally viewing any confidential or sensitive data that was being stored by this transaction in task lifetime storage. |
| Task data key | TASKDATAKEY | The storage key of the storage CICS allocates at task initialization for the duration of the task (task-lifetime storage), and
which is accessible by the application. These storage areas are the EXEC interface block (EIB) and the transaction work area
(TWA). This also specifies the key of the storage that CICS obtains on behalf of all programs that run under
the transaction:
|
| Task data location | TASKDATALOC | Specifies whether task life-time storage acquired by CICS for the duration of the transaction can be located above the 16MB
line in virtual storage. These areas, which relate to specific CICS tasks, include the EXEC interface block (EIB) and the
transaction work area (TWA):
You must specify BELOW if any of the programs that make up the transaction runs in 24-bit addressing mode (this also applies to task-related user exits running on behalf of the transaction). For transactions that do not satisfy any of these conditions, you can specify ANY to obtain the associated virtual storage constraint relief. |
| Transaction initiation | TASKREQ | Specifies whether a transaction is to be initiated by pressing a PF key, by using a light pen, or by
using a card. Possible values are:
|
| Transaction class number | TCLASS | This is obsolete from CICS/ESA 3.3. Specifies the 8-character transaction class name to which the transaction belongs. If the transaction does not belong to a class, DFHTCL00 is returned. The abbreviation for TCLASS is Tcl. To remove a transaction from its TCLASS, the Tcl field should be set to DFHTCL00. A series of blanks can be inserted, in which case, DFHTCL00 is returned. An added or changed TClass must be defined. |
| APPC partner transaction name | TPNAME | The name of the transaction that can be used by an APPC partner if the 4-character length limitation of the TRANSACTION attribute is too restrictive. This name can be up to 64 characters in length. |
| Purgeable for terminal error option | TPURGE | Specifies (for non-VTAM terminals only) whether the transaction can be purged because of a terminal error:
|
| Trace transaction activity option | TRACE | Specifies whether the activity of this transaction is to be traced. |
| Transaction class name | TRANCLASS | The name of the transaction class to which the transaction belongs. Transactions belonging to a transaction class are subject to scheduling constraints before they are allowed to execute. The reserved TRANCLASS name DFHTCL00 is used to indicate that the transaction does not belong to any transaction class. The name can be up to 8 characters in length. |
| Transaction security value | TRANSEC | This attribute is obsolete. |
| Transaction routing profile | TRPROF | The name of the profile for the session that carries intersystem flows during ISC transaction routing. The name can be up to eight characters in length. |
| Size in bytes of transaction work area (TWA) | TWASIZE | The size (in bytes) of the transaction work area to be acquired for this transaction. Specify a 1-to 5-digit decimal value in the range 0 through 32767. |
| Use alternate screen size | USEALTSCRSIZ | This attribute is obsolete. |
| User data area 1 | USERDATA1 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |
| User data area 2 | USERDATA2 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |
| User data area 3 | USERDATA3 | Optional string of up to 8 characters that allows you to provide additional site-specific data related to the BAS resource definition. This field is ignored for CICS CSD resource definitions. |
| In-doubt wait option | WAIT | Specifies whether an in-doubt unit of work (UOW) is to wait, pending recovery from a failure that occurs after the
UOW has entered the in-doubt state:
|
| In-doubt wait time (days) | WAITTIMEDD | How long in days a transaction is to wait before taking an arbitrary decision about an in-doubt unit of work, based on what is specified in the ACTION attribute. The maximum value is 99. If you leave the 3 wait time fields blank, CICSPlex SM uses the default values for your CICS environment, if there are any. |
| In-doubt wait time (hours) | WAITTIMEHH | How long in hours a transaction is to wait before taking an arbitrary decision about an in-doubt unit of work, based on what is specified in the ACTION attribute. The maximum value is 23. If you leave the 3 wait time fields blank, CICSPlex SM uses the default values for your CICS environment, if there are any. |
| In-doubt wait time (minutes) | WAITTIMEMM | How long in minutes a transaction is to wait before taking an arbitrary decision about an in-doubt unit of work, based on what is specified in the ACTION attribute. The maximum value is 59. If you leave the 3 wait time fields blank, CICSPlex SM uses the default values for your CICS environment, if there are any. |
| Alternate partner transaction name (in hex) | XTPNAME | (Optional) An alternative to TPNAME. Enter a hexadecimal string up to 128 characters in length, representing the name of the transaction that may be used by an APPC partner. All hexadecimal combinations are acceptable except X'40'. |
| Alternate name (in hex) for initiating transaction | XTRANID | (Optional) Another name to be used instead of the TRANSACTION name for initiating transactions. The name may be up to eight hexadecimal digits in length. Because XTRANID is specified in hexadecimal form, you can use a name that contains characters that you cannot specify in the TRANSACTION attribute. |