Required TDQUEUE definitions

Some transient data queues are used by CICS® services, and it is important that the associated TDQUEUE definitions are installed as soon as possible during cold start. You can ensure that this is the case in one of two ways:
  • You can specify DFHLIST as the first list in the GRPLIST system initialization parameter; DFHLIST contains group DFHDCTG, which, in turn, contains the relevant TDQUEUE definitions.
  • If you do not use DFHLIST, you ensure that group DFHDCTG is the first group in the first list in the GRPLIST system initialization parameter.
The transient data queues in group DFHDCTG are:
CADL (needed to log VTAM® resource definitions)
For VTAM resources, this destination keeps a log of each RDO definition installed in the active CICS system. The log records both the installation of entries in the TCT, and the deletion of autoinstalled entries from the TCT. It records definitions installed:
  • By autoinstall
  • Using CEDA INSTALL
  • At system initialization

For details about defining CADL and CSDL, see the CICS System Definition Guide.

CAIL (needed to log autoinstall terminal model definitions)
The autoinstall terminal model manager (AITM) uses this destination to log all autoinstall terminal model entries installed in, and deleted from, the TCT.
CCPI (needed for CPI Communications messages)
The common programming interface for communications (CPI Communications) writes messages to this destination.
CCSE (needed for C language support)
CICS directs the C standard streams to transient data queues. (Queue names are fixed in CICS: thus, the C standard streams cannot be redirected to other queues.) C programs write to the CCSE queue by writing to stderr. You may code this destination as extrapartition, intrapartition, or indirect. If you do not provide a TDQUEUE definition for the CCSE queue, writing to stderr in C programs will fail.
CCSI (optional, for C language support)
The CCSI queue is reserved for stdin, the C standard stream for input data. Although the CCSI queue name is reserved for stdin, any attempt to read from stdin in CICS results in EOF being returned. For this reason, this destination is optional. You may code it as extrapartition, intrapartition, or indirect.
CCSO (needed for C language support)
CCSO is associated with stdout, the C standard stream for output data. You may code this destination as extrapartition, intrapartition, or indirect. If you do not define the CCSO queue, writing to stdout in C programs will fail.
CDBC (needed for DBCTL DFHDB81xx messages)
CDBC is defined as an indirect queue, which points to the CSML extrapartition queue. Only DBCTL DFHDB81xx messages use this data log; other messages use either the terminal or the console.
CDUL (needed for transaction dump messages)
CDUL is the destination for transaction dump messages. If a transaction dump is requested, for example after a transaction abend, a message is written to this destination to show that a dump has been taken or to give a reason why the dump was suppressed.
CESE (needed for run-time output from Language Environment®)
For Language Environment, all run-time output is written to this transient data queue. For further information, see the z/OS Language Environment Programming Guide.
CMIG (needed for migration log)
CMIG is a migration log, which receives messages reporting the use of functions that are no longer supported in CICS (for example, the EXEC CICS ADDRESS CSA command). You can define CMIG as an intrapartition, extrapartition, or indirect destination.
Start of changeCPLI (needed for CICS PL/I support) End of change
CPLI is the destination for SYSPRINT output. The minimum logical record size is 137. If this destination is extrapartition (direct or indirect), it must be V format. See the installation manual for your PL/I compiler for more details.
CRDI (needed to log program resource definitions)
This destination provides a log of installed resource definitions for programs, transactions, maps, and mapsets.
CSCS (needed for the sign-on transaction)
CSCS receives a message giving details of each sign-on and sign-off. It also receives a message about each rejected attempt at sign on and each resource authorization failure. This destination can be of any type.
CSDL (needed to log RDO commands)
The resource definition online (RDO) transactions write to this destination all commands that result in changes to the CICS system definition (CSD) file or active CICS system.

You need CSDL only if you use RDO and want to keep a log of commands.

The maximum length of data records written to CSDL is 128 bytes. If you define CSDL as extrapartition, the associated SDSCI or DD statement should specify V format records with a minimum blocksize of 136 bytes.

CSFL (needed to log file resource definitions)
CSFL is a log of all file resource definitions installed in the active CICS system. Deletions of file resource entries are also logged here.
CSJE and CSJO (needed for redirected output from Java™ programs that execute in a JVM)
CSJE and CSJO receive output from JVMs that has been intercepted by the CICS-supplied sample class com.ibm.cics.samples.SJMergedStream. This sample class can optionally be specified by the USEROUTPUTCLASS option in a JVM profile. CSJE is for stderr output, internal messages, and unresettable event logging, and CSJO is for stdout output. The com.ibm.cics.samples.SJMergedStream class handles both types of output, and directs them to the correct transient data queue. CSJE and CSJO are defined as indirect queues that point to the CSSL queue.

The length of messages issued by the JVM can vary, and the maximum record length for the CSSL queue (133 bytes) might not be sufficient to contain some of the messages you receive. If this happens, the sample output redirection class issues an error message, and the text of the message might be affected. If you find that you are receiving messages longer than 133 bytes from the JVM, you should redefine CSJO and CSJE as separate transient data queues. Make them extrapartition destinations, and increase the record length for the queue. You can allocate the queue to a physical data set or to a system output data set. You might find a system output data set more convenient in this case, because you do not then need to close the queue in order to view the output. If you redefine CSJO and CSJE, ensure that they are installed as soon as possible during a cold start, in the same way as for transient data queues that are defined in group DFHDCTG.

CSKL (needed to log transaction and profile resource definitions)
CSKL is a log of all transaction and profile resource definitions installed in the active CICS system. Deletions are also logged here.
CSML (needed for the sign-off transaction)
CICS sign-off writes data to this destination.
CSMT (needed for terminal error and abend messages)
The terminal abnormal condition program (DFHTACP) and abnormal condition program (DFHACP) write terminal error and ABEND messages, respectively, to this destination. You may code this destination as extrapartition, intrapartition, or indirect.
CSNE (needed for node error messages)
The node abnormal condition program (DFHZNAC) and the node error program (DFHZNEP) write terminal error messages and data to this destination. You can code this destination as extrapartition, intrapartition, or indirect.
CSPL (needed to log program resource definitions)
CSPL is a log of all program resource definitions installed in the active CICS system. Deletions are also logged here.
CSRL (needed to log partner resource definitions)
CSRL is a log of all partner resources installed in the active CICS system. Deletions are also recorded here. For more information about partner resources, see PARTNER definition attributes.
CSSL (needed for recovery utility statistics)
The recovery utility program (DFHRUP) writes statistics to this destination. This destination needs a minimum logical record length of 132 bytes and a minimum blocksize of 136 bytes.
CSTL (needed for terminal I/O error messages)
The terminal abnormal condition program (DFHTACP) writes terminal I/O error messages to this destination. You may code this destination as extrapartition, intrapartition, or indirect.
CSZL (needed for the Front End Programming Interface)
If you have installed the CICS FEPI feature, CSZL is used as the destination for FEPI messages. For information on FEPI transient data destinations, see the CICS Front End Programming Interface User's Guide.
CSZX (needed for the Front End Programming Interface)
If you have installed the CICS FEPI feature, CSZX is intended for use with a triggered transaction. For information on FEPI transient data destinations, see the CICS Front End Programming Interface User's Guide.