How to fully customize your data set allocations

You can customize data sets beyond the capabilities supported by Configuration Manager or PARMGEN.

During the configuration process of OMEGAMON for Db2 PE many data sets can be potentially pre-allocated, depending on the monitoring features selected, such as:

• Enhanced 3270 Thread History
• Static Sequential data sets
• Periodic Exception processing related data sets

For the selected features, most of these data sets will be pre-allocated only one time during the configuration process as they will be updated with data that is collected on the systems where the monitor runs. Primary examples are the Enhanced 3270 Thread History VSAM data sets.

Configuration Manager or PARMGEN generate a JCL to allocate these “static” data sets in RKD2SAM(ALLOCDS); this JCL can also be submitted manually, if needed. The configuration process provides only limited flexibility on the customization of the allocation attributes of the individual data sets, especially as mostly not needed for SMS storage based configurations. For non-SMS storage configurations, the allocation process can be tailored to meet specific needs, for example to specify a specific volume for each Enhanced 3270 Thread History data set. This granular customization can be accomplished by modifying the RKD2SAM(ALLOCDS) JCL accordingly.

Use the KD2_OMPE_RUNALLOC and KFJ_LOCAL_KD2_RUN_ALLOC (for remote deployments) parameters to drive the allocation of the data sets, for example, by running the Configuration Manager GENERATE action. For example, if you specify KD2_OMPE_RUNALLOC as “N”, the RKD2SAM(ALLOCDS) member will be generated, but not executed. If you want to tailor ALLOCDS after the initial generation and submit manually, use the “N” option for KD2_OMPE_RUNALLOC and add the RKD2SAM(ALLOCDS) job to the exclude member KCI$XW2R in the embed override member.