Near-term history data collection options

This topic provides an overview of the near-term history data collection options member of RKD2PAR.

Related parameters

For more information about the KD2_PFnn_HIS parameters that control the history behavior in your environment, refer to 'KD2_PFnn_HIS - History' in the Parameter Reference.

For more information about the KD2_PFnn_THRDHIS parameters that control the thread history behavior in your environment, refer to 'KD2_PFnn_THRDHIS - Thread history' in the Parameter Reference.

Options

Data collection options determine the behavior of a Near-Term History Data Collector and the amount of data being collected.

For each Near-Term History Data Collector, a data set member rHilev.RKD2PAR(COPTcccc) where cccc specifies the Db2 subsystem identifier) is generated that holds the data collection options. Collection options members for specific Db2 subsystems can be created and invoked at startup of a Near-Term History Data Collector. Collection options in a COPTcccc data set member are specified by keywords and associated keyword values. Basically, keywords and values specify and limit the data to be collected by the Near-Term History Data Collector.

Generally, configurations you make to near-term history parameters generate collection options members. Nevertheless, a collection options member for a specific Db2 subsystem can also be created by copying an existing collection options member or the default member rhilev.RKD2PAR(COPTcccc) and modifying the collection options in the copied member. Before you do this, ensure that you make backups of the member as configurations you make might overwrite existing members.

COPTcccc Keyword syntax and considerations

Keywords in a collection options member are used in the following ways:
  • Keyword(value)
  • Keyword(value,value,…)
  • Keyword(value␣value␣…)

If a keyword accepts only one value, enter the value in parentheses after the keyword. If a keyword accepts multiple values, enter the values in parentheses after the keyword and separate the values by commas or spaces.

The NOT operator (¬) negates value specifications. For example, CONNID(¬IM3D,¬I210) specifies that the Near-Term History Data Collector should collect data about all connection identifiers except for IM3D and I210.

The asterisk (*) wildcard character can be used at the end of value specifications. For example, PLAN(ABCD*) specifies that the Near-Term History Data Collector should collect data about all plans with names that begin with ABCD.

The question mark (?) wildcard character can be used as a single character replacement within value specifications. For example, DB2ID(D??T) specifies that the Near-Term History Data Collector should collect data about all Db2 subsystems with names that begin with D, followed by two variable characters, and end with T.

If you must continue statements in an COPTcccc member on another line for keywords such as AUTHID, CONNID, CORRID, ORIGAUTH, or PLAN:
  • Do not use a continuation character. This means, do not repeat a Keyword( entry on the next line.
  • Do no start the continuation line in column 1. Only keywords should begin in column 1, as in the following example:
PLAN(¬DSNG* ¬DSNTI* ¬FINAN1 ¬FINAN2 ¬DSNG*
␣¬DSNZZ ¬FINAN3 ¬FINAN4 ¬DSNR* ¬DSNRR*
␣¬FINAN5 ¬FINAN6)