OpenVMS Management Station Release Notes for OpenVMS Revision/Update Information: Version 3.3 Hewlett-Packard Company CONTENTS 1. Introduction 2. Known Problems and Restrictions 2.1 Only Cluster-Unique Devices Managed 2.2 Bound Volumes Limited in Number of Members 2.3 Privately Mounted and Foreign Volumes not Managed 2.4 Files Created After Error is Logged 2.5 Write-Locked Shadow Sets not Supported 2.6 Clicking Stop to Interrupt an Operation 2.7 Server Busy Message 2.8 Setting the DMA Attribute 2.9 DECnet Phase IV Database and Proxies Issue 2.10 Renaming Users Resets New Mail Count 2.11 Manually Editing the UIC Group Number 2.12 TCPware Print Symbiont Limitation 2.13 Printer Rename Fails for Reconciled Printers with DQS Queues 2.14 Duplicate Queue Names on Create 2.15 Destination Field not Shown 2.16 PWDMIX Flag for User Accounts 2.17 Installation on OVMS 7.2 and later Versions 2.18 OMS Server and Client Version 2.19 Microsoft Management Console Version 3. Problems Fixed in Version 3.3 3.1 Support for External Authentication Flag 3.2 Owner Field Not Updated in OMS Client 3.3 Broken Links in Help Files 4. Notes 5. Trademarks 1. Introduction This file contains important information regarding the OpenVMS Management Station software that is not described in the installation guide or in online help. Read this file before you begin using OpenVMS Management Station. Version 3.3 of OpenVMS Management Station is a 32-bit application and is compatible with the management domains created with Version 3.0 or later of OpenVMS Management Station. If you are running a version of OpenVMS Management Station prior to Version 3.0, you must recreate OpenVMS Management Domains for use with Versions 3.0 or later. 2. Known Problems and Restrictions This section details known problems and restrictions in the OpenVMS Management Station software. 2.1 Only Cluster-Unique Devices Managed This release of OpenVMS Management Station manages and displays only disks that are visible to all nodes in a cluster. This means that you will not be able to display or manage public volumes mounted on "unmanaged" devices, such as an infoserver device. It also means that OpenVMS Management Station does not manage SCSI disks connected to VAX systems. 2.2 Bound Volumes Limited in Number of Members OpenVMS Management Station can manage bound volumes with these restrictions: - If every member volume is a shadow unit with one member, the maximum number of member volumes is 28. - If every member volume is a non-shadowed disk, the maximum number of member volumes is 42. 2.3 Privately Mounted and Foreign Volumes not Managed OpenVMS Management Station handles privately mounted and foreign volumes as special cases and does not display or manage them. 2.4 Files Created After Error is Logged When the OpenVMS Management Station server is first installed on a system, the TNT$SERVER_ERROR.LOG error log contains errors that indicate that the TNT$ACS.DAT and journal files could not be found. These files are, in fact, created immediately after the errors are logged. You can ignore the errors. 2.5 Write-Locked Shadow Sets not Supported This version of OpenVMS Management Station does not support write-locked shadow sets. 2.6 Clicking Stop to Interrupt an Operation Expanding an OpenVMS Storage object occasionally results in a "Retrieving information from the server..." message window being displayed. If you click the Stop button while this message is displayed, the following error might be reported: TNT-F-Writelock Locked against write access. SYSTEM-W-NOT QUEUED, Request not queued To work around this problem, select that same OpenVMS Storage Object and hold down the F5 key to refresh or click Refresh from the Action menu. 2.7 Server Busy Message If the OpenVMS Management Station server returns a "busy, try again later" message, it means that multiple clients are using the server at the same time. Retry the operation. 2.8 Setting the DMA Attribute If you set the direct memory access (DMA) attribute for a terminal device (TT or LAT) that does not support DMA, the device ignores the DMA setting. However, OpenVMS Management Station considers the DMA control to be set. If DMA support is later added for the device, you must clear the DMA attribute and then reset it in order to enable DMA support on the physical device. You cannot just set DMA again because the OpenVMS Management Station believes it is already set and will not set it again until it is first cleared. 2.9 DECnet Phase IV Database and Proxies Issue OpenVMS Management Station does not update the DECnet Phase IV NETPROXY.DAT file. If you add a proxy using OpenVMS Management Station, applications such as DFS (prior to Version 2.0) and DECnet Phase IV (components such as file access listener (FAL)) that read the Phase IV database do not see the proxy. Use AUTHORIZE to add a proxy if you require access by DFS (prior to Version 2.0) and DECnet Phase IV components such as FAL. 2.10 Renaming Users Resets New Mail Count If you rename a user account that has unread new mail messages, the new mail count for the renamed account is set to zero. However, the user can use the READ/NEW command to read the new mail messages. 2.11 Manually Editing the UIC Group Number If you manually edit the UIC Group control on the Advanced UIC dialog box, the Next Available Member and Next Highest Member controls are not updated. If you select an existing group from the list,the Next Available Member and Next Highest Member controls are properly updated. Please see the online help for more information. 2.12 TCPware Print Symbiont Limitation Queues that are based upon TCPware's print symbiont TCPWARE_TSSYM cannot be made autostartable. As such, this type of queue cannot be used as the reference printer during a Create Printer operation. 2.13 Printer Rename Fails for Reconciled Printers with DQS Queues If you rename a printer at the OpenVMS Management Domain level, and the printer you select is a reconciled printer with two or more DQS queues from the same node, the rename operation fails to rename all reconciled printers. 2.14 Duplicate Queue Names on Create When creating a printer at the OpenVMS Management Domain level based on a reference printer accessed using DQS, the queue-naming algorithm sometimes generates duplicate queue names. To work around this problem, check the queue names and use the Rename control to correct any duplicates. 2.15 Destination Field not Shown When viewing the devices for a printer made up of DQS and unknown (other) devices, the Destination Node field is not shown for the DQS device. 2.16 PWDMIX Flag for User Accounts OpenVMS Management Station (OMS) does not support the OpenVMS Version 7.3-2 feature for mixed case password. Refer to OpenVMS Version 7.3-2 documentation for more information on the PWDMIX flag for user accounts. 2.17 Installation on OVMS 7.2 and later Versions OpenVMS Management Station (OMS) is a part of OVMS operating system (Version 7.2 and later). While installing OpenVMS Management Station on these operating systems, the files supplied by VMS may be replaced by the new files of the OpenVMS Management Station kit. Under such circumstances, as there are some problems in the PCSI database, the TNT objects will have two entries with the same name, one provided by VMS and other by OpenVMS Management Station kit. The corresponding files will be replaced in the TNT objects while installing OMS and will have the status "Conflict". If OpenVMS Management Station is uninstalled, the PCSI database reassigns ownership of those files back to VMS, which will have the status OK. The PRODUCT SHOW OBJECT *TNT* /FULL command will not show any conflicts now, but the files retained will be that of OMS Kit and not the ones which were supplied with the OS. 2.18 OMS Server and Client Version OMS V3.3 Client must be used with OMS Server V3.3 version. Using OMS Client V3.3 with versions prior to OMS V3.3 Server may result in unexpected behavior. 2.19 Microsoft Management Console Version OMS V3.3 client uses Microsoft Management Console (MMC) version 1.2. If the Console setting is saved using OMS Client V3.3 version, you will no longer be able to use this file with earlier versions of OMS Client that uses MMC version 1.1. 3. Problems Fixed in Version 3.3 3.1 Support for External Authentication Flag For a given account, you can modify the External Authentication Flag from OpenVMS Management Station. 3.2 Owner Field Not Updated in OMS Client The owner field of an existing account is not updated in OMS Client if the owner field is modified or updated from the UAF prompt. This behavior is rectified in the current release. 3.3 Broken Links in Help Files Clicking on some of the online help links of the OpenVMS Management Station client, displays the following error: "The topic doesn't exist. Contact your application vendor for updated help file.129". All the broken links are fixed in this release. 4. Notes - Filtering Users by Rights Identifier The time needed to filter users by their rights identifiers is directly proportional to the number of users and rights identifiers on the system. 5. Trademarks © Copyright 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Intel is a trademark of Intel Corporation in the U.S. and other countries and is used under license. Java(tm) is a US trademark of Sun Microsystems, Inc. Oracle® is a US registered trademark of Oracle Corporation, Redwood City, California. OSF and Motif are trademarks of The Open Group in the US and other countries. UNIX® is a registered trademark of The Open Group. Microsoft®, Windows®, Windows NT®, and MS Windows® are US registered trademarks of Microsoft Corporation. X/Open® is a registered trademark, and the X device is a trademark of X/Open Company Ltd. in the UK and other countries.