Start the new system

  1. Change JTOPTS CURRPLAN(NEW) to CURRPLAN(CURRENT).
  2. In the BATCHOPT statement used by the batch job, uncomment the JRUNHISTORY parameter if you had commented it out.
  3. Start the controller. The merged checkpoint data set will enable it to continue reading the event records.
  4. The first time you start the trackers at the version to which you are migrating, in the OPCOPTS statement specify BUILDSSX(REBUILD) and SSCMNAME(EQQSSCMn,PERMANENT) then delete these parameters because no longer required.
  5. Enter the Service Functions dialog on the controller, and activate job submission (if it is not already active).
  6. Submit a daily plan replan or extend as soon as possible after migration. Until a new current plan is created, any references to special resources will cause the resource object to be copied from the EQQRDDS to the current-plan-extension data space. This processing has some performance overheads.

    The new-current-plan-extension data set (EQQNCXDS) is built during daily planning to contain all special resources referenced by operations in the new current plan.

  7. After the first IPL of the z/OS system, delete the BUILDSSX and SSCMNAME parameters from the OPCOPTS statement in the Z controller and trackers, because they are no longer required.