Sample to migrate the history database

Use the EQQICNVH sample to migrate the Tivoli Workload Scheduler for z/OS Operation History data from one release to another.

EQQICNVH is a job with the following steps:

  1. IDCAMS

    Makes it possible to rerun the job by deleting the data sets created in the previous run.

  2. UNLOAD

    Uses the DB2® utility named DSNTIAUL to unload the four tables with the Operation History data, the main table OPCMAIN, the occurrence table OPCOCC, the operation table OPCOPR and the joblog table OPCJL into the UNLOAD data sets. DSNTIAUL also creates the control statements required to later load the unloaded tables in the x.HISTMIG.CNTL data set.

  3. EDIT

    Modifies the LOAD control statements created in the preceding step to make the LOAD step add table entries to the existing tables instead of replacing the tables. The RESUME YES parameter is added.

  4. CONVERT

    Reads the entries of the unloaded tables. You specify the input release and the input subsystem name, and the output release and the output subsystem name. The entries in the UNLOAD data sets for the input release and input subsystem are converted to the record layouts of the output release and given the output subsystem name. The converted table entries are written to the LOAD data sets. The input and output releases can be the same.

  5. LOAD

    Uses the DB2 LOAD utility to add the new table entries to the Operation History tables; that is, the entries created by the CONVERT step.

  6. RESET

    Uses the DB2 REPAIR utility to clean the Operation History tables after the processing of the LOAD step. This step is necessary because LOG NO is specified in the DB2 LOAD utility control statements.

After the job successfully run, the following data sets are created:

After a successful run, the UNLOAD data sets contain a backup of the Operation History tables.

The statements in data set x.HISTMIG.CNTL can be used to recreate the original contents of the Operation History tables. Remove the RESUME YES parameters.

|At the end of the process, you must make a BIND of the new |version. You can use the BIND step provided with the EQQINIDB sample.