Defining data sets

CICS® system data sets are used by a number of CICS processes including temporary storage, transient data, transaction dump and trace. Some data sets are optional, others are required for running CICS. If a data set needs pre-formatting, a job that you can use for this purpose is shown.

For more information about CICS and data sets see:

Subtopics

Setting up CICS data sets
You must define a number of data sets to run CICS. Some of these data sets are mandatory, whereas others are needed only if you are using the corresponding facilities. You might also need to provide data set definitions for user files, DL/I databases, and terminals other than z/OS® Communications Server terminals.
Setting up temporary storage data sets
Each CICS region uses an area of 64-bit (above the bar) or 31-bit (above the line) storage in the CICS region as main temporary storage. You can define some auxiliary temporary storage for the CICS region in a nonindexed VSAM data set. Applications in a CICS region can also use shared temporary storage pools in a z/OS coupling facility.
Setting up data sets for transient data
Data sets that are used for transient data queues can be intrapartition or extrapartition. The transient data intrapartition data set is a VSAM entry-sequenced data set (ESDS) that is used for queuing messages and data within the CICS region. Transient data extrapartition data sets are sequential files, normally on disk or tape; you can use the queue to send and receive data outside the CICS region.
Setting up CICS log streams
Create CICS log streams to use the MVS™ system logger to record journaling and logging information.
Setting up the catalog data sets
You must define and initialize new CICS catalogs for CICS Transaction Server for z/OS, Version 5 Release 1.
Setting up auxiliary trace data sets
CICS trace entries can be directed to auxiliary trace data sets, which are CICS-owned BSAM data sets. If you want to use auxiliary trace, you must create the data sets before you start CICS; you cannot define them while CICS is running.
Defining dump data sets
CICS uses the dump data sets for recording dumps as a consequence of a failure that is detected when CICS is running, or upon explicit request.
Defining user files
This section tells you how to define user files and how to access VSAM data sets, BDAM data sets, data tables, and coupling facility data tables.
Defining the CDBM GROUP command data set
The CDBM GROUP command data set, DFHDBFK, is a VSAM key-sequenced data set (KSDS). The CDBM transaction uses this data set to provide a repository for stored groups of DBCTL commands, .
Defining the CMAC messages data set
The CMAC messages data set is a VSAM key-sequenced data set (KSDS) called DFHCMACD. The CMAC transaction uses DFHCMACD to provide online descriptions of the CICS messages and codes.
Defining the WS-AT data set
The data set you require to enable CICS Web Services Atomic Transaction (WS-AT) support is the WS-AT directory data set, DFHPIDIR. The WS-AT directory data set, DFHPIDIR, is a file containing a mapping between contexts and tasks.
Setting up the debugging profiles data sets
Application programmers who use certain debugging tools with CICS create debugging profiles which are stored in a VSAM key sequenced data set with an alternative index.
Encrypting data sets
You can encrypt any data sets that you use with CICS for which z/OS data set encryption is supported.

Parent topic: Setting up a CICS region

dfha2_defining_datasets.html | Timestamp icon

Last updated: Thursday, 27 June 2019