Skip to Content

History File Specification dialog fields

The following figure shows an example of the History File Specification dialog:

Related topic

Creating-task-performance-detail-history-file-definitions


History File Specification dialog
-------------- BMC AMI OpsM for CICS History File Specification --------------
COMMAND ===>                                              SCROLL ===> CSR

Targets
 ..(1).. BCVCB73*,BCVCB72*
 ..(2)..
 ..(3)..
 ..(4)..

 Target Type CICS

Dataset I
 DSName      BCVM.&CMRTARG..V&CMRREL..CMRDETL
 DDName

Dataset II
 DSName
 DDName

Dataset Options
 DSN Count   5
 Continue    YES
 Stop        NO
 Archive JCL NONE
 Create      YES

Dataspace Options
 DataSpace   NO
 DSP Size
 DSP Minutes 10


NEXT to set allocation values
END to exit saving changes
CANCEL to exit without saving changes
HELP to view related help
RESET to reset to initial data
VERIFY Verify how CMRDETL will work 

The following table describes the fields on the History File Specification dialog.

Field name

Description

Targets

The four 62-byte areas contain target specifications for the definition. The four areas are considered to be contiguous and all spaces are collapsed.

Target names are separated by commas and can contain wildcards. Valid wildcard characters are as follows:

  • Plus sign (+) represents a single character
  • An asterisk (*) represents multiple characters (including no characters)

When using single-character replacement, the target name can contain any character at the position of the wildcard. Non-wildcard characters in positions prior to or after the + wildcard must match exactly. The target must contain a character at the wildcard location. Multiple + wildcards can be used, and be contiguously specified.

Information
Example

Examples are AB+CD, AB++C+D, and ABCD+.

Multiple character replacement, designated by the asterisk, *, means that any number of characters (or none) can exist starting at the position of the wildcard. Characters preceding the * wildcard must match exactly. All characters are accepted until the next non-wildcard character is matched or the end of the field is reached. Multiple * wildcards can be used in the target name.

Information
Example

Examples are AB*, AB*CD and AB*CD*.

The two wildcards can be combined in a single template, such as AB++D*, AB*D+E and A*B+C*D.

Target Type

This field indicates what type of system will use this definition. Valid values are:

  • CICS indicates that this definition will be used for CICS Transaction Server tasks.

  • CTG indicates that this definition will be used for CICS Transaction Gateway tasks.


Dataset I DSName

Identifies the data set name to be used when allocating the primary history file. It is important to ensure that the data set names are unique for each target CICS region. The names can be completely qualified or contain system variables. See System-symbols.

The data set is allocated with a disposition of SHR. The data set must not be protected by VSAM password protection. IBM RACF or equivalent security can be used as long as the BBI-SS PAS has write access to the data set.

When the DSN Count value is less than 3, BMC AMI Ops Monitor for CICS maintains regular processing of dual CMRDETL files using the fully qualified data set names that you entered in the Dataset I and Dataset II fields. BMC AMI OpsM for CICS provides this processing to support earlier installations.

When the DSN Count value is 3 or greater, BMC AMI OpsM for CICS uses the name you entered in the Dataset I field as the hlq variable for the individual files with a suffix of .Dnn (01-10). BMC AMI OpsM for CICS ignores any value you might specify in the Dataset I DDNAME field. When Dataset Options: Create is set to YES, BMC AMI OpsM for CICS uses the values (Primary Records, VSAM Volume and the SMS classes) related to Dataset I.   BMC AMI OpsM for CICS ignores all setting for Dataset II.  

Dataset I DDNAME

If you specify values for DSName and DDNAME, these values are used as names for dynamic allocation.

BMC AMI OpsM for CICS ignores this parameter when the value in the DSN Count field is more than 2.

Dataset II DSName

Identifies the data set name to be used when allocating the secondary history file. It is important to ensure that the data set names are unique for each target CICS region. The names can be completely qualified or contain system variables. See System-symbols.

The data set is allocated with a disposition of SHR. The data set must not be protected by VSAM password protection. RACF or equivalent security can be used as long as the BBI-SS PAS has write access to the data set.

