Allocating historical data set BBILIB member @@YZZ051

To help you decide the number of historical data sets you will need, the following table lists the type of PAS in which a product runs:

Before you begin

Consider the following information before creating historical data sets:

• Each PAS requires its own set of historical data sets if any product in the PAS intends to keep historical data.
• If you are running BMC AMI Ops Monitor for z/OS, and you want to implement long-term history recording, you need to define a second set of historical data sets. For long-term history files, the low-level qualifier begins with HST1DSnn (rather than HISTDSnn). After the long-term files are defined, see Customizing after installation for information about activating long-term data collection.
• If you are running version 3.0.00 (or later) of BMC AMI Ops Monitor for z/OS or version 5.8.00 (or later) of BMC AMI Ops Monitor for CMF, and you want to implement short-term history recording, you need to define another set of historical data sets. For short-term history files, the low-level qualifier begins with HST2DSnn (rather than HISTDSnn). After the short-term files are defined, see Customizing after installation for information about activating short-term data collection.
• If you do not want to use historical data for products that run in the z/OS PAS, delete the HISTDSnn and HST1DSnn DD statements from the PAS started task procedure that is described in Creating-the-CAS-startup-procedure.

• If you are running version 11.1.00 (or later) of BMC AMI Ops Monitor for Db2, you need to define a set of historical data sets to contain one-minute statistics records. The low-level qualifier begins with HST1DSnn (rather than HISTDSnn).

  Important

  If these data sets are not allocated, the BMC AMI Ops Monitor for Db2 health analysis views and MainView Explorer configurations are disabled.

• You can also add historical data sets dynamically from the DSLIST view, as described in Managing-historical-data-sets.
• If you have already defined the appropriate historical data sets, you do not need to perform this task.

To allocate and format the historical data sets

Use the following procedure (which uses BBILIB member @@YZZ051 as a model) to allocate and format historical data sets.

1. Determine how many VSAM files you need to define and how large the files should be.You can allocate a maximum of 100 data sets. Default customization creates three 30-cylinder data sets (on a 3390). When one data set is full, recording starts with the next data set until all data sets are full. Recording then begins again with the first allocated data set and overwrites any existing data.

   The appropriate number of historical data sets for your site depends on several factors, including system load, system configuration, and the specific BMC AMI Ops products that are sharing the z/OS PAS or the BBI-SS PAS. BMC suggests that you follow this procedure to determine the historical data set space requirements for your site:

   1. Decide how many historical data sets you want to use.There is no rule about how many historical data sets a site should have. At some sites, the number is based on the number of times that the system workload characteristics change during the day: typically three times, corresponding to shift changes. However, you might decide that a different number is appropriate for your site.
   2. Determine the size of the historical data sets.After you complete customizing all products, allow the PAS to run for approximately 24 hours. During the 24-hour period, note when the PAS receives messages indicating that the historical data set is full and is being switched. By using this method, you can determine how much space is typically required to hold historical data over a given amount of time. You can then adjust the size of the historical data sets according to whether you want them to hold data for a longer or shorter period of time.
2. Copy BBILIB member @@YZZ051 to a UBBSAMP data set.@@YZZ051 contains sample JCL to allocate three VSAM data sets with IDCAMS DEFINE CLUSTER statements.
3. Follow the instructions at the top of BBILIB member @@YZZ051 to modify the JCL according to your site's needs.

4. Submit the @@YZZ051 job.The historical data sets are allocated and formatted by using an initial record format that is shipped in BBILIB member @@YZZ052.

   The allocated data sets use a default data set name of hlq.smfid.HISTDSnn (for regular history), hlq.smfid.HST1DSnn (for long-term history or one-minute statistics for BMC AMI Ops Monitor for Db2 11.1.00 or later), or hlq.smfid.HST2DSnn (for short-term history).

   The variables are as follows:

   • hlq is the high-level qualifier for your BMC product libraries.
   • smfid is the SMF identifier of the system for which the data will be collected.
   • nn is a unique value from 00 to 99. Each historical data set must have a unique name.
5. Check the job output for condition code 0.If the condition code is not 0, review the job output messages, correct the problems, and submit the job again.
6. Ensure that a //HISTDSnn, //HST1DSnn, or //HST2DSnn DD statement is defined in the PAS started task procedure for each historical data set that you allocate