Event Monitoring Service Version A.04.10 Release Notes

Event Monitoring Service Version A.04.10 Release Notes
Patches and Fixes in this Version
Chapter 1 17
Patches and Fixes in this Version
Required and Recommended Patches
The contents of EMS A.03.20.01, A.03.40 and A.04.00.01 has been incorporated into A.04.10
release.
Fixes and Changes
The following defects have been fixed in EMS version A.04.10:
JAGaf19567
Problem: When an attempt is made to register persistent requests during the boot phase, the
contents of the persistence file is deleted.
Resolution: A client API is_ems_ready() is added to check the status of persistence client
activity on the system after reboot. The persistence client calls this API before registering,
unregistering, or modifying a request.
JAGae94047
Problem: The emscli(1M) command with the -g option generates incorrect scripts for text log
and syslog notification options.
Resolution: The emscli(1M) command has been fixed to generate the script correctly.
JAGae94058
Problem: The emscli(1M) command does not set the default threshold value for enumerated
resource instances.
Resolution: The emscli(1M) command has now been fixed to set the default threshold value
and register the request for enumerated resource instances.
JAGae82761
Problem: EMS notifications for resources of type, RM_FLOAT64_TYPE are reported in different
format for syslog and SNMP/OPC.
Resolution: EMS code has been modified to display SNMP/OPC and syslog notifications in
decimal notation for resources of type, RM_FLOAT64_TYPE.