Step 1. Prepare a plan

1. Prepare batch jobs and CLISTs

   Prepare batch jobs and CLISTs to automate as much of the upgrade as possible. Edit, copy, and delete files manually only when you have no choice. This enables you to review and test your jobs and CLISTs before the upgrade, and run them automatically during the upgrade.

   Place your batch jobs and CLISTs in a dedicated library.

   Examples:

   For Step 21. Adjust Control-M/Tape:

   Instead of copying files manually, prepare a CLIST that copies definitions from your previous version to the current release Control‑M/Tape PARM library.

   For Step 38. Copy definition libraries:

   Instead of copying libraries manually, make a batch job that copies libraries from your previous version to the current release.

2. Plan and schedule the migration

   Build your plan around the batch jobs, CLISTs, and site‑specific parameter members that make up the bulk of the work.

   Note: Keep a record of the customizations that you have made, both during the upgrade and after you have migrated production to the current release.