Deactivating parameters

To reduce the impact on your system resources and enhance performance, you can deactivate parameters that are not commonly needed. However, before deactivating a consumer parameter, consider the results:

• The icon for the consumer parameter disappears and no data is collected or stored.
• The collector parameter that sets the deactivated consumer parameter notates the system output window with an error each time that the collector attempts to send information to the deactivated parameter.
• Some collector parameters might also set off recovery actions if they cannot find a deactivated consumer parameter.

Instead of disabling consumer parameters, consider the results that occur when you perform one of the following actions:

• Disable only the alarms for a consumer parameter.
   The collector parameter continues to send data to the consumer parameter, and the consumer parameter continues to provide a view and history for that data. However, no alarms or warnings are displayed and no recovery actions are triggered for that consumer parameter.
• Deactivate a collector parameter.
   The collector parameter stops collecting data for the consumer parameter it sets.
• Do not monitor an application class.
   No parameters are displayed for application classes that is not set up for monitoring. For information about how to set up monitoring for application classes, see Using.

 Application classes with status changes set in the code

The change_state function is called on certain application classes during the discovery process or in response to a menu command. When instances of application classes are created, most are set to an OK status except under the following conditions.

The following events, commands, and changes in status precipitate internal status changes. These changes overwrite whatever changes are made through PATROL Configuration Manager.

For DB2 UDB EE and DB2 UDB EEE

The following status changes apply to both DB2 UDB EE and DB2 UDB EEE.

For DB2 UDB EE only

The following status changes apply to DB2 UDB EE only.

Status changes for DB2 UDB EE

Condition

Status Change

database discovery

DB2_DB is set to OFFLINE during database discovery for EE if the database status is not Active as far as the DB2 DBRMS is concerned. If the database status is Active, DB2_DB is set to OK.

bufferpool discovery

DB2UDB_BUFFERPOOL is set to OFFLINE during bufferpool discovery if a SQL1611 error (no data returned, usually due to no applications connected to database) occurs.

Force Stop of Database Manager menu command

The DB2 > Database Administration > Database Modes > Force Stop of Database Manager menu command sets /DB2/ and /DB2_DB/ to OFFLINE for the instance.

Start Database Manager menu command

The DB2 > Database Administration > Database Modes > Start Database Manager menu command sets /DB2/ and /DB2_DB/ to OK for instance.

Stop Database Manager menu command

The DB2 > Database Administration > Database Modes > Stop Database Manager menu command sets /DB2/ and /DB2_DB/ to OFFLINE for instance.

The DB2 > Database Administration > Database Modes > Stop Database Manager menu command sets /DB2EEE_DB_NODE/ to OFFLINE.

For DB2 EEE only

The following status changes apply to DB2 UDB EEE only.