Step 12. Creating the DB2 database

In this optional step, required only if you need the history function, you create the DB2® database, tables, and indexes. If you need to migrate the history data that you have already defined, then run only the EQQICNVH sample. You can use the history function to rerun operations after they have completed and are no longer in the current plan. When the history function is active, details about completed operations are copied to the DB2 database when you extend the current plan, and remain in the database for a period that you specify. See Tivoli® Workload Scheduler for z/OS®: Managing the Workload for a description of how to use the history function, and Tivoli Workload Scheduler for z/OS: Customization and Tuning for a description of the necessary initialization parameters.

Note:
Do not stop DB2 with the quiesce option if the scheduler history function is implemented. A quiesce of DB2 could cause any dialog user to hang until DB2 termination is complete. Use the +stop db2,force command, instead.

Edit and run the supplied sample job EQQINIDB. This job:

  1. Binds the DB2 plan.
  2. Grants authorities.
  3. Creates the database.
  4. Creates the tablespace.
  5. Creates the tables and indexes.

Save the output of this job, because this lists the objects that were created, with their parameters. Ensure that you bind the plan and grant the necessary authorities after applying service to Tivoli Workload Scheduler for z/OS.