- ACTION({BACKOUT|COMMIT})
- specifies
the action to be taken when a CICS® region fails, or loses connectivity
with its coordinator, during two-phase commit processing after the
unit of work has entered the in-doubt period. The action depends on
the WAIT attribute. If WAIT specifies YES, ACTION has no effect unless
the WAITTIME expires before recovery from the failure.
If WAIT
specifies NO, the action taken is one of the following:
- BACKOUT
- All changes made to recoverable resources are backed out, and
the resources are returned to the state they were in before the start
of the UOW.
- COMMIT
- All changes made to recoverable resources are committed, and the
UOW is marked as completed.
- ALIAS(alias)
- allows you to specify an alias transaction name for this transaction.
The name may be up to four characters in length. This
useful if you wish to run on a terminal defined with UCTRAN(NO), or
a transaction that allows mixed case input (PROFILE UCTRAN(NO)). For
example, you can invoke via alias(abcd) the same transaction
as ABCD.
When you install a TRANSACTION definition which
contains the ALIAS attribute, the result depends upon whenter the
alias name is already in use in the system:
- If the alias name is in use as a primary transaction ID, the ALIAS
attribute is ignored.
- If the alias name is in use as the alias for a different transaction,
the original alias is replaced by the new one. In other words, after
the TRANSACTION definition has been installed, the alias name refers
to the new transaction, and not the original.
- BREXIT(program)
- This
is an optional attribute that defines the name of the default bridge
exit to be associated with this transaction, if it is started in the
3270 bridge environment with a START BREXIT command
that does not specify a name on its BREXIT option. The name may be
up to eight characters in length.
Acceptable characters:A-Z 0-9 $ @ #
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
If BREXIT is defined, REMOTESYSTEM, REMOTENAME,
DYNAMIC(YES), and RESTART(YES) should not be specified, and will be
ignored.
Note: The Link3270 mechanism is now the recommended
way to use the 3270 bridge. Use of the START BREXIT interface is not
described in CICS documentation for CICS TS Version 2, and you should
refer to the publications for CICS Transaction Server for OS/390,
Version 1 Release 3 if you need to implement new applications using
this interface.
- CMDSEC({NO|YES})
- specifies
whether security checking is to be applied on system programming commands.
For programming information on the system programming commands, see the CICS System
Programming Reference.
- NO
- No check is made. The commands are always executed.
- YES
- A call is made to the external security manager (ESM). CICS either
authorizes or prevents access. If the ESM cannot identify the resource
or resource type, access is prevented.
- CONFDATA({NO|YES})
- specifies
whether CICS is to suppress user data from CICS trace entries when
the CONFDATA system initialization parameter specifies HIDETC. If
the system initialization parameter specifies CONFDATA=SHOW, CONFDATA
on the transaction definition is ignored.
If the system initialization
parameter specifies CONFDATA=HIDETC, the following options are effective:
- NO
- CICS does not suppress any user data. VTAM® and
MRO initial user data is traced in trace point AP FC92. FEPI user
data is traced in the normal CICS FEPI trace points.
- YES
- CICS suppresses user data from the CICS trace points.
- DESCRIPTION(text)
- You can provide a description of the resource you are defining in this
field. The description text can be up to 58 characters in length. There are
no restrictions on the characters that you can use. However,
if you use parentheses, ensure that for each left parenthesis there is a matching
right one. If you use the CREATE command, for each single apostrophe in the
text, code two apostrophes.
- DTIMOUT({NO|mmss})
- 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.
- NO
- The deadlock time-out feature is not required.
- mmss
- The length of time (MMSS for minutes and seconds) after which
the deadlock time-out facility terminates a suspended task. The maximum
value that you can specify is 68 minutes; this is accurate to one
second.
- DUMP({YES|NO})
- specifies whether a call is to be made to the dump domain to produce
a transaction dump if the transaction terminates abnormally.
- YES
- CICS calls the dump domain to produce a transaction dump. Note
that the final production or suppression of the transaction dump is
controlled by the transaction dump table. For more information about
the dump table, see the CICS Problem
Determination Guide.
If no transaction dump table entry
exists for the given dump code when a transaction abends, CICS creates
a temporary entry for which the default is to produce a transaction
dump.
You control dump table entries for transaction dumps
using the CEMT transaction (for more information, see the CICS Supplied
Transactions) or the EXEC CICS SET TRANDUMPCODE command
(for programming information, see the CICS System
Programming Reference).
- NO
- No call is made to the dump domain, suppressing any potential
transaction dump.
Note: This operand has no effect on the following:
- An EXEC CICS DUMP command, which always produces a dump.
- The system dumps for dump codes AP0001 and SR0001 that CICS produces
in connection with ASRA, ARSB, or ASRD abends. If you specify NO on
the transaction DUMP attribute, CICS suppresses the transaction dump,
but not the system dump.
- DYNAMIC({NO|YES})
- specifies whether the transaction can be dynamically routed to
a remote region, using the CICS dynamic transaction routing facility.
- NO
- Creates a local or remote definition according to the REMOTESYSTEM
attribute.
- YES
- Allows the dynamic transaction routing program to determine the
local or remote status dynamically at invocation time. For programming
information about the dynamic transaction routing program, see the CICS Customization
Guide.
Note: If the TRANDEF is either named in a resource
assignment or dynamically installed with a Usage value of REMOTE,
the Mode value (DYNAM or STAT) overrides this value in determining
whether the transaction can be dynamically routed.
- EXTSEC
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- GROUP(groupname)
- Every resource definition must have a GROUP name. The resource definition
becomes a member of the group and is installed in the CICS system when the
group is installed.
Acceptable characters:A-Z 0-9 $ @ #
Any
lower case characters you enter are converted to upper case. |
The GROUP name can be up to eight characters in length. Lowercase
characters are treated as uppercase characters. Do not use group names beginning
with DFH, because these characters are reserved for use by CICS.
- INDOUBT
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- ISOLATE({YES|NO})
- specifies
whether CICS is to isolate the transaction's user-key task-lifetime
storage to provide transaction-to-transaction protection. (See the
TASKDATAKEY attribute for a description of user-key storage.) 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). Figure 1 shows the effect of the
ISOLATE attribute.
Note: - The ISOLATE attribute does not provide any protection against
application programs that execute in CICS key—that is, from programs
defined with EXECKEY(CICS).
- VSAM nonshared resources (NSR) are not supported for transactions
that use transaction isolation. You should specify ISOLATE(NO) when
you define transactions that access VSAM files using NSR.
- YES
- The transaction's user-key task-lifetime storage is isolated from
the user-key programs of all other transactions—that is, from programs
defined with EXECKEY(USER), but not from programs defined with EXECKEY(CICS).
Also, the user-key task-lifetime storage of all other transactions
is protected from the user-key programs of transactions defined
with ISOLATE(YES).
- NO
- If you specify ISOLATE(NO), the transaction's task-lifetime storage
is isolated from the user-key programs of those transactions defined
with ISOLATE(YES). The transaction's storage is not, however, isolated
from user-key programs of other transactions that also specify ISOLATE(NO)
because, with this option, the transactions are all allocated to the
common subspace.
Note also that the user-key task-lifetime storage
of all transactions defined with ISOLATE(YES) is protected from the
user-key programs of transactions defined with ISOLATE(NO).
Specify
ISOLATE(NO) for those transactions that share any part of their user-key
task-lifetime storage.
Figure 1. The
effect of the ISOLATE attribute of storage accessThis figure shows four transactions — A, B, C, and D — defined
with the ISOLATE(YES), and three transactions — E, F, and G — defined
with ISOLATE(NO):
- The user-key task-lifetime storage of each of the transactions
A, B, C, and D is isolated from all other transactions.
- The user-key task-lifetime storage of transactions E, F, and G
is accessible by all the user-key application programs of transactions
E, F and G, but is isolated from the user-key programs of transactions
A, B, C, and D.
- All the transactions have read-only access to CICS-key storage.
- LOCALQ({NO|YES})
- specifies
whether queuing on the local system is to be performed.
- NO
- No local queuing is to be performed.
- YES
- Local queuing can be attempted for an EXEC START NOCHECK request
when the system is not available and the system name is valid. A system
is defined as not available when:
- The system is OUT OF SERVICE when the request is initiated.
- The attempt to initiate any session to the remote system fails
and the corrective action taken by the abnormal condition program
(DFHZNAC) or the node error program (DFHZNEP) is to place the system
OUT OF SERVICE.
- No sessions to the remote system are immediately available, and
your XISCONA global user exit program specifies that the request is
not to be queued in the issuing region.
Local queuing should be used only for those EXEC START commands
that represent time independent requests. The delay implied by local
queuing affects the time at which the request is actually started.
It is your responsibility to ensure that this condition is met.
If
you specify LOCALQ(YES), you cannot specify ROUTABLE(YES).
You can use the global user exit XISLCLQ for the
intersystem communication program to override the setting of the LOCALQ
attribute. For programming information on the user exits in the intersystem
communication program, see the CICS Customization
Guide.
- OTSTIMEOUT({NO|hhmmss)
- specifies, in hours, minutes, and seconds, the length of time
for which an Object Transaction Service (OTS) transaction, created
in an enterprise beans environment and executing as a task under this
CICS transaction, is allowed to execute before the initiator of the
OTS transaction must take a syncpoint or roll back the transaction.
If the specified period expires, CICS purges the task.
The initiator
of the OTS transaction may be:
- The client of the enterprise bean.
- The EJB container. (The container issues a syncpoint at the end
of the bean method.)
- A session bean that manages its own OTS transactions.
Methods of session beans that manage their own OTS transactions
can override the default timeout value by using the setTransactionTimeout method
of the javax.Transaction.UserTransaction interface.
- NO
- OTS transactions will not time out. This is the default.
- hhmmss
- The period of time (in HHMMSS format) before the task is purged.
The maximum period is 24 hours (240000).
- PARTITIONSET({partitionset|KEEP|OWN})
- 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.
Acceptable characters:A-Z 0-9 $ @ #
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
If you do not specify a partition set name or either
of the reserved names, CICS destroys existing partitions before the
first BMS output to the terminal from the transaction.
- partitionset
- CICS destroys existing partitions and loads the named partition
set before the first BMS output to the terminal from the transaction.
(Existing partitions are not destroyed if the terminal partition set
matches the application partition set.)
This name must not be
the same as that specified in PROGRAM(name).
- KEEP
- The transaction uses the application partition set for this terminal,
whatever it may be. This option is normally used for successor transactions
in a chain of pseudoconversational transactions.
- OWN
- The transaction performs its own partition management.
- PRIMEDSIZE
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- PRIORITY({1|priority})
- specifies
the transaction priority. This 1-to 3-digit decimal value from 0 to
255 is used in establishing the overall transaction processing priority.
(Transaction processing priority is equal to the sum of the terminal
priority, transaction priority, and operator priority, not exceeding
255.) The higher the number, the higher the priority.
- PROFILE({DFHCICST|profile})
- is
the name of the PROFILE definition that specifies the processing options
used in conjunction with the terminal that initiated the transaction.
Acceptable characters:A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
For information about entering mixed case information,
see Entering mixed case attributes. |
The default is DFHCICST. The processing options
provided by the default DFHCICST are shown in PROFILE definitions in group DFHISC.
DFHCICST is not suitable for use with a distributed program link.
Instead, specify DFHCICSA, which has INBFMH=ALL.
- PROGRAM(program)
- specifies
the name of the program to which CICS gives control to process this
transaction. The name can be up to eight characters in length.
Acceptable characters:A-Z 0-9 $ @ #
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
Ensure that this name is not the same as that specified
in PARTITIONSET(name).
Note: If a name is specified for REMOTESYSTEM,
and it differs from that of the current system, no name need be specified
for PROGRAM. If, in these circumstances, a name is specified for PROGRAM,
it may be ignored.
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.
See the TRANSID attribute on the PROGRAM definition in dfha4_attributes.htm#dfha46x.
- REMOTENAME(transaction)
- specifies
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. IMS uses 8-character
names and, if REMOTENAME has fewer than 8 characters, IMS translates
it into a usable format.
Acceptable characters:A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
For information about entering mixed case information,
see Entering mixed case attributes. |
If you specify REMOTESYSTEM and omit REMOTENAME,
the value of REMOTENAME defaults to the local name; that is, the TRANSACTION
name on this definition. Note that the transaction need not necessarily
reside on the remote system or region.
- REMOTESYSTEM(connection)
- specifies
the name of the CONNECTION definition of the intercommunication link
on which the transaction attach request is sent.
Acceptable characters:A-Z 0-9 $ @ #
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
This attribute is used for CICS function request
shipping (asynchronous processing and transaction routing).
- RESSEC({NO|YES})
- specifies whether resource security checking is to be used for
resources accessed by this transaction.
- NO
- All resources are available to any user who has the authority
to use this transaction.
- YES
- An external security manager is used. For more details about external
security checking, see the CICS RACF® Security
Guide.
- RESTART({NO|YES})
- 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 RESTART(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.
A terminal-initiated transaction will be allowed to restart during
CICS shutdown even if the transaction is defined as SHUTDOWN(DISABLED).
For more details of automatic transaction restart, see
the CICS Recovery
and Restart Guide.
- NO
- The restart facility is not required.
- YES
- The restart facility is to be used.

- ROUTABLE({NO|YES})
- specifies
whether, if the transaction is the subject of an eligible EXEC CICS
START command, it will be routed using the enhanced routing method.
- NO
- If the transaction is the subject of a START command, it will
be routed using the “traditional” method.
- YES
- If the transaction is the subject of an eligible START command,
it will be routed using the enhanced method.
If you specify ROUTABLE(YES),
you cannot specify LOCALQ(YES).
For details of the enhanced and “traditional” methods
of routing transactions invoked by EXEC CICS START commands, see the CICS Intercommunication
Guide.
- RSL
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- RUNAWAY({SYSTEM|0|milliseconds})
- 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.
- SYSTEM
- CICS is to use the ICVR system initialization parameter value
as the runaway time limit for this transaction.
- 0
- There is no limit and no runaway task detection is required for
the transaction.
- milliseconds
The runaway time limit in the range 500
through 2700000. CICS rounds the value you specify downwards, to a
multiple of 500.
- SHUTDOWN({DISABLED|ENABLED})
- applies
to all transactions, and specifies whether it can be run during CICS
shutdown. This supplements the XLT option the PERFORM SHUTDOWN command.
For a transaction to be attached during shutdown, it must either be
defined as SHUTDOWN(ENABLED) or, in the case of terminal-based transactions,
be named in the XLT specified in the PERFORM SHUTDOWN command.
- DISABLED
- The transaction is disabled from running during CICS shutdown.
- ENABLED
- The transaction is enabled to run during CICS shutdown.
- SPURGE({NO|YES})
- specifies
whether the transaction is initially “system purgeable” or not.
SPURGE=NO
prevents a transaction being purged by the deadlock time-out (DTIMOUT)
facility, an EXEC CICS ... PURGE command, TWAOCT (Cancel Task) being
set in the node error program (NEP), or a CEMT SET ... PURGE command.
SPURGE=YES
allows such purges to go ahead as far as the user is concerned. CICS
may, however, prevent the purge if it is not safe to allow a purge
at the point the transaction has reached.
Note that SPURGE=NO
does not prevent a transaction being purged by the read time-out (RTIMOUT)
facility, an EXEC CICS SET ... FORCEPURGE command, or a CEMT SET TRANSACTION(tranid)
FORCEPURGE command. SPURGE determines only the initial value, which
can be changed by the transaction while it is running.
- NO
- The transaction is not initially system purgeable.
- YES
- The transaction is initially system purgeable.
- STATUS({ENABLED|DISABLED})
- specifies the transaction status.
- ENABLED
- Allows the transaction to be executed normally.
- DISABLED
- Prevents the transaction being executed.
- STORAGECLEAR({NO|YES})
- 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.
- TASKDATAKEY({USER|CICS})
- specifies
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).
TASKDATAKEY also
specifies the key of the storage that CICS obtains on behalf of all
programs that run under the transaction. The program-related storage
that CICS allocates in the specified key includes:
- The copies of working storage that CICS obtains for each execution
of an application program.
- The storage CICS obtains for the program in response to implicit
and explicit GETMAIN requests. For example, the program can request
storage by a GETMAIN command, or as a result of the SET option on
other CICS commands.
You must specify TASKDATAKEY(USER) if any of the programs
in the transaction is defined with EXECKEY(USER). If you specify TASKDATAKEY(CICS)
for a transaction, an attempt to run any program in user key under
this transaction leads to a task abend, with abend code AEZD.
- USER
- CICS obtains user-key storage for this transaction. Application
programs executing in any key can both read and modify these storage
areas.
Note: User-key programs of transactions defined with ISOLATE(YES)
have access only to the user-key task-lifetime storage of their own
tasks.
User-key programs of transactions defined with ISOLATE(NO)
also have access to the user-key task-lifetime storage of other tasks
defined with ISOLATE(NO).
See the description of the EXECKEY
attribute on the PROGRAM definition for more information about task
storage protection.
- CICS
- CICS obtains CICS-key storage for this transaction. Application
programs executing in CICS key can both read and modify these storage
areas. Application programs executing in user key can only read these
storage areas.
- TASKDATALOC({BELOW|ANY})
- 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 TASKDATALOC(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.
CICS
polices the use of TASKDATALOC(ANY). In particular:
- An attempt to invoke an AMODE 24 program running under a transaction
defined with TASKDATALOC(ANY) results in an AEZC abend.
- An attempt to issue an EXEC CICS command or call a task related
user exit while running AMODE(24) with TASKDATALOC(ANY) specified
results in an AEZA abend.
- An AMODE 31 program running as a transaction with TASKDATALOC(ANY),
which attempts to invoke a task-related user exit that is forced to
run AMODE(24), results in an AEZB abend.
- If a task-related user exit that is forced to run in AMODE 24
is enabled for task start, CICS forces TASKDATALOC(BELOW) for all
transactions for the remainder of the CICS run.
- BELOW
- Storage areas that CICS acquires for the transaction must be located
below the 16MB line.
- ANY
- Storage areas that CICS acquires for the transaction can be located
above the 16MB line in virtual storage.
- TASKREQ(value)
- 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:
- PA1, PA2, or PA3 for PA keys.
- PF1 through PF24 for PF keys.
- OPID for the operator identification card reader.
- LPA for a light-pen-detectable field on a 3270 device.
- MSRE for the 10/63 character magnetic slot reader.
Here are some notes on the use of PF and PA keys:
- TCLASS
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- TPNAME(name)
- specifies
the name of the transaction that may 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.
Acceptable characters:A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
For information about entering mixed case information,
see Entering mixed case attributes. |
If this range of characters is not sufficient for a
name that you wish to specify, you may use the XTPNAME attribute instead
of TPNAME.
- TPURGE({NO|YES})
- specifies
(for non-VTAM terminals only) whether the transaction can be purged
because of a terminal error.
- NO
- The task cannot be purged when a terminal error occurs. Manual
intervention by the master terminal operator is required when this
happens.
- YES
- The task can be purged when a terminal error occurs.
- TRACE({YES|NO})
- specifies
whether the activity of this transaction is to be traced.
- YES
- Trace the activity for this transaction.
- NO
- Do not trace the activity for this transaction.
Note: The CICS-provided transaction definitions for
CEDF and CSGM specify TRACE(NO).
- TRANCLASS(DFHTCL00|tranclass)
- specifies
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.
Note: If a transaction is run and its associated
TRANCLASS definition is not installed, the transaction runs without
any of the scheduling constraints specified in the TRANCLASS. Message
DFHXM0212 is issued as a warning.
TRANCLASS can be up to
8 characters in length.
Acceptable characters:A-Z 0-9 $ @ #
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
- TRANSACTION(name)
- specifies
the name of the transaction, or transaction identifier (TRANSID).
The name can be up to four characters in length.
Acceptable characters:A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
For information about entering mixed case information,
see Entering mixed case attributes. |
Do not use transaction names beginning with C, because
these are reserved for use by CICS. Note: - If you use a comma (,) in a name, you will be unable to use those
commands such as
CEMT INQUIRE TRANSACTION(value1,value2)
CEMT SET TRANSACTION(value1,value2)
where
the comma serves as a list delimiter. See CICS Supplied
Transactions for information about using lists of resource
identifiers.
- If you protect your transient data queues using RACF,
avoid using % and & in the name.
RACF commands assign a special meaning to these characters when they
are used in a profile name. See the CICS RACF Security
Guide.
If you wish to use other special characters in a
transaction identifier, use the XTRANID attribute to specify another
name that can be used to initiate the transaction. You must also specify
a TRANSACTION name, because this is the name by which the TRANSACTION
definition is known on the CSD file.
When defining a transaction,
you must also name either a PROGRAM or a REMOTESYSTEM.
- TRANSEC
- This attribute is obsolete, but is supported to provide compatibility
with earlier releases of CICS. For more information, see Obsolete attributes.
- TRPROF({DFHCICSS|profile})
- specifies
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.
Acceptable characters:A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
For information about entering mixed case information,
see Entering mixed case attributes. |
You can specify this only for remote transactions.
- TWASIZE({0|number})
- specifies
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.
Note: - Your storage may be corrupted if your TWASIZE is too small.
- Do not change the TWASIZE of the CICS-supplied transactions.
- WAIT({YES|NO})
- 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.
Note: Old-style transaction definitions using INDOUBT(WAIT)
are accepted by CICS, and are interpreted as WAIT(YES) ACTION(BACKOUT).
- YES
- The UOW is to wait, pending recovery from the failure, to resolve
its in-doubt state and determine whether recoverable resources are
to be backed out or committed. In other words, the UOW is to be shunted.
Recoverable resources can include:
- DBCTL databases
- DB2® databases
- Temporary storage queues
- Logically-recoverable intrapartition transient data queues that
specify WAIT(YES) in the TDQUEUE definition
- VSAM data sets
- BDAM data sets.
The WAIT(YES) option takes effect
provided that none
of the following applies:
- The transaction has subordinate MRO sessions to back-level systems.
- The transaction has LU6.1 subordinate sessions. (Note that, in
this context, LU6.1 IMS sessions are not subordinates.)
- The transaction has more than one session and its coordinator
session is to a back-level system, or LU6.1.
- The task-related user exits attached to the transaction do not
support the CICS in-doubt protocols.
If none of the above exceptions applies, but there are
subordinate LU6.2 sessions to non-CICS Transaction Server for z/OS® systems
(for example, CICS/6000®) that do not use the CICS Transaction Server for z/OS in-doubt
architecture, CICS can indicate that the subordinate should wait by
forcing session outage.
If any resources cannot wait for the
coordinator's in-doubt resolution, a decision is taken for the transaction
in accordance with the ACTION attribute. In practice, the only circumstances
that force decisions in this way are updates to transient data queues
with WAIT(NO) specified in the TDQUEUE definition, and installations
of terminal-related resources. The latter are normally installed using
an INSTALL command.
Table 1 shows
how the WAIT attribute defined on a TRANSACTION definition and a logically
recoverable TDQUEUE definition are resolved when there is a conflict.
- NO
- The UOW is not to wait. CICS immediately takes whatever action
is specified on the ACTION attribute.
Table 1. Resolution
of WAIT attributes on TRANSACTION and TDQUEUE definitionsWAIT attribute of TDQUEUE definition |
WAITACTION attribute of TDQUEUE definition |
WAIT attribute of TRANSACTION definition |
Action |
NO |
not applicable |
YES |
The TD WAIT(NO) overrides WAIT(YES) on the TRANSACTION
definition. The UOW is forced to either commit or back out, in accordance
with the transaction's ACTION attributes. |
NO |
not applicable |
NO |
The UOW is forced to either commit or back out,
in accordance with the transaction's ACTION attributes. |
YES |
QUEUE |
YES |
The UOW waits (that is, it is shunted). A request
from another task for a lock on the TD queue must wait, and is queued
by CICS. |
YES |
QUEUE |
NO |
The transaction WAIT(NO) overrides the TDQUEUE
definition. The UOW is forced to either commit or back out, in accordance
with the transaction's ACTION attributes. |
YES |
REJECT |
YES |
The UOW waits (that is, it is shunted). A request
from another task for a lock on the TD queue is rejected with the
LOCKED condition. |
YES |
REJECT |
NO |
The transaction WAIT(NO) overrides the TDQUEUE
definition. The UOW is forced to either commit or back out, in accordance
with the transaction's ACTION attributes. |
Note: If the UOW references more than one transient data
queue, and the queues have inconsistent WAIT options, WAIT(NO) always
takes precedence and overrides a WAIT(YES). Thus a WAIT(NO) on one
TDQUEUE definition forces a failed in-doubt UOW to take either the
BACKOUT or COMMIT attribute defined on the UOW's TRANSACTION definition.
- WAITTIME({00,00,00|dd,hh,mm})
- specifies
how long 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.
- 00,00,00
- The transaction waits indefinitely.
- dd,hh,mm
- The time, in days, hours, and minutes, for which the transaction
is to wait. The maximum value is 93,23,59.
WAITTIME takes effect only if WAIT(YES) is specified.
- XTPNAME(value)
- This
attribute may be used as 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'. To specify an XTPNAME
more than 72 characters long to DFHCSDUP, put an asterisk in column
72. This causes the following line to be concatenated to the current
line.
- XTRANID(xtranid)
- You
can use this optional attribute to specify 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.
(See also
TASKREQ, another transaction alias that can be specified.)
- value
- A 4-byte transaction identifier in hexadecimal notation (the identifier
therefore uses up to eight hexadecimal digits). If you specify fewer
than eight hexadecimal digits, the identifier is padded on the right
with blanks.
Certain values are reserved for use by CICS, and so
there are restrictions on the values you can specify:
- The first byte must not be X'C3'.
- The first byte must not be less than or equal to X'40'.
- The value must not be X'00000000'.
- The last three bytes must not be X'FFFFFF'.
Avoid using values in the range
X'00' through
X'3F' in
the second, third and fouth bytes if the transaction is to be attached
by unsolicited data received from a terminal defined as a 3270 device,
because CICS will interpret these values as control characters, and
not as part of the transaction identifier. For example, if you issue
EXEC CICS RETURN or EXEC CICS START and specify TRANSID(X'41303238'),
then the correct transaction will be attached. However, if you issue
EXEC CICS RETURN without specifying a TRANSID, and the 3270 device
transmits data that begins with
X'41303238', CICS will attempt
to attach a transaction as if
X'41404040' had been transmitted.