Starting, stopping and refreshing the DB2 for z/OS health monitor

On the z/OS^® system, the DB2^® for z/OS health monitor is started as a task for each DB2 subsystem to be monitored or on a dedicated member of a data sharing group.

To start a DB2 health monitor, issue the following START MVS™ system command:
```
   S membername,DB2SSN=ssid,JOBNAME=HMONssid,TRACE=trace,REFRESH=nn
```
TRACE and REFRESH parameters are optional.
membername

Specifies a procedure library member that is executed to start the DB2 health monitor, that is, DSNHMONP. This cataloged procedure is created by the DSNTIJHM installation job.

ssid

Specifies the name or identifier of the DB2 subsystem to be monitored.

trace
Specifies the trace flag. Possible values are:
- ON - Turn on trace. Trace records are written to SYSOUT
- OFF - Do not turn on trace
The default is OFF.
nn

Specifies the hour (using a 24-hour clock) when the health monitor refreshes the evaluation schedule snapshot it uses to trigger policy evaluations. The default is 22.
To start multiple DB2 health monitors, issue the following START MVS system command:
```
 S membername
```
membername
A procedure library member that is executed to start multiple DB2 health monitors, that is, DSNHMONA.
Note: Before starting multiple DB2 health monitors with one START command using DSNHMONA, the HMONPARM data set specified in the DSNHMONA proc must be populated with the list of subsystems to be monitored. The cataloged procedure and the data set are created by the DSNTIJHM installation job.
To refresh the policy evaluation schedule snapshot used by the DB2 health monitor to determine when to trigger policy evaluations, issue the following MODIFY MVS system command:
```
   F HMONssid,APPL=REFRESH
```
ssid

Name or identifier of the DB2 subsystem that the DB2 health monitor you're refreshing is monitoring.
To stop a DB2 health monitor, issue the following STOP MVS system command:
```
   STOP HMONssid  or P HMONssid
```
ssid

Name or identifier of the DB2 subsystem that the DB2 health monitor you're stopping is monitoring.