some CICS migration guidelines
Check software and hardware requirements
- Disk space
- Maintenance levels
- HFS (SMS) for java bits and pieces etc
- IMS and/or DB2 releases plus other related software.
- Third party products?
Research and apply any required maintenance
Be aware of changes to CICS-supplied transactions
- Changed CEMT commands
- New CEMT commands
- Changes to CETR
- Changes to CDBM
- Changes to CEBR
- New CBAM transaction
- CWBC obsolete
Review changes introduced with this release including the following…
- System initialisation parameters
- Additions to CICS RACF category 1 transactions
- Resource definition (online) changes
- Resource definition (macro) changes
- The application programming interface (API)
- The system programming interface (SPI)
- CICS-supplied utility programs
- The global user-exit programming interface
- The exit programming interface
- The task-related user-exit programming interface
- The external CICS interface (EXCI)
- User-replaceable modules
- Monitoring and statistics
Follow ServerPac dialogs
Integrating CICS and OS390
(Some of these tasks will already be in place for existing CICS also some tasks can wait.)
- Authorise the hlq.SDFHAUTH library
- Authorise CICS regions to access MVS resources
- Define the default CICS userid to RACF
- Install CICS-required modules in the MVS linklist
- Define CICS as an MVS subsystem
- Install the CICS Type 3 SVC
- Decide whether to use the high-performance option
- Define CICS regions as applications to VTAM
- Install CICS modules in the MVS link pack area
- Define CICS IPCS exit control data to MVS
- MVS Program properties table entries
- MVS performance definitions
- MVS automatic restart management definitions
- MVS cross-system MRO definitions
- Definitions required for VSAM RLS support
Review messages and automation
Defining the logger environment for CICS journaling
Applying service to CICS Transaction Server for OS/390
Perform IVPs
Convert a test region and check it out
Tasks required for converting a region include
- Decide whether to share CSD’s.
- Create the necessary unique datasets (temporary storage, transient data etc)
- Create the JCL
- Convert the SIT
- Assemble any necessary tables
- Define the RDO objects
- Integrate DB2 / MQSeries etc
- Is there a relevant model in the logging structure for journaling etc?