When the DSN Count value is less than 3, BMC AMI OpsM for CICS maintains regular processing of dual CMRDETL files using the fully qualified data set names that you entered in the Dataset I and Dataset II fields. BMC maintained this processing for compatibility with existing installations.

When the DSN Count value is 3 or greater, BMC AMI OpsM for CICS ignores all of the attributes you entered for the Dataset II fields (DSName, DDName, and the file attributes), and uses the values specified for Dataset I.

Dataset II DDNAME

This field identifies the DDNAME of a DD statement specified in the BBI-SS PAS startup JCL to be used for the secondary history file. If both DSName and DDNAME are used, BMC AMI OpsM for CICS uses this name for dynamic allocation.

Data set Options: DSN Count

Contains the number of BMC AMI OpsM for CICS Task Performance Detail History File data sets that are used to record CMRDETL data. The default value is 2 and the maximum value is 10.

When the value is 2, BMC AMI OpsM for CICS maintains regular processing of dual CMRDETL files using the fully qualified data set names that you entered in the Dataset I and Dataset II fields. BMC maintained this processing for compatibility with existing installations.

When the value is 3 or greater, BMC AMI OpsM for CICS uses the name you entered in the Dataset I field as the hlq variable for the individual files with a suffix of .Dnn (01-10). BMC AMI OpsM for CICS ignores any value you might specify in the Dataset I DDNAME field. When Dataset Options: Create is set to YES, BMC AMI OpsM for CICS uses the values (Primary Records, VSAM Volume and the SMS classes) related to Dataset I. BMC AMI OpsM for CICS ignores all settings for Dataset II.

Dataset Options: Continue

This field specifies whether data collection should resume on the history file that was active when recording stopped. Valid values are as follows:

  • YES specifies that this value specifies that recording begins in the history file that was active when data collection stopped. An archive request is submitted when the data set becomes full. This option is the default.

  • NO specifies that this value specifies that recording begins in the history file that was inactive when data collection stopped. An archive request is submitted when the data set becomes full, when data collection stops, or when the BBI_SS PAS terminates normally.

Dual-data-sets-with-CONTINUE-YES-STOP-NO-and-ARCHIVE-NONE gives an example of how the Continue option controls history file recording.

Dataset Options: Stop

This field specifies whether data collection should stop when a data set switch occurs and the target data set contains data that has not been archived nor is being archived (the archive in progress flag is not on). Valid values are as follows:

  • YES terminates recording to the history file. Data collection must be stopped and restarted to reactivate data recording. This option is the default.

  • NO specifies that recording is to continue. If unarchived records are detected on the switched data set, an FT224 message is issued to warn that existing records are being overwritten.

Dataset Options: Archive JCL

This field specifies the name of the started task that requests an archive of the history file. Valid values are as follows:

  • CMRDJCL: This value is the default name of the archive PROC. If no value is specified, when a switch occurs, this name will be used to request archiving.

  • archjcl: This value can be any valid started task name.

  • NONE: This value specifies that an archive request should not be submitted when a data set becomes full. NONE can be used when an automation product submits an archive request in response to messages, or when data archiving is not required.

Dataset Options: Create

This field specifies whether the history file should be created if it does not exist when data collection starts. See Automatic-creation-of-CMRDETL-data-sets. Valid values are as follows:

  • NO specifies that the history file should not be created. This option is the default.
  • YES specifies that the history file should be created.

Data space Options: Data space

This field specifies whether the T6E records should be temporarily saved in a data space rather than recorded to a data set. See Using-a-history-data-space. Valid values are as follows:

  • NO specifies that a data space should not be used to hold T6E records. This option is the default.
  • YES specifies that a data space should be used to hold T6E records.

Data space Options: DSP Size

This field specifies the size, in megabytes, of the data space that is used to hold T6E records. If no value is specified, the default is 1 MB. The maximum is 100 MB

Data space Options: DSP minutes

This field specifies the maximum number of minutes worth of T6E records that will be kept in a data space maintained for that purpose. The valid range of values for this field are from 0 (no time limit) to 1440 (24 hours). If a value is not specified (or a value of 0 is specified), records will be kept in the data space until it is filled.

 

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

BMC AMI Ops Monitor for CICS 7.4