RELEASE NOTES 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. NOT COMPATIBLE WITH PRIOR VERSIONS Version 3.0 of OpenVMS Management Station is a 32-bit application and is not compatible with the management domains created with any prior version of OpenVMS Management Station. You must recreate your OpenVMS Management Domain for use with Version 3.0. EXTERNAL AUTHENTICATION OpenVMS Version 7.1 allows users to log in using an account and password maintained by an external authentication agent such as a Primary Domain Controller in a LANman domain. To use this functionality, you need to use the AUTHORIZE qualifier /FLAGS=EXTAUTH with the ADD, COPY, MODIFY and RENAME commands. If this flag is set but a matching account does not exist in the external authenticator, the user cannot log in, even if there is a matching account in the OpenVMS UAF file. OpenVMS Management Station does not yet display or control this flag. However, it does propagate the flag when creating, modifying, or renaming accounts. For example, when you create an account, the flag is set however it is set in the reference account. When you create or rename an account and the EXTAUTH flag is set, the following warning is issued: TNT-W-EXTAUTH, Newly created or renamed account is externally authenticated. Make sure a corresponding account exists in the external domain. This is a reminder that an account that matches the new OpenVMS account name must exist in the external authenticator's security domain in order for the login to succeed. External authentication can be disabled by the AUTHORIZE command MODIFY account /FLAGS=NOEXTAUTH. LAUNCHING StorageWorks Command Console If you have the StorageWorks Command Console software installed on your PC, you can launch it from OpenVMS Management Station by right-clicking on a disk device and selecting the Launch SWCC menu entry. 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. KNOWN PROBLEMS AND RESTRICTIONS This section details known problems and restrictions in the OpenVMS Management Station software. 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. 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. 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. 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. WRITE-LOCKED SHADOW SETS NOT SUPPORTED This version of OpenVMS Management Station does not support write-locked shadow sets. 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 refresh the display by either using the F5 key or by choosing Refresh from the Action menu. SERVER BUSY MESSAGE If the OpenVMS Management Station server returns a "busy, try again later" message, it usually means that multiple clients are using the server at the same time. Retry the operation. 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. 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. 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. 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. 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. 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. 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. 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.