DECamds Version 7.3-2B Release Notes Release Notes for DECamds Version 7.3-2B appear in the following sections: 1. Problems Corrected 2. Operation Notes 3. Restrictions and Workarounds in Version 7.3-2B 1 Problems Corrected The following section discusses problems corrected in Version 7.3-2B of DECamds. 1.1 Installation of Availability Manager Removes DECamds When installing the Availability Manager Data Analyzer kit on a node, you are prompted to remove prior versions of the Availability Manager. If DECamds is also installed on the node, removing the previous version of Availability Manager might cause DECamd to become inoperable. If this problem occurs, running DECamds results in the display of the following message: %DCL-W-ACTIMAGE, error activating image amds$system:amds$console -CLI-E-IMGNAME, image file AMDS$SYSTEM:[SYSEXE]AMDS$CONSOLE.EXE; -RMS-F-DEV, error in device name or inappropriate device type for operation In this situation, the workaround is to reinstall DECamds. This problem has been resolved in the Availability Manager Data Analyzer Version 2.4 kit and the DECamds Version 7.3- 2B kit. 1.2 Double-Clicking Process Name Causes ACCVIO Error On several pages that display a list of processes, double- clicking on a process at times caused an ACCVIO error instead of displaying the Single Process page. This problem has been corrected in Version 7.3-2B. 1 1.3 Hang in IVP Portion of Installation Fixed During the installation of DECamds, the execution of the IVP procedure would sometimes hang. This problem has been corrected. 2 Operation Notes The following section contains a note pertaining to the operation of the DECamds Version 7.3-2B. 2.1 Collecting Data from Disks Initialized with Dynamic Volume Expansion In collecting Disk Volume Summary data for OpenVMS Alpha Version 7.3-2 and later, DECamds uses the number of blocks from the $ SET VOLUME/SIZE command to calculate the number of blocks used in the volume summary display. 2.2 Logical LAN Support Logical LAN support was new in OpenVMS Version 7.3-2. Refer to New Features and Documentation Overview for OpenVMS Version 7.3-2 for details on logical LAN support. DECamds is compatible with this feature. You can specify the logical LAN device in the logical AMDS$DEVICE. However, if the current device name that the logical AMDS$DEVICE specifies is part of a logical LAN failover set, the device name needs to be changed. This is because specifying a physical device in a failover set is illegal and will result in an error when executing SYS$STARTUP:AMDS$STARTUP START. For a device name, you can specify either the logical LAN device for the failover set or another network device. The following figure shows a possible OpenVMS pre-Version 7.3-2 configuration. The AMDS$DEVICE logical points to EIB0:. 2 AMDS$DEVICE | V EIA0: EIB0: EWA0: If, after installing OpenVMS Version 7.3-2, you create a logical LAN failover set with EIA0: and EIB0:, the AMDS$DEVICE logical can no longer specify EIB0:, because EIB0: is now in a failover set. In this case, you must set the AMDS$DEVICE logical to either LLA0:, which is the logical LAN device, or to EWA0:. EIA0: EIB0: EWA0: \ / ---------+---------- | V LLA0: 3 Restrictions and Workarounds in Version 7.3-2B The following sections explain restrictions and workarounds that exist in DECamds Version 7.3-2B. 3.1 Workaround for eXcursion Display Problem Users have reported intermittent problems displaying the DECamds Event Log Window (in conjunction with the Overview Window) using eXcursion. It appears that if the Event Log Window is placed in certain locations, eXcursion does not display it. The icon for the window is visable, and you can maximize the Event Log Window from the icon, but the window disappears when you try to restore it. As a workaround, follow these steps: 1. Run DECamds with the display set to an OpenVMS Motif screen, and display the Overview and Event Log Windows. 2. Move the Event Log Window away from the edge of the screen and to a position and size that fit on both the OpenVMS and PC screens. 3. Exit from OpenVMS, which saves the current geometry of the windows. 3 4. Start DECamds and display the windows on a PC using eXcursion. The Event Log Window should now display correctly. (You might need to experiment a bit to find the right position for the Event Log Window.) 3.2 Kernel Threads Not Supported (Alpha Only) DECamds support for kernel threads has not been implemented on OpenVMS Alpha systems. If you use threaded processes, DECamds displays only the top thread. 4