Unicenter® System Watchdog for OpenVMS I64 r2.5

9.0 Contact Technical Support

1.0 Welcome

Welcome to Unicenter System Watchdog for OpenVMS I64 r2.5. This file contains product installation considerations, operating system support, and information about contacting CA Technical Support.

2.0 Operating System Support

Unicenter System Watchdog for OpenVMS I64 r2.5 supports the following operating systems:

2.1 OpenVMS Support

• HP OpenVMS Industry Standard 64 V8.2‑1 or V8.3

2.2 Windows Support

• Microsoft Windows 2000 Professional, Server, Advanced Server, Datacenter Server with a minimum of Service Pack 3 or any later maintenance (32-bit)

• Microsoft Windows XP Professional (32-bit version only) with any later maintenance

• Microsoft Windows 2003 Standard Enterprise, Datacenter, and Small Business Server (32-bit version only) with any later maintenance

3.0 System Requirements

The following table lists the OpenVMS versions and the corresponding TCP/IP stack versions:

OpenVMS Version	TCP/IP Services
V8.2-1	V5.5
V8.3	V5.6

OpenVMS Version	TCPware
V8.2-1, V8.3	V5.7-1 or V5.7-2

OpenVMS Version	MultiNet
V8.2-1, V8.3	V5.1 or V5.2

3.1 Watchdog Agent

The OpenVMS requirements are as follows:

• To install Watchdog Agent a minimum of 132,000 blocks free disk space is required.

• To run the Watchdog Agent a minimum of 32,000 blocks free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log files collected by Watchdog Agent.

3.2 Watchdog Manager

The OpenVMS requirements are as follows:

• To install Watchdog Manager, you must have Watchdog Agent installed and running.

• To install Watchdog Manager a minimum of 225,000 blocks free disk space is required.

• To run Watchdog Manager a minimum of 70,000 blocks free disk space is required.

Disk space refers to space required for the product base files and does not take into account the requirements for log files collected by Watchdog Manager.

4.0 Installation Considerations

Use the following command to mount the DVD:

Mount/over=id device:

Note: Device is the CD‑ROM or DVD‑ROM drive.

4.1 Windows Considerations

If you are using Unicenter NSM on Windows, you need to be aware of the following situations:

• When installing Unicenter OpenVMS Integration for Unicenter NSM on a Windows server running Unicenter NSM r11, you might need to reboot the Windows server after completing the Integration installation.

• To install the CCS r11.1 package on a system that previously had CCS/NSM r11 and Ingres DB installed, you must clean up the %TEMP% directory before beginning the CCS r11.1 installation.

• Avoid installing CCS with only the WorldView component. Install the Event Management Component to eliminate any issues. 

  For more information see the section “Known Issues.”

4.2 OpenVMS Considerations

The following consideration applies only when you install on an OpenVMS system running DECnet Phase IV:

Beginning with release 2.5, both the Manager and the Agent do attempt to create the SNS$WATCHDOG account if it does not exist. When the Manager is installed first on a clean machine, installing the Agent causes the password for the SNS$WATCHDOG account to be updated to match the DECnet object. However, if you install the Agent first and then the Manager, only one modification is made to the system authorization (SYSUAF) file.

4.3 Cluster Considerations

If you install this product on multiple nodes in either a homogeneous cluster or in a heterogeneous cluster where multiple nodes boot from the same system disk, the product startup files residing on the system disk(s) are replaced. Any customizations to those files are also lost. To avoid this, save your customizations before installing the product on additional nodes that boot from any system disk where the product has already been installed. CA is considering changing this behavior in future releases.

5.0 General Considerations

This section contains general information you should know before using Unicenter System Watchdog for OpenVMS I64 r2.5.

5.1 Version Number

CA has changed their product version scheme. The official version of this release of Unicenter System Watchdog for OpenVMS is I64 r2.5. This version is the same as V2.5-0706.

5.2 Software Write Locked Events

CA recommends that you add exclusion entries for your CD-ROM and DVD-ROM devices in order to prevent unnecessary Software Write Locked (SWL) events. You can use the wildcard feature to create the exclusion entries.

5.3 Motif Interface

This software was developed on DECwindows Motif and has not been tested with all available X Windows emulators.

5.4 Startup file names

Beginning with release 2.5, the names of the startup and shutdown files are changed. The new startup file names are USW$AGENT$STARTUP.COM and USW$MANAGER$STARTUP.COM. For the convenience of users familiar with the OpenVMS Alpha/VAX environments, a file named SNS$STARTUP.COM is also provided with this release. For the convenience of users familiar with the OpenVMS Alpha/VAX environments, a file named WATCHIT$STARTUP.COM is also provided with this release.

Save your customizations to the startup file before doing a reinstall. For more information see the section "Known Issues."

6.0 Known Issues

The following items are known issues with Unicenter System Watchdog for OpenVMS I64 r2.5:

• If you reinstall this product, the startup files are overwritten and any customizations you created are lost. To avoid this, save your customizations to the startup file before doing a reinstall. CA is considering changing this behavior in future releases.

• In the Motif Profile Editor, toggle buttons in the following windows do not display the default setting:

  • Add, Node, Disk Free Space, Threshold. The default setting “Percent” should be set.

  • Add, Node, Shadow Sets, Merge Copy Messages. The default setting “Off” should be set.

  • Add, Node, Shadow Sets, Full Copy Messages. The default setting “On” should be set.

• The Agent Installation does not display the value of the system logical SNS$CLUSTER_NAME if it is defined on the node. If the system logical SYS$CLUSTER_NODE is not defined, the installation prompts for a value for SNS$CLUSTER_NAME, saying “<Return> for none”, but does not provide a default value. If a value was previously set and you press Return (or Enter), the value remains unchanged.

• If you exit the SHOW EVENTS/CONTINUOUS display during a poll, and then restart the display, you could encounter a corruption. If this occurs, exit the corrupted display while it is waiting for the next poll, and then restart the display.

• When using Apply from the Motif Profile Editor, if you delete an entry from a profile, that entry is deleted but the entry name remains in the Selection box. The following entries are affected:

  • Node

  • Class

  • External Message Class

  • Action Routine Set

  • DECtalk Set

  • Mailbox Set

• When installing Remote Admin Client with the CCS r11 WorldView component only (without Event Management), the subsequent uninstall fails to remove CCS components, returning the error:

  Internal Error:function TNGSetProductContext was passed invalid parameter(s).
  

  Contact CA Customer Support for the latest CCS Event Management / CCS Installation patches.

• The SHOW MESSAGE, Description section (Chapter 3, page 97) of The Administrator Guide contains the following text:

  The SHOW MESSAGE command resets the hidden status of all messages that contain “name message text.” For example, if the hidden message is “12-OCT 03:45 NODEA unreachable,” the SHOW MESSAGE command parameter must be “NODEA unreachable.”

  The text should read as follows:

  The SHOW MESSAGE command makes visible all messages that contain "message text" which are from cluster or node "node_name". For example, the following command makes visible all messages from NODEA that contain the word QUEUE:

  SENSE WATCHDOGS SHOW MESSAGE "NODEA QUEUE"
  

• Under certain conditions, you might experience an error in the Motif Profile Editor File Open dialog box. If you do not specify the file name extension when manually entering a file name in the selection field, you might experience the following error:

  raised CONSTRAINT_ERROR : sns$profile_mgt.ada:169 length check failed
  

  To avoid this error, select the name from the box listing the file names.  Alternately, enter the complete file name, including the .DAT file extension.

7.0 Published Fixes

The complete list of published bug fixes for this product can be found through Published Solutions at: http://supportconnect.ca.com/

The following fixes and behavioral changes are included in this service pack. Where applicable, the published PTF number is specified before the description of the fix:

PTF Number	Description
QO81583	Sometimes a folder name is created in lower case.
QO83553	Nomsg error/accvio messages in agent logfile
QO83554	Can't start consolidator with alternate UIC.
QO78267	Link error during installation.
QI84865	CA licensing for OpenVMS.

8.0 Documentation

Updated guides for this product are available at http://ca.com/support.

The PDF guides for this product are as follows:

• Unicenter System Watchdog for OpenVMS I64 Installation Guide

• Unicenter System Watchdog for OpenVMS I64 Administrator Guide

• Unicenter System Watchdog for OpenVMS I64 Release Summary

• CA Common Services for OpenVMS Integration Guide

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

8.1 Release Numbers on Documentation

The release number on the title page of a document might not correspond to the current product release number; however, all documentation delivered with the product, regardless of release number on the title page, will support your use of the current product release. The release number changes only when a significant portion of a document changes to support a new or updated product release. If no substantive changes are made to a document, the release number does not change. For example, a document for r11 may still be valid for r11.1 or even r12. Documentation bookshelves always reflect the current product release number.

Occasionally, we must update documentation outside of a new or updated release. To indicate a minor change to the documentation that does not invalidate it for any releases that it supports, we update the edition number on the cover page. First editions do not have an edition number.

9.0 Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.