ServiceGuard Manager Version A.03.00 Release Notes, Second Edition, June 2003

ServiceGuard Manager Version A.03.00 Release Notes, Second Edition
Patches and Fixes in this Version
Chapter 1 45
• What is the workaround? There is no workaround. Message fixed in
ServiceGuard Manager A.03.00.01, but not in A.03.00.
JAGae50883 - Event Browser Time/Date sort does not work
correctly (Fixed in A.03.00.01)
• What is the problem? More recent events were found in the middle of
the table, not at the top or bottom.
• What is the workaround? There is no workaround. Fixed in
ServiceGuard Manager A.03.00.01, but not in A.03.00.
JAGae50948 Event Browser reports “HA Cluster Node Joined
Cluster” when it should report “HA Cluster Node Up.” (Fixed in
A.03.00.01)
• What is the problem? In A.03.00, incorrect message appears in Event
Browser. Fixed in A.03.00.01.
• What is the workaround? Remember to substitute correct message.
To be sure you have correct status, check the node’s Properties.
JAGae50816 “Java Webstart not installed” message displayed
when using Netscape.
• What is the problem? The problems occurs when using Service
Control Manager 3.0 to launch ServiceGuard Manager for Netscape
6.0 or later. You see a message saying that Java Webstart 1.2 is not
installed, even when it is installed.
• What is the workaround? ServiceGuard Manager has incorporated a
workaround that willalert the user to the problem andoffer a chance
to continue launching ServiceGuard Manager.
JAGae50813 Cannot launch ServiceGuard Manager 3.00 from
Service Control Manager 3.0
• What is the problem? When launching ServiceGuard Manager from
Service Control Manager, SCM searches the client system for version
1.2 of Java Webstart. If it does not find it on the system, it directs you
to install it. However, at the time of writing this document, Webstart
1.2 is not available on HP-UX.