Step 9. Allocating data sets

At this stage of the installation of your Tivoli Workload Scheduler for z/OS system, you allocate the data sets that your JCL procedures refer to. You can create the data sets by using the jobs created by the EQQJOBS installation aid.

If you are using the EQQJOBS installation aid, you will already have generated several members in the output library that you specified.

Consider carefully where Tivoli Workload Scheduler for z/OS data sets are allocated in your production environment. Some data sets can be highly active. Avoid placing these data sets on DASD volumes with high activity because this can result in poor performance due to contention. Also consider the ability to recover data sets if a DASD volume becomes unusable. If you place all your data sets on the same volume, you must recover many data sets before you can continue your Tivoli Workload Scheduler for z/OS service. Tivoli® Workload Scheduler for z/OS®: Customization and Tuning describes recovery of Tivoli Workload Scheduler for z/OS data sets in detail.

The space to allocate for your data sets depends upon the workload at your installation. It is difficult to give precise figures for the amount of space you will need. The space allocated by the sample JCL should give you enough space to at least get started. These amounts will be enough for the Tivoli Workload Scheduler for z/OS service for many installations. Use Table 24 as a guide to allocate space for VSAM data sets.

The following sections describe the Tivoli Workload Scheduler for z/OS data sets and include examples of the JCL needed to create them.