Before creating historical data sets
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 MainView 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 MainView for z/OS customization for information about activating long-term data collection.
- If you are running version 3.0.00 (or later) of MainView for z/OS or version 5.8.00 (or later) of CMF MONITOR , 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 MainView for z/OS customization 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 MainView 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).
- 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.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*