z/VSE 6.1 requires an initial installation.
z/VSE 6.1 migration information is provided in the z/VSE Planning and the z/VSE Administration books. You can download them from z/VSE's documentation page - here.
In addition we just uploaded a migration paper - see my related blog entry from last Thursday. The paper is here.
Please let me know, if there is anything not addressed or just send me your questions.
Mike Poil started a CICS migration discussion on VSE-L too.
The migration to the new TCP/IP stacks - TCP/IP for z/VSE 2.1 and IPv6/VSE 1.2 - should be relatively easy.
There is a bit more to consider for the migration to the new CICS TS for z/VSE 2.1. We have comprehensive migration chapters added to the CICS TS for z/VSE 2.1 Enhancements Guide (in short CICS Enhancements Guide).
It's also on our documentation page. The CICS Enhancements Guide is here.
There we describe the tasks to migrate to CICS TS for z/VSE 2.1. Below is a short overview:
- Migrate your CICS tables
All IBM-supplied tables are built with the CICS TS for z/VSE 2.1 level. If you use your own CICS tables (SIT, MCT, DFHCNV, and others) you need to reassemble and re-link these tables using the macros of CICS TS for z/VSE 2.1.
- Migrate your CSD data set
- Migrate CICS application programs
- If you use EXEC CICS API interfaces within your application programs, you can run your programs unchanged with CICS TS for z/VSE.
- If you use internal CICS control blocks within programs it is recommended to reassemble these programs.
- Migrate Global User Exit Programs
- The changes because of channels are transparent for existing user exit programs.
- Various internal CICS control blocks were changed. The changes are not transparent. If you use these control blocks within your exit programs, you have to reassemble these programs.
- Migrate DFHCNV and DFHUCNV user-replacable programs
If you are using the DFHCNV and DFHUCNV user-replaceable programs you need to reassemble the DFHCNV, and modify the DFHUCNV program.
- Migrate Dynamic Transaction Routing programs
If you use user-written dynamic transaction routing programs, there is a whole chapter that helps to decide whether you need to update these programs.
- If you have enabled monitoring
- If you use your own monitoring control table (MCT) it has to be reassembled.
- You have enabled performance class monitoring, you have to create a performance dictionary record with the DFHMNDUP utility program shipped with CICS TS for z/VSE.
- Channel and container related values were added to the performance-class monitoring records. To INCLUDE or EXLUDE these values you can modify the DFHMCT TYPE=RECORD macro.
- If you use statistical reports
- New fields were added to the statistics A14 record and the statistics report.
- Always use the version of the DFHSTUP program from the same release of CICS as the data that it is to process.
- Use correct version of CICS-supplied utility programs
- Always use the version of the CICS-supplied utility programs shipped with your CICS TS version.
- Migration from CICS/VSE 2.3 to CICS TS
- Status of CICS/VSE 2.3:
- End of service of CICS/VSE 2.3 is effective since October 31, 2012.
- Starting with z/VSE 4.3, the CICS coexistence environment was dropped.
- Starting with z/VSE Version 5, CICS/VSE 2.3 can no longer be used with z/VSE.
- It is recommended to first migrate from CICS/VSE 2.3 to CICS TS for VSE/ESA 1.1.1 on your current system (z/VSE 4.2 or older). This allows you run both CICS versions in a coexistence environment.
- The CICS Application Migration Aid is no longer shipped with CICS TS for z/VSE 2.1.
- Regarding migration from CICS/VSE 2.3 to CICS TS for VSE/ESA please refer additionally to:
CICS Transaction Server for VSE/ESA Migration Guide and the CICS Enhancements Guide,
IBM Redbook Migration to VSE/ESA 2.4 and CICS Transaction Server for VSE/ESA 1.1
- Migration of RPG II online applications
If your current system is z/VSE 4.1 or 4.2, it is recommended to migrate your RPG II online applications on your current system. Refer to the CICS Enhancements Guide.