Event Monitoring Service Version A.03.10 Release Notes

12 Chapter1

Patches and Fixes in this Version

longer need to be applied separately:

Table 1-5 lists defects have been ﬁxed in EMS A.03.10:

Table 1-4 EMS Patches Rolled into EMS A.03.10

Patch Date HP-UX Description

PHSS_18433 990708 10.20 s700 and s800 10.20 Event Monitoring

Service (EMS) English patch

PHSS_18434 990712 10.20 s700 and s800 10.20 Event Monitoring

Service (EMS) Japanese patch

PHSS_18435 990709 11.00 s700 and s800 11.00 Event Monitoring

Service (EMS) English patch

PHSS_18436 990713 11.00 s700 and s800 11.00 Event Monitoring

Service (EMS) Japanese patch

Table 1-5 Corrected Defects

SR Number Problem and Resolution

JAGab67387 Problem: resdata returns a non-zero exit code even

when it succeeds. If you use EMS with OpenView

IT/O, the status of the automatic action is reported as

Failed, even when it succeeded. The automatic

action is invoked to gather additional event data

using the resdata command. If the exit code from

resdata is non-zero, IT/O marks the result of the

automatic action as failed.

Resolution: The software was changed to ensure that

the proper exit code is always set.

JAGab69099 Problem: EMS used up an increasing number of UDP

ports. When NIS is used for name resolution, over

time, an increasing number of UDP port numbers

would be used by the persistent client (p_client).

Consequently, other UDP application might be unable

to bind to UDP ports.

Resolution: The persistence client (p_client) now

closes all ﬁle descriptors before restarting itself.