IBM OS/390 User Manual

Page of 673
Warning:
When you migrate your CSD entries you must ensure that you do not
copy over IBM supplied definitions in groups that you have defined. The
reason is that some of the groups and resources were changed and/or
deleted. Thus, you should see that your user groups with IBM defined
resources are copied from the newly defined CSD. Once, you have
imported your defined resources into the CSD for MVS, be cognizant of
changes via the ALTER command, the default attributes and/or new
attributes may not be what you desire. To illustrate, the SESSION
resource definitions allows the send and receive prefixes to default. CICS
creates the last three characters of the session names from the
alphanumeric characters A through Z, and 1 through 9. These
three-character identifiers begin with the letters AAA, and continue in
ascending sequence until the number of session entries reaches the limit
set by the SENDCOUNT or RECEIVECOUNT value.
6.1.7.2 RDO
Here are items to consider with the use of RDO on your CICS/ESA system:
Be sure that all user defined TRANSACTION resources specify the attribute
(SPURGE). SPURGE must be set to purge transaction from the system and to
detect loops.
CICS-supplied transactions have changed (for example, CSSN and CSSF are
CESN/CESF). CICS TS removed transactions CSMT, CSOT, CSSF, CSSN, and
CSST. Please refer to your 
CICS Supplied Transaction, SC33-1686 for more
details.
Below are examples of resources and/or attributes changes:
TRANSACTION/TCLASS
is replaced by the TRANCLASS parameter, within the new
TRANCLASS resource definition.
CONNECTION/SECURITYNAME(MRO)
is obsolete on MRO connections. To specify bind-time and link
security for MRO connections, you must define appropriate RACF (or
another ESM) security profiles.
CONNECTION/PROTOCOL
the scope of this parameter is extended for the external CICS
interface (EXCI). This parameter allows client programs (batch
programs) the ability to access CICS services.
PROGRAM/EXECKEY
the effect of this parameter is extended for transaction isolation. With
transaction isolation active, a user-key program has read and write
access to the user-key task-lifetime storage of its own task only, and
to any shared DSA storage, if its transaction is defined with
ISOLATE(YES).
SESSIONS/RECOVOPTION
this parameter is extended to cover VTAM persistent sessions. In
earlier releases of CICS it was meaningful for CICS regions running
with XRF only.
SESSIONS/RECEIVEPFX/SENDFX
you no longer need to specify send and receive prefixes on MRO
session definitions.
144
VSE to OS/390 Migration Workbook