Information

This site will undergo maintenance on Friday, 26 September at 2:00 AM CDT / 12:30 PM IST and may experience a short period of instability during that time.

Specify the number and names of CMRDETL history files


Specify the number of CMRDETL history files with the DSN Count option. For current installations using dual detail data sets, this number is set to 2. The maximum number of CMRDETL history files that you can define for a single IBM CICS target is 10.

Specify the names of CMRDETL history files with the DSName field for the Dataset I and Dataset II options..

Dual-detail data sets

When creating definitions for dual-detail data sets, you must specify a DSN Count of 2. You must also provide the data set names for both history files with the DSName option for Dataset I and Dataset II.  Enter fully qualified data set names and BMC AMI Ops Monitor for CICS uses these names as you entered. 

If you plan to allow BMC AMI OpsM for CICS to automatically define the data sets, you must specify the size, location, and SMS class data for the data sets for both files.

Multiple-detail data sets

If you create more than 2 data sets (multiple-detail data sets), you must specify a DSN Count in the range of 3 to 10. You must also provide a high-level qualifier (hlq) in Dataset I that BMC AMI OpsM for CICS uses as the data set name prefix in defining and allocating the file. BMC AMI OpsM for CICS appends the Dnn suffix to the hlq in the format hlq.Dnn, where nn is the file number. BMC AMI OpsM for CICS uses the file number to process using the files. All sequenced files must be present without gaps.

For example, if you specify 5 CMRDETL data sets, and enter an hlq of MVCICS.CICSPROD.CMRDETL for the DSName value for Dataset I, BMC AMI OpsM for CICS uses the following five data set names:

  • MVCICS.CICSPROD.CMRDETL.D01
  • MVCICS.CICSPROD.CMRDETL.D02
  • MVCICS.CICSPROD.CMRDETL.D03
  • MVCICS.CICSPROD.CMRDETL.D04
  • MVCICS.CICSPROD.CMRDETL.D05

If you plan to use the BMC AMI OpsM for CICS facility to automatically define the data sets, you must specify the size, location, and SMS class data only for Dataset I.  For multiple-detail data set definitions, BMC AMI OpsM for CICS ignores any options specified for Dataset II

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for CICS 7.5