Event Monitoring Service version A.04.20.11.05, A.04.20.23.05, and A.04.20.31.05 release notes (December 2009)

In the support mode the following is applicable:
• No new EMS Monitors will be developed. Customers are encouraged to develop WBEM
provider based monitors using the SysFaultMgmt framework rather than developing EMS
monitors.
• Monitoring for new platforms will be accomplished through WBEM based monitoring only
using the SysFaultMgmt Product.
• EMS Developers Kit will no longer be shipped with HP-UX 11i v3.
For HP-UX 11i v3 you can download the latest templates from the HP Software Depot web
site at http://www.hp.com/go/softwaredepot. In the main page of the Software Depot, select
High Availability under Product Category. In the High Availability page that opens, select
Event Monitoring Service (EMS) Developer's Kit. The templates are listed in the
Developer’s Kit page. Instructions are provided with the templates. To download the
templates, click the Receive for Free button at the top or the bottom of the page. Select
HP-UX 11.23 version A.04.20 when you select the product Specifications.
For more information about EMS Future Strategy, see the 05/08 Event Monitoring Service (EMS)
Release Support Model news update available at http://www.hp.com/softwarereleases/
releases-media2/proginfo/EMS_Future_Direction_0408.pdf
Fixes in this Version
The following defects are fixed in this release:
• QXCR1000985071 – On upgrading to A.04.20.xx.04, EMS monitors core dump, many
persistence files build up.
In EMS versions A.04.20.11.04, A.04.20.23.04, and A.04.20.31.04 adding a persistence
resource monitor request causes core dump. The code is now corrected to fix this problem.
• QXCR1000974345 – msswinitconfig -r java.lang.Exception: Uninstall was incomplete.
In EMS version A.04.20.23.04, unconfigure or uninstall of MSSW is incomplete. This problem
is now fixed. The EMS-MX configure script now copies the emstools.xml file instead of
the emstools.tdeffile to /var/opt/mx/tools.
• QXCR1000932860 – rm_log_init: fopen of file /etc/opt/resmon/log/client.log
failed
When an EMS client executes with non-root privilege, it is not able to open the /etc/opt/
resmon/log/client.log file due to insufficient privileges. EMS logged an error message
in the syslog stating that the privilege is insufficient. This message is no longer logged this
release onwards.
Known Problems and Workarounds
The following are the known problems and workarounds:
• JAGaf19567 - EMS does not handle registering of persistent requests during boot time
correctly. This results in certain requests getting lost. Persistence files are set to zero if a user
tries to register the persistent requests during the boot phase.
This problem is resolved for emsgui and emscli client. However, this problem will continue
to exist for other clients.
• JAGag19389 - WBEM supports the feature of specifying the severity of an event. The severity
level can be critical, major, minor, warning, information, normal, and so on. However, when
emsgui or emscli is used to submit a wbem request, the ems client program does not allow
Fixes in this Version 13