• Continuously collects a configurable set of information on server health, configuration, environment

Runs continuously in the background collecting info for 10/20/60 minute intervals
Archives this information in the database
Negligible performance hit  - could turn off with dsmserv.opt “alwaysonservermon=no”

• If the server encounters any problems

Easy for the customer to retrieve information 
Information already exists about the server's status at the time of the problem (and perhaps before) 
Can send in to IBM support

* Simply runs in the background  

Collections stored temporarily in srvmon directory which is a staging area
Compressed and consolidated as archiveFile-[date].zip
Stored in SERVERMON_ARCHIVES table in the SP db
servermon executable automatically prunes archives from database
dailyretention (number of daily collections to keep default 90 days)
weeklyretention (number of additional collections one/week to keep default 30 weeks)

servermon:  will run servermon until interrupted
servermon –debug: will run the servermon with enhanced logging
servermon –list: will list archives of data that have been stored in Db2 by servermon
servermon –remove -id <ID>: will delete a stored archive based on the provided ID
servermon –extract –id <ID>: will extract an archive from Db2 and leave it in the srvmon directory as a date stamped zip file that can be extracted for analysis
servermon –prune: will remove archives from Db2 that are determined to be no longer necessary by configurable options (this occurs automatically once per day during normal servermon execution)