IBM OS/390 User Manual
JCT
The CICS log manager does not support journal data sets,
making the journal control table obsolete. The CICS
system log and journals are mapped to MVS system
logger log streams (or, for some journals, SMF data sets)
by means of JOURNALMODEL resource definitions.
making the journal control table obsolete. The CICS
system log and journals are mapped to MVS system
logger log streams (or, for some journals, SMF data sets)
by means of JOURNALMODEL resource definitions.
JSTATUS
CICS log manager does not support journal data sets, on
either disk or tape, making this initialization parameter
obsolete.
either disk or tape, making this initialization parameter
obsolete.
PLI
removed because DOS PL/I is not supported.
SCS
removed because the storage cushion size is determined
by CICS.
by CICS.
System initialization modifications (SIMODs) are obsolete.
START
the INITIAL option is added to indicate that CICS is to
initialize as if this is a first-time start of the CICS region.
Unlike a normal cold start, the cold start resulting from
START=INITIAL causes CICS to purge the system log as
well as the catalog data sets. An INITIAL start is the same
as if you start CICS with a new system and newly defined
catalog data sets.
initialize as if this is a first-time start of the CICS region.
Unlike a normal cold start, the cold start resulting from
START=INITIAL causes CICS to purge the system log as
well as the catalog data sets. An INITIAL start is the same
as if you start CICS with a new system and newly defined
catalog data sets.
TLT
is replaced by the CSD function.
TRACE
is replaced by new trace parameters.
TSMGSET there is no need for dynamic storage for temporary
storage pointers as a result of the restructure of the
temporary storage domain.
temporary storage domain.
ZCP
is not modifiable, thus the parameter is removed.
Note:
CICS/ESA provides a default source (DFHSIT$$) with which you may start
or use the default load module (DFHSIT) and override the defaults.
6.1.7 CSD and RDO Considerations
Below are commonly identifiable changes required to migrate a CICS/VSE
system to CICS TS CSD and online resource definition entries. These parameters
listed below should be viewed as a reminder of items to consider, and not as an
inclusive list of parameter changes and/or obsolescence. You should review the
CICS Resource Definition Guide, SC33-1684 for full details of parameters required
for the different online resource definitions.
system to CICS TS CSD and online resource definition entries. These parameters
listed below should be viewed as a reminder of items to consider, and not as an
inclusive list of parameter changes and/or obsolescence. You should review the
CICS Resource Definition Guide, SC33-1684 for full details of parameters required
for the different online resource definitions.
6.1.7.1 CSD
To start with the CSD is mandatory in CICS/MVS, but does not require an entry
in the FCT.
in the FCT.
You should define and initialize the CSD from the CICS/ESA system, as opposed
to attempting to upgrade the CICS/VSE CSD to CICS/ESA. The reason is you
want the space allocation of your CSD to accommodate the addition of VSAM
FCT and DCT entries plus entries for comment fields (that is, entries not
available to CICS/VSE). After the CSD is defined and initialized on the CICS/MVS
system, you can use the DFHCSDUP utility to EXTRACT your user definition from
CICS/VSE, then import it to CICS/MVS
to attempting to upgrade the CICS/VSE CSD to CICS/ESA. The reason is you
want the space allocation of your CSD to accommodate the addition of VSAM
FCT and DCT entries plus entries for comment fields (that is, entries not
available to CICS/VSE). After the CSD is defined and initialized on the CICS/MVS
system, you can use the DFHCSDUP utility to EXTRACT your user definition from
CICS/VSE, then import it to CICS/MVS
′
s CSD. For details on using DFHCSDUP
refer to your CICS Resource Definition Online and CICS Customization Guide.
Chapter 6. CICS
143