Migrating TXSeries for Multiplatforms regions from V5.1 to V6.2 or V7.1
Preventive Service Planning
Steps to follow when migrating a region from TXSeries V5.1 to V6.2 or V7.1
You need to complete the following steps for migrating a region from TXSeries V5.1 to V6.2 or V7.1:
1. Use cicsexport utility to export your existing TXSeries V5.1 region. Running this command will create an archive file that you can import later to TXSeries V6.2 or TXSeries V7.1. This archive file will also serve as a backup if any problems are encountered during migration.
# install_dir/bin/cicsexport -r region_name -o archive_file
is the directory where CICS is installed. On AIX, it is /usr/lpp/cics.
region_name is the name of the region to export.
archive_file is the name of archive file to be created.
2. Uninstall CICS and Encina components of TXSeries V5.1 from your workstation.
3. Install TXSeries for Multiplatforms V6.2 or V7.1.
4. If you are moving the region to a new workstation, import your region as described in step a and b. If you are migrating to a new version of TXSeries on the same machine, go to Step 5.
a. Transfer the archive file created using cicsexport command to the workstation where TXSeries V6.2 or TXSeries V7.1 is installed.
b. Use cicsimport utility as shown to import the region.
# install_dir/bin/cicsimport -r region_name -i archive_file byteorder_specifier
install_dir is the directory where CICS is installed.
region_name is the name of the region to import. region_name must be name of the region that was exported from V5.1, and must not match the name of an existing region on the new workstation .
archive_file is the name of the archive file created when you ran the cicsexport command.
Byteorder_specifier indicates whether byte swapping is necessary while importing the region from archive file. AIX, Solaris (on PA-RISC) and HP-UX (on Itanium and PA-RISC) are big-endian operating systems. Windows is a little-endian operating system. A byte-swapping is required only when you are migrating across a big-endian and little-endian operating system. You need to specify -B as Byteorder_specifier if you are migrating across operating systems of different endian order. For example, you need to specify -B option when a migration is done from Windows to AIX or vice versa.
a. Create an upgrade script using the following command:
# install_dir/bin/cicsmigrate -g script_name -o log_filename -r region_name
install_dir is the directory where CICS is installed.
script_name is the full path name of the upgrade script.
log_filename is the log file, that logs the information about the migration.
region_name is the region that needs to be migrated.
b. Run the upgrade script by entering the following command:
# ksh script_name
script_name is full path name of the upgrade script.
After the successful execution of this script , the region would have migrated to the latest version level.
6. You can verify whether migration is successful by checking the region definition file (RD.stanza) of the migrated region.
If you have migrated to TXSeries Version 6.2, the first line in RD.stanza will be updated to m113 .
If you have migrated to TXSeries Version 7.1, the first line in RD.stanza will be updated to m114 .
7. Make sure that the following variables are unset on the workstation before starting the region on the migrated version is attempted.
8. Make sure that the SFS file system is migrated to current level by checking SSD.stanza before starting the region on the migrated version is attempted.
If you have already migrated SFS to TXSeries Version 6.2, the first line in SSD.stanza will be updated to m113.
If you have already migrated SFS to TXSeries Version 7.1, the first line in SSD.stanza will be updated to m114
If you are not migrated the SFS filesystem, use ‘cicmigrate –s’ command to migrate the SFS file system to current level before starting the region or SFS.
To create a shell migrate script that upgrades only the SFS resource database,
cicsmigrate -g script_name -o /tmp/logfile -s
9. If you configured PPCGWY server in your environment, Make sure that the PPCGWY server is migrated to current level by checking GSD.stanza before starting the region on the migrated version is attempted
If you have already migrated PPCGWY server to TXSeries Version 6.2, the first line in GSD.stanza will be updated to m113.
If you have already migrated PPCGWY server to TXSeries Version 7.1, the first line in GSD.stanza will be updated to m114
If you are not migrated the PPCGWY server, use ‘cicmigrate –p’ command to migrate the PPCGWY server to current level before starting the region or PPCGWY server.
To create a shell migrate script that upgrades only the PPCGWY server resource database,
cicsmigrate -g script_name -o /tmp/logfile -p
10. Cold start the CICS region on the workstation you upgraded, by entering the following command for each region:
# install_dir/bin/cicscp -v start region region_name StartType=cold
11. To ensure that no error occurred during the region restart, check the latest console.< nnnnnn> file in the /var/cics_regions/region_name directory.
12. Run a CICS based or user-application transaction on the 3270 terminal “cicslterm” to test the connectivity to the region.
See the TXSeries for Multiplatforms Information Center for information on migrating data in SFS across the release.
You can follow the topic, Migration to TXSeries for Multiplatforms from an earlier version in TXSeries V7.1 Information Center to migrate regions, SFS and data.
The Information Center link for migrating to TXSeries 7.1 is http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp?topic=/com.ibm.cics.tx.doc/tasks/t_mig_tx_previous_ver.html
Refer to the following link to find the equivalent of TXSeries V5.1 Encina environment variables in TXSeries V7.1: http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp?topic=/com.ibm.cics.tx.doc/reference/r_environmt_varbles.html
For SARPC environment variables in TXSeries V7.1, see http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp?topic=/com.ibm.cics.tx.doc/reference/r_sarpc_env_variable.html
Also, for further references you can find Migration guidelines and checklist in the following IBM Redbooks:
More support for:
TXSeries for Multiplatforms
Software version: 6.2, 7.1, 8.1, 8.2
Operating system(s): AIX, HP-UX, Solaris, Windows
Reference #: 1328969
Modified date: 09 September 2014
Translate this page: