IBM OS/390 User Manual

this option now governs restart in two separate types of situation.

the scope of this parameter is extended to cover VTAM persistent
sessions. In CICS/VSE this parameter was meaningful for CICS
regions running with XRF only.

Before you install your CICS data sets you should determine the DASD
requirements for all CICS data sets and MVS data used by CICS.

Below are the data sets needed to implement CICS TS. You should review the
CICS System Definition Guide, SC33-1682 and the CICS Installation Guide,
GC33-1691 for full details on the facilities, functions and usage for each data set
listed below:

Temporary storage data set
Transient data destination data sets
CICS log streams
System definition data set
Catalog data sets
Auxiliary trace data sets
Dump data sets
Availability manager data sets
CMAC messages data set

After you have installed CICS, and applied any necessary service, you can run
the DFHCOMDS, DFHDEFDS, and DFHCMACI jobs to create the CICS data sets.
MVS storage management facility (SMS) should facilitate the placement, and
allocation of your data sets. Still, you should keep an eye on extent allocations
for the data sets used by CICS, for performance reasons (that is, is the single
extent allocation too small).

Be sure you note that CICS Log is unique to CICS TS, and requires special
consideration as opposed to journal files used in CICS/VSE. In OS/390 Version 2
Release 4, the CICS log manager supports the DASD-only option of the MVS
system logger. This means that individual CICS log streams can use either
Coupling Facility structures or DASD-only logging.

Figure 13 on page 146 shows the choices you have when defining individual log
streams, depending on the hardware and software you are using.

Chapter 6. CICS