Manually allocating data sets
This optional task allocates the data sets that Near-Term History and Periodic Exception Processing require for data collection. The configuration tool assembles a job that contains allocation steps for all data sets that are needed for all Db2 subsystems according to your configuration. It is not allways necessary to allocate these data sets. Consider performing this task, if default allocations are too small or the data sets should be placed on specific storage volumes, or if custom retention policies need to be applied to collected data.
Before you begin
- ALTER privileges are granted for the high-level qualifiers that you specified for Near-Term History and Periodic Exception Processing data sets
- Configuration parameter KD2_OMPE_RUNALLOC is set to N (disabled)
- Near-Term History is enabled, and/or
- Periodic Exception Processing is enabled
About this task
The allocation job does not delete existing data sets. It allocates data sets only if the data sets do not already exist. Consider setting the configuration parameter KD2_OMPE_RUNALLOC to Y to automatically allocate the data sets using Configuration Manager or PARMGEN.
Procedure
- Edit the member rHilev.rte_name.RKD2SAM(ALLOCDS) as needed for your environment.
- Submit the job.