Batch Mass Migration

Step 1: Preparation

Step 0 in the Mass Migration process is to make sure the mass migrate libraries are empty. If not, they first need to be emptied or re-created.

Before commencing with a mass migration, the group requesting the mass migration must move programs, data, JCL, load members, etc., into appropriate migrate libraries. Specifically,

The SCT DB2 level for the SCT system being migrated (if relevant) must be updated. This can be done through SPX, option SCT, suboption 3, selection 1 (DB2 Production Level Update).
Source modules, JCL and data must be copied into ISP89.PAN.VALET. This Panvalet library must have a control code of 14.
Batch load modules must be copied into ISP89.MIGR.LOAD
Online load modules must be copied into ISP89.CICS.MIGR.LOAD
SCT DB2 RMAPs must be copied into ISP89.MIGR.RMAP. This can be done through SPX, option SCT, suboption 3, selection 3 (DB2 RMAP Library Copy).
SCT DB2 DCLs must be copied into ISP89.MIGR.DCL. This can be done through SPX, option SCT, suboption 3, selection 5 (DB2 DCL Library Copy).
SCT DB2 Bindings must be copied into ISP89.MIGR.BINDCNTL. This can be done through SPX, option SCT, suboption 3, selection 6 (DB2 BINDCNTL Library Copy).
SCT DB2 Control Information must be copied into ISP89.MIGR.CNTLLIB. This can be done through SPX, option SCT, suboption 3, selection 4 (DB2 CNTLLIB Library Copy).
Run AU5001 to insure that all JCL members have a JOB statement, valid USER= code and jobname matching the member name.

Step 2: Initial Backups

Before the actual migration process, production libraries should be backed up.

Back up PCP40.PAN.VALET
Back up PCP41.PAN.VALET
Back up PCP42.PAN.VALET
Back up PCP40.PAN.EXEC
Back Up PCP40.CICS.PROD.LOADLIB
Back Up PCP40.SCT.PROD.RMAP
Back Up PCP40.SCT.PROD.DCL
Back Up PCP40.SCT.PROD.BINDCNTL
Back Up PCP40.SCT.PROD.CNTLLIB

Step 3: Create Panvalet Migration Commands

To do a mass migrate into PCP40, PCP41 and PCP42 Panvalet, any members which already exist must first be deleted. After a migrate is completed, members in PCP40 must have their statuses changed to PROD status. This step creates the necessary commands to accomplish a mass migration into PCP40, PCP41 and PCP42. Specifically:

Run AU5005Z1 to create commands for PCP40
Run AU5005Z2 to create commands for PCP41
Run AU5005Z3 to create commands for PCP42

Step 4: Panvalet Migration

The migration process will disable members in PCP40, PCP41 and PCP42 that are to be replaced. These members will then be removed from their respective Panvalet libraries. New modules are then migrated, and those members in PCP40 that were migrated then must have their statuses changed to PROD status. Specifically:

Run AU5010Z1 to disable members in PCP40
Run AU5010Z2 to disable members in PCP41
Run AU5010Z3 to disable members in PCP42
Back up and purge PCP40.PAN.VALET
Back up and purge PCP41.PAN.VALET
Back up and purge PCP42.PAN.VALET
Run AU5015Z1 to transfer members into PCP40
Run AU5015Z2 to transfer members into PCP41
Run AU5015Z3 to transfer members into PCP42
Run AU5020Z1 to mark PCP40 items transferred as PROD
Run AU5020Z3 to mark PCP42 items transferred as PROD

Step 5: Back Up Panvalet Libraries After Migration

Once the transfers are complete, the PCP40, PCP41 and PCP42 Panvalet libraries should be backed up. Specifically:

Back up PCP40.PAN.VALET
Back up PCP41.PAN.VALET
Back up PCP42.PAN.VALET

Step 6: Library Migrations

Library modules should now be migrated into the appropriate batch and online production libraries. Specifically:

Run AU5025 to migrate batch load modules
Run AU5030 to migrate online load modules
Run AU5035 to migrate SCT DB2 RMAPs
Run AU5040 to migrate SCT DB2 DCLs
Run AU5045 to migrate SCT DB2 BINDCNTLs
Run AU5050 to migrate SCT DB2 CNTLLIBs

Step 7: Production Library Backup

After load modules and SCT DB2 libraries have been migrated, the production libraries should be backed up. Specifically:

Back up the PCP40.PAN.EXEC library
Back up the PCP40.CICS.PROD.LOADLIB library
Back up the PCP40.SCT.PROD.RMAP library
Back up the PCP40.SCT.PROD.DCL library
Back up the PCP40.SCT.PROD.BINDCNTL library
Back up the PCP40.SCT.PROD.CNTLLIB library

In Conclusion:

The above completes the mass migration of modules from ISP89 and ISP90 migrate datasets into appropriate production libraries. Library backups and Panvalet backups/purges have been defined generically. These items should already exist, and should be reused rather than reinvented. The Panvalet process used here will insure that members can be recovered from the Panvalet purge tape.

Migration Documentation

Last Modified: Thursday, 05-Oct-2000 08:16:13 CDT