IBM® TXSeries® for Multiplatforms V6 IBM® TXSeries® for Multiplatforms V6 Migration Overview This presentation will cover migrating to TXSeries for Multiplatforms V6 from the previous version of TXSeries. Goals Goals Provide an overview of the migration process when upgrading to TXSeries for Multiplatforms V6 The goal of this presentation is to provide an overview of the migration process available with TXSeries for Multiplatforms V6. Agenda Agenda Discuss some migration related considerations when upgrading to TXSeries V6 Describe the general migration process when moving from a previous version to TXSeries V6 The agenda for this presentation is to describe migration considerations and the steps involved in migrating to TXSeries for Multiplatforms V6 from the previous version of TXSeries. Migration considerations Migration considerations Section This section will take you through the migration considerations. TXSeries co-existence TXSeries co-existence Two versions of TXSeries cannot co-exist on a machine Migration of a single machine is therefore: Export CICS® regions De-install old version of TXSeries Install new version of TXSeries Import and migrate region definitions Migration to a new machine is a simpler process Less downtime Opportunity for housekeeping Opportunity to upgrade supporting software and retest It is important to understand that multiple versions of TXSeries cannot co-exist on the same machine. Because of this, migrating the old version of TXSeries to a new machine is considered optimal. This will give you the benefit in having minimal downtime of your systems where the current level of TXSeries is functional, and will also provide you an opportunity to upgrade the supporting software and conduct testing in the migrated environment. Migration to TXSeries V6: Key points Migration to TXSeries V6: Key points All the following must now exist on same machine as the CICS region SFS Servers PPC Gateway Servers With TXSeries V6, you will need to define and configure SFS servers and PPC Gateway servers on the same machine where your CICS regions are defined. Initial migration checks Initial migration checks Ensure the latest level of supported software is installed See http://www.ibm.com/software/htp/cics/txseries/ Review any new resource definition attributes added and modify their values accordingly. For example: TCPProcessCount [ LD definition ] ServerMemCheckInterval [ RD definition ] NameService [ RD definition ] Check user written scripts working against files such as the console, symrecs, or CSMT.out as message formats can change. Before migrating, you should ensure the latest level of supported IBM and third-party products are installed. You should also review the release notes for any new or changed features, and to ensure backward compatibility for your CICS server applications. For example, with TXSeries V6 there are new resource definition attributes introduced, such as ServerMemCheckInterval that enables checking of process memory growth, that will need your attention. If you have written scripts to interpret CICS logs such as console, symrecs and CSMT.out then you must check for any changes in the format of these logs. Migration steps Migration steps Section This section will describe the steps necessary to perform the migration. CICS region migration steps CICS region migration steps Export the CICS regions to be migrated to an archive file cicsexport -r -o Import the CICS region on system with latest CICS level cicsimport -r -i Begin the migration procedure by first migrating the CICS region definitions. For this you will need to export the region definitions of the current version of TXSeries using the cicsexport command. The cicsexport command will create an archive file containing the region data. This archive file must be transferred in BINARY mode to the target machine where the new version of TXSeries is installed. Once transferred, you will use the cicsimport command to import the region data from the transferred archive file. The cicsimport command will create the CICS region by reading the definitions from the archive file. CICS region migration steps CICS region migration steps Migrate the CICS region definitions to the latest level cicsmigrate –r -g