search cancel

Migration Checklist - TPX 5.4

book

Article ID: 225496

calendar_today

Updated On:

Products

TPX - Session Management

Issue/Introduction

Use this checklist when migrating to TPX 5.4.

Resolution


Caution:
Before installing TPX on production system, perform the installation and initial evaluations of the product and its components on a test system.
Business Value:
Evaluating TPX in a test environment helps to detect any possible problems before rolling out the product to a production system. New releases of TPX are always compatible with previous releases, letting you run a new release on a test system while still running the older version on a production system.

WARNING: It’s important to follow this procedure , which outlines the proper upgrading procedures. Failure to follow these instructions, explicitly, could, and most likely will, result in unexpected failures, such as VSAM errors, abends and unpredictable results.


Installing TPX 5.4


1. Read through the 'Installing' documentation.
2. Download and Install TPX 5.4.   
3. Download all the PTF's for TPX 5.4.

4. Follow the area 'Configuring your Product'.  Be sure you can bring up this 'starter' 5.4 TPX.
5. Next, follow the ‘Post Installation’ Tasks.
6.  Before any of the 'Migration Checklist' can be done, the product has to be installed successfully.
7. Once the product has been installed successfully, follow the ‘Migration Checklist’ below (find in blue some extra info from ‘Migration Information’ documentation).


Migration Checklist
Note: All the steps on the Checklist are important to ensure a smooth upgrade.  

Use this checklist when migrating to TPX 5.4

  • On the mainframe, refer to CB0VJCL library, see member $INDEX for the JCL members.
  • Use the file allocations from the new CA TPX as delivered. (Refer to CB0VJCL library, member DEFVSAM)
  • Make a backup of the old CA TPX VSAM files.(Refer to CB0VJCL library, member VBACKUP or LSBACKUP (if L-SERV)). Important note: TPX must be down!
  • Copy the CA TPX VSAM file backups into the new allocated VSAM files. (Refer to CB0VJCL library, member VRESTORE or LSRESTOR (if L-SERV)). Important note: TPX must be down!
  • Verify that LOADLIB is APF authorized.
  • Run RESET INTEGRITY (Refer to CB0VSRC library, member BATCHINI) This is done in the last step in the VRESTORE. Important note: TPX must be down!
  • Migrate any custom ACL/E programs to the new ACL/E library.
  • Migrate any custom PANEL libraries to the new PANEL library.
  • Review if any call points have been added or removed from the new distributed EXITS and update your code accordingly.
  • Reassemble all custom user exits against the new libraries. (Create a v5.4 USERLOAD for the custom exits - do not override the delivered exits in CB0VLOAD. Also, verify that USERLOAD is APF Authorized)
  • Modify the new CA TPX startup procedure to refer to tables from migrated files (for example, SMRT, ACT, and so on).
  • Review new SMRT parameters:
    1. Take screen prints of each SMRT panel in the existing release.
    2. Create a new SMRT in the new release and take screen prints of these.
    3. Compare both the SMRTs to identify new fields and their defaults.
      If no changes were applied to the SMRT in the new release, the defaults will be in effect for any new fields introduced since the existing release.

Note:  As of r4, VSAM files are upwardly compatible and do not require conversion.