Required TDQUEUE definitions
CICS® services use certain transient data queues, and the associated TDQUEUE definitions must be installed as soon as possible during a cold start.
To ensure that the required TDQUEUE definitions are installed
as soon as possible, specify the GRPLIST system
initialization parameter in one of the following ways:
- Specify DFHLIST as the first list in GRPLIST. The DFHLIST list contains the group DFHDCTG, which contains the relevant TDQUEUE definitions.
- Specify that group DFHDCTG is the first group in the first list in GRPLIST.
The transient data queues in group DFHDCTG are as follows:
- CADL (needed to log z/OS® Communications Server resource definitions)
- For z/OS Communications Server 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 data sets for transient data queues, see Defining data sets.
- CADO (needed for CICS Development Deployment Tool messages)
- CADO is the transient data queue that logs the messages from the CICS Development Deployment Tool.
- CADS (needed for messages produced by auditing system programming interface commands)
- CADS is the transient data queue that logs the messages produced when auditing the system programming interface commands.
- 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 can 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 fails.
- 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 can 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 can code this destination as extrapartition, intrapartition, or indirect. If you do not define the CCSO queue, writing to stdout in C programs fails.
- CCZM (needed for CICS class messages)
- CCZM is the transient data queue that logs the messages from the CICS foundation classes.
- 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.
- CDB2 (needed if DB2® is used)
- CDB2 is the transient data queue for messages and statistics from the CICS DB2 attachment facility.
- CDEP (needed for deprecation messages)
- CDEP is the transient data queue for deprecation messages.
- 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.
- CECO (needed for event capture and emission messages)
- CECO is the transient data queue for messages from the event capture and emission (EC) component.
- CEJL (needed for Enterprise Java™ messages)
- CEJL is the transient data queue for messages from the Enterprise Java domain.
- CEPO (needed for event processing messages)
- CEPO is the transient data queue for messages from the event processing (EP) domain.
- CESE (needed for runtime output from Language Environment®)
- For Language Environment, all runtime output is written to this transient data queue. For further information, see the z/OS Language Environment Programming Guide.
- CESO (needed for runtime output from Language Environment)
- For Language Environment, all runtime output is written to this transient data queue. For further information, see the z/OS Language Environment Programming Guide.
- CIEO (needed for IP ECI messages)
- CIEO is the transient data queue for Internet Protocol (IP) external call interface (ECI) messages from the IP ECI (IE) domain.
- CISL (needed to log IPCONN resource definitions)
- This destination provides a log of installed IPCONN resource definitions. During early CICS initialization, if CISL is not yet available messages intended for this destination can be routed to the console.
- CISO (needed for IPIC messages)
- CISO is the transient data queue for IP interconnectivity (IPIC) connection messages from the inter-system (IS) domain.
- CJRM (needed for JRas logging and tracing facility messages)
- CJRM is the transient data queue for messages from the JRas logging and tracing facility. These are messages that are issued by a Java class running in a CICS JVM that are not CICS messages.
- CKQQ (needed for CICS-MQ Connection messages)
- CKQQ is the transient data queue that logs the CICS-MQ messages that are issued during CICS-MQ adapter startup and shutdown. It is defined as an intrapartion queue.
- 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.
- CMLO (needed for markup language messages)
- CMLO is the transient data queue for messages from the markup language domain.
- CMPO (needed for managed platform messages)
- CMPO is the transient data queue for messages from the managed platform domain.
- CMQM (needed for CICS-MQ messages)
- CMQM is the queue that logs all CICS-MQ messages that are issued by the CICS-MQ adapter, CICS -MQ trigger monitor,and CICS-MQ bridge.
- CPIO (needed for CICS SOAP messages)
- CPIO is the transient data queue that logs the CICS SOAP messages.
- CRDI (needed to log program resource definitions)
- This destination provides a log of installed resource definitions, such as programs, transactions, maps, and mapsets.
- CRLO (needed for resource lifecycle messages)
- CRLO is the transient data queue for messages from the resource lifecycle manager.
- CRPO (needed for Open Network Computing Remote Procedure Call (ONC RPC) messages)
- CRPO is defined as an extrapartition queue, but you can make the destination intrapartition or indirect.
- CSBA (needed if using the business application manager (BAM))
- CSBA is the transient data queue for messages from the business application manager domain.
- CSBR (needed if using the bridge facility)
- CSBR is the transient data queue that logs the bridge facility messages.
- CSCC (needed for CICS client error messages)
- CSCC is the transient data queue that logs the CICS client error messages.
- 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.
- CSDH (needed if using the document handler template)
- CSDH is the transient data queue that receives explanatory messages from a document handler template exit program.
- 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.
- CSLB (needed to log LIBRARY resource definitions)
- CSLB is a log of all changes to the dynamic LIBRARY resources installed in the active CICS region. That is, install and discard of LIBRARY resources, and any changes to the configuration of LIBRARY resources, including changes to the enablement, ranking or critical status of a LIBRARY. If no dynamic LIBRARY resources are installed, no audit logging to CSLB takes place.
- 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 can 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.
- CSOO (needed for sockets domain messages)
- CSOO is the transient data queue for messages from the sockets domain.
- 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.
- CSQL (needed for transient data queue messages)
- CSQL is the transient data queue that receives audit log messages from the transient data queue manager itself.
- 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.
- CSSH (needed for scheduler services)
- CSSH is the transient data queue that receives messages from the scheduler services.
- 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 136 bytes and a minimum blocksize of 140 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 can code this destination as extrapartition, intrapartition, or indirect.
- CSZL (needed for the Front End Programming Interface)
- CSZL is the transient data queue that logs FEPI messages.
- CSZX (needed for the Front End Programming Interface)
- CSZX is the transient data queue that logs unexpected events for FEPI.
- CWBO (needed for CICS web support messages)
- CWBO is the transient data queue that logs the CICS web support messages that are issued from the CICS Web Interface.
- CWBW (needed for CICS web warning messages)
- CWBW is the transient data queue that logs the HTTP warning headers on messages that are received by CICS web support.