======================================================================
                  Halcyon PrimeAlert (R) for DB2
                          Version 1.0.0

                           Release Notes
======================================================================
Copyright (c) 2008 Halcyon Monitoring Solutions, Inc.

Note: For the latest information on this product, visit:
      http://www.HalcyonInc.com

      Refer to the README file(s) for all other information.

Versions Documented Below: 1.0.0


======================================================================
VERSION/DATE: 1.0.0/2008-01-14


ENHANCEMENTS
----------------------------------------------------------------------
- None.

BUG FIXES
----------------------------------------------------------------------
- None.

UPGRADE STRATEGY
----------------------------------------------------------------------
- None.

KNOWN PROBLEMS
----------------------------------------------------------------------
- Sun MC 3.6 and up is experiencing problems serving help files from
  the server layer. Please refer to Troubleshooting for a workaround
  to this problem.

- Row indexes of the 'Application Statistics' table contain data
  generated by DB2. These indexes may not exist after DB2 is restarted
  or when applications disconnect from DB2. Thus, alarm thresholds for
  any row in that table may be lost, and Performance Reporting Manager
  (PRM) reports using these indexes are no longer applicable.

  Additionally, Sun MC will log an error message in the agent log file
  regarding rows that no longer exist. The text of these messages is:
  'error logging event in rule rCompare : error is no such instance'.
  They do not affect functionality of the module and can be ignored.

- When adding new tablespaces to a monitored DB2 database, the table
  'Tablespaces Capacity' will display data for the new tablespaces after
  a delay of up to 10 minutes.

- Sun MC will log an error message in the agent log file regarding
  rows that no longer exist in tables 'Tablespaces Capacity' and
  'Tablespace Performance'. The text of these messages is:
  'error logging event in rule rCompare : error is no such instance'.
  They do not affect functionality of the module and can be ignored.

- The 'Diagnostic Log Monitor' node monitors the DB2 log file that is
  specified by the module load parameter 'Log File Path'. This log file
  contains messages related to all databases running in the monitored
  instance. Hence, the 'Diagnostic Log Monitor' will raise alarms for
  all databases of the monitored instance.

- The 'Diagnostic Log Monitor' reports only the first line of a multi-
  line DB2 error message.

NOTES
----------------------------------------------------------------------
- The property 'Last Reset Timestamp' in nodes 'Manager Information'
  and 'Database Instance Information' indicates the date and time the
  monitor counters were reset for the application collecting monitor
  information. Currently, PrimeAlert for DB2 does not reset these
  counters. Therefore the 'Last Reset Timestamp' will always be '-'.

- DB2 processes specifically for multi-partitioned database environments 
  are not automatically monitored. Configure the ProcessAlert submodule  
  manually to monitor these processes.

--//---