Subtask commands to the Near-Term History Data Collector

You can issue specific subtask commands to the Near-Term History Data Collector subtask (H2WLMGR). The subtask commands must be preceded by the MODIFY command of the OMEGAMON® Collector.

Specific subtask commands are:

START command

The START command starts the Near-Term History Data Collector.

F cccccccc,S H2WLMGR,OPTION=COPTxxxx
where
  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • xxxx is the name of the Db2 subsystem that the Near-Term History Data Collector monitors

STOP command

The STOP command stops the Near-Term History Data Collector.

F cccccccc,STOP H2xxxx
where
  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • xxxx is the name of the Db2 subsystem that the Near-Term History Data Collector monitors

LISTH2DS command

Lists the Virtual Storage Access Method (VSAM) data sets for history data that are defined in the collections options member. It also displays the status of each data set and the amount of space used.

F cccccccc,F H2cccc,LISTH2DS
where:
  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • cccc is the ID of the Db2 subsystem from which data is collected

This example shows system output for the LISTH2DS command:

O20561     H2 DATA SET         STATUS     %FULL
O20561     IBM.DB2P.VSAM01     AVAIL      20.1
           IBM.DB2P.VSAM02     AVAIL      20.1
           IBM.DB2P.VSAM03     ACTIVE     25.5

SWITCH command

The Near-Term History Data Collector can switch and archive data sets automatically when the data set is full. The SWITCH command allows you to perform this operation manually whenever you want.

Requirement: Before you use this command, check the availability of your VSAM data sets by using the LISTH2DS command. Data is saved only for available data sets.

F cccccccc,F H2cccc,SWITCH
where
  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • cccc is the ID of the Db2 subsystem from which data is collected

VARY command

Changes the collection specifications when the Near-Term History Data Collector is active.

F cccccccc,F H2cccc,VARY OPTION=COPTxxxx
where
  • cccccccc is the started task name that you specify for the OMEGAMON Collector during the configuration within the Configuration Tool
  • cccc is the ID of the Db2 subsystem from which data is collected
  • xxxx is the name of the Db2 subsystem that the Near-Term History Data Collector monitors

Use the Configuration Tool to specify the operational behavior of a Near-Term History Data Collector. For each Near-Term History Data Collector the Configuration Tool generates a data set member COPTcccc (where cccc specifies the Db2 subsystem identifier) 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, the Configuration Tool should be used to 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.

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)

The new collection specifications take effect after the current collection interval expires.