Number of User Report entries to be retained

The number of History User Report entries to be retained.

• Maximum: 9 digits.

Number of $SYSDATA entries to be retained

The number of $SYSDATA entries to be retained.

• Maximum: 9 digits.

Extend

Whether a secondary extent is allocated automatically when an out-of-space condition is detected.

Valid values are:

• A (Auto) – A secondary extent is automatically allocated when an out-of-space condition is detected. Default.
• M (Manual) – Requires a secondary extent to be manually allocated after an out-of-space condition is detected.

Note: The EXTEND parameter is ignored if no secondary space amount is specified in the SPACE parameter.

Secondary allocation (percentage of primary)

Secondary space allocation (percentage of primary allocation). BMC recommends that you specify approximately 50%.

Data Comp

Data component of the History User Report List file. This parameter has the following subparameters:

• DUAL – Whether dual (mirror) image processing is implemented. The contents of the dual file are kept synchronized by Control‑D with the contents of the primary History User Report List file. Use of the dual file provides data recovery capabilities if the primary History User Report List file becomes damaged or inaccessible. Valid values are:
  — Y (Yes) – Allocate a dual (mirror) image History User
       Report List file.
  — N (No) – Do not allocate a dual (mirror) image History
       User Report List file.
• DUALM – Whether execution terminates if a non-recoverable I/O error occurs while processing the dual image file. This parameter is only relevant if dual image file processing is implemented. Valid values are:
  — Y (Yes) – Terminate execution if a nonrecoverable I/O
       error occurs while processing the dual (mirror) image
       History User Report List file.
  — N (No) – Continue execution if a nonrecoverable I/O
       error occurs while processing the dual (mirror) image
       History User Report List file.
• DUALST – Whether Control‑D performs timestamp checkpoint processing to ensure that the primary file and dual image file are fully synchronized. Enabling this option ensures greater data integrity at the expense of increasing I/O processing overhead.
  — Y (Yes) – Perform timestamp checkpoint processing.
  — N (No) – Do not perform timestamp checkpoint
       processing.

Index Comp

Index component of the History User Report List file. This parameter has the following subparameters:

• DUAL – Whether dual (mirror) image processing is implemented. The contents of the dual file are kept synchronized by Control‑D with the contents of the primary History User Report List file. Use of the dual file provides data recovery capabilities if the primary History User Report List file becomes damaged or inaccessible. Valid values are:
  — Y (Yes) – Allocate a dual (mirror) image History User
       Report List file. BMC recommends that you
       do not use a dual file for the Index Component.
  — N (No) – Do not allocate a dual (mirror) image History
       User Report List file.
• DUALM – Whether execution terminates if a non-recoverable I/O error occurs while processing the dual image file. This parameter is only relevant if dual image file processing is implemented. Valid values are:
  — Y (Yes) – Terminate execution if a nonrecoverable I/O
       error occurs while processing the dual (mirror) image
       History User Report List file.
  — N (No) – Continue execution if a nonrecoverable I/O
       error occurs while processing the dual (mirror) image
       History User Report List file.

DUALST – Whether Control‑D performs timestamp checkpoint processing to ensure that the primary file and dual image file are fully synchronized. Enabling this option ensures greater data integrity at the expense of increasing I/O processing overhead.
— Y (Yes) – Perform timestamp checkpoint processing.
— N (No) – Do not perform timestamp checkpoint
     processing.

Main Data

The primary data component.

This parameter has the following subparameters:

• Unit type – The unit type to which data should be allocated.
• Volser – Up to six volsers can be specified.

Main Index

The primary index component.

This parameter has the following subparameters:

• Unit type – The unit type to which data should be allocated.
• Volser – Up to six volsers can be specified.

Dual Data

The dual data component.

This parameter has the following subparameters:

• Unit type – The unit type to which data should be allocated.
• Volser – Up to six volsers can be specified.

Dual Index

The dual index component.

This parameter has the following subparameters:

• Unit type – The unit type to which data should be allocated.
• Volser – Up to six volsers can be specified.