OpenVMS Management Station
Overview and Release Notes

Order Number: AA-QJGCE-TE

June 2002

This documentprovides an overview of OpenVMS Management Station and describes how to getstarted using the software.  Thisdocument also includes release notes for OpenVMS Management Station.

Revision/UpdateInformation:     This manual supersedes the OpenVMS Management Station Overview andRelease Notes, Version 3.0.

SoftwareVersion:                       OpenVMSManagement Station Version 3.2

OperatingSystem:                      OpenVMS AlphaVersion 7.3-1
OpenVMS VAX Version 7.3

Compaq ComputerCorporation
Houston, Texas

©2002 Compaq Information Technologies Group, L.P.

Compaq, the Compaq logo, Alpha,InfoServer, OpenVMS, Tru64, VAX, VMS, and the DIGITAL logo  are trademarks of Compaq InformationTechnologies Group, L.P. in the U.S.and/or other countries.

Microsoft, MS-DOS, Visual C++,Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S.and/or other countries.

All other product names mentionedherein may  betrademarks of their respective companies.

Confidentialcomputer software. Valid license from Compaq required for possession,use or copying. Consistent with FAR 12.211 and 12.212, Commercial ComputerSoftware, Computer Software Documentation, and Technical Data for CommercialItems are licensed to the U.S. Government under vendor’s standard commerciallicense.

Compaq shall not be liable fortechnical or editorial errors or omissions contained herein. The information inthis document is provided “as is” without warranty of any kind and is subjectto change without notice. The warranties for Compaq products are set forth inthe express limited warranty statements accompanying such products. Nothingherein should be construed as constituting an additional warranty/

The Compaq OpenVMS documentation set is available on CD-ROM.

Preface

Overview.. 1

What IsOpenVMS Management Station?. 1

StorageManagement 2

PrinterManagement 3

AccountManagement 4

WhatIs an OpenVMS Management Domain?. 4

HowAre Systems in the Domain Organized?. 4

Whatis the Scope of an Operation?. 5

AvoidSurprises. 6

Choosinga Transport 6

OtherFeatures. 6

AreThere Restrictions on the Systems in an OpenVMS Management Domain?  7

How to Get Started. 9

BeforeYou Begin. 9

Whereto Find Information. 9

GettingStarted. 9

NextSteps. 16

StorageManagement Operations. 16

PrinterManagement Operations. 16

AccountManagement Operations. 17

Release Notes. 19

SupportedPlatforms. 19

Compatibilitywith Previous Versions. 19

SupportedConfigurations. 20

ImportantNotes. 20

KnownProblems and Restrictions. 20

OnlyCluster-Unique Devices Managed. 20

BoundVolumes Limited in Number of Members. 21

PrivatelyMounted and Foreign Volumes Not Managed. 21

FilesCreated After Error Is Logged. 21

Write-LockedShadow Sets Not Supported. 21

ClickingStop to Interrupt an Operation. 21

ServerBusy Message. 21

Settingthe DMA Attribute. 21

DECnetPhase IV Database and Proxies Issue. 22

RenamingUsers Resets New Mail Count 22

ManuallyEditing the UIC Group Number 22

TCPwarePrint Symbiont Limitation. 22

PrinterRename Fails for Reconciled Printers with DQS Queues. 22

DuplicateQueue Names on Create. 22

DestinationField Not Shown. 22

Installationon OpenVMS Version 7.2 and Later 22

ProblemsFixed in Version 3.2. 23

BadMagic Number Problem.. 23

Floodingof Monitoring Events. 23

IncorrectUpdating of Mount/Dismount Status. 23

ServerFailure. 23

ProblemRecognizing Fibre Channel Disk Devices. 23

ServerLooping. 23

PrimaryServer Selection. 23

ServerHangs on OpenVMS Version 7.3. 24

AdditionalNotes. 24

ExternalAuthentication. 24

FilteringUsers by Rights Identifier 24

Figures

Figure1  Volume Properties Dialog Box……………………2

Figure 2  Example ofan OpenVMS Management Domain…4

Intended Audience

This document is intended for systemmanagers, operators, and others who want to use OpenVMS Management Station tomanage user accounts, printers, and storage.

Document Structure

This document is divided into thefollowing chapters:

      Chapter 1 provides an overview of OpenVMSManagement Station and introduces new features for Version 3.2.

      Chapter 2 describes how to get startedusing the OpenVMS Management Station software. 

      Chapter 3 provides the release notes thatyou should read before you start to use OpenVMS Management Station.

Reader's Comments

Compaq welcomes your comments onthis manual.  Please send comments toeither of the following addresses:

Internet                             openvmsdoc@compaq.com

Mail                                   CompaqComputer Corporation

OSSG DocumentationGroup, ZKO3-4/U08

110 Spit Brook Rd.

Nashua, NH 03062-2698

How ToOrder Additional Documentation

Visit the following World Wide Web addressfor information about how to order additional documentation:

http://www.openvms.compaq.com/

1

What IsOpenVMS Management Station?

OpenVMS ManagementStation is a powerful Microsoft Windows based management tool for systemmanagers and others who perform management tasks on OpenVMS systems.  OpenVMS Management Station provides acomprehensive user interface to OpenVMS account, printer, and storagemanagement.

OpenVMS ManagementStation is based on the Microsoft Management Console (MMC).  The Microsoft Management Console provides acommon management framework for various administration programs.  OpenVMS Management Station is implemented asan MMC snap-in and includes all of the MMC components you need.

OpenVMSManagement Station allows you to organize the systems you need to manage inways that are meaningful to you and your environment, and allows you to manage useraccounts, printers, and storage on those systems.

In addition, you caneasily manage user accounts, printers, and storage across multiple OpenVMSsystems.  For example, assume that youhave an account on three different OpenVMS Cluster systems.  With OpenVMS Management Station, you caneasily update a process quota, add a privilege, grant a rights identifier, andso forth, for each instance of the account.

OpenVMS ManagementStation consists of two components.  Youinstall the client software on a PC to perform all management operations.  You install the server component on all ofthe OpenVMS systems you want to manage. You do not interact directly with the server component.

·        RemoteManagement Support

You can use OpenVMS Management Station to remotely manageyour OpenVMS systems.  Once you establisha TCP/IP dialup connection, you can use OpenVMS Management Station to manageyour OpenVMS systems from home, while traveling, and so forth.

·        IntegratedWeb Features

MMC lets you insert World Wide Web URLs directly into the viewer and access themusing Microsoft Internet Explorer.  You can use this feature to addweb links of your own.  For example, youmight add a link to either an internal help desk page or to a system managementprocedures page.

·        Version3.2 New Features

Version 3.2 of the OpenVMS ManagementStation Client is supported on Windows 95, Windows 98, Windows 2000, andWindows Me.  The OpenVMS ManagementStation Server is supported on OpenVMS Versions 6.2, 7.2, and 7.3.

OpenVMS Management Station Version 3.2provides Fibre Channel disk device support and architectural changes to makethe product more stable.  Read therelease notes in Chapter 3 for more release-specific information.

StorageManagement

Version 3.0 of OpenVMSManagement Station added storage management support, making it easy for you tomanage your disk storage devices across multiple OpenVMS Cluster systems.  You no longer need to maintain complicatedcommand files to control your storage environment.  You can create, delete, and manage storagefrom an easy-to-use Windows interface. 

OpenVMS ManagementStation makes it easy for you to manage a wide range of storage devices acrossmultiple OpenVMS Cluster systems.  Itprovides a database that can automatically determine and configure yoursystem's storage configuration at system startup.

Some of the tasks youcan perform are:

·        Monitor your storage configuration

·        Examine and modify storage attributes

·        Create volumes

·        Control configuration over reboots

Figure 1 shows an example of howOpenVMS Management Station displays volume properties.

Figure 1  Volume Properties Dialog Box

Features include:

·        Storage configurationmanagement

You can create, delete, and manage a disk volume under oneinterface.  Wizards make it easy tocreate a volume.

·        Configurationcontrol over reboots

If you allow it to, OpenVMS Management Station preserves thedisk configuration across reboots. OpenVMS Management Station can mount and maintain your storageconfiguration without intervention.

And, OpenVMS Management Station enhances performance becauseit mounts volumes much faster than is possible with DCL or command procedures.

·        Coexistencewith established environments

You do not have to change your existing DCL commandprocedures. You can use the display capabilities of OpenVMS Management Stationwithout having to use the automated mount feature.  In this way, you can give OpenVMS ManagementStation as little or as much control as you want.

In addition, the OpenVMS Management Station serverperiodically generates a DCL command procedure that includes the commands tomount all of the volumes managed by OpenVMS Management Station.  If you are familiar with DCL, you can look atthis command procedure to see what actions OpenVMS Management Station performsfor you.  And, in the event of either anunforeseen system problem or a corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you could use this command procedure to mountthe volumes.  The following is the nameof the generated file:

SYS$SYSTEM:TNT$EMERGENCY_MOUNT.COM.

The OpenVMS Management Station server limitsthis file to seven versions.

PrinterManagement

OpenVMS Management Station makes it easy for you to manage a widerange of printers and print queues across multiple OpenVMS Cluster systems andOpenVMS nodes.  In addition, the printermonitoring feature allows you to quickly detect and correct printer problems.

You no longer need tomaintain complicated command files to control your printer environment.  You can create, delete, and manage a printerand its related queues, as well as manage print jobs for those printers from aneasy-to-use Windows interface.

Some of the tasks youcan perform are:

·        Monitor one or more printers

·        Examine and modify printer attributes

·        Delete printers and their associated queues

·        Create printers and their associated queues

·        Examine and modify queue attributes

·        Examine and modify job attributes, requeue jobs,and delete jobs

AccountManagement

You can use OpenVMSManagement Station to manage OpenVMS user accounts in a convenient, easymanner.  For example, when creating anaccount, OpenVMS Management Station can add a user authorization file (UAF)entry, grant rights identifiers, create an OpenVMS directory, set a disk quota,set up OpenVMS Mail characteristics, and so forth.

In addition, you caneasily manage user accounts across multipleOpenVMS systems.  For example, supposeyou have an account on three different OpenVMS Cluster systems.  OpenVMS Management Station makes it easy toupdate a process quota, add a privilege, grant a rights identifier, and soforth, for each instance of your account.

OpenVMS ManagementStation can manage the following OpenVMS resources:

·        SYSUAF.DAT user authorization file

·        TNT$UADB.DAT file

·        RIGHTSLIST.DAT user rights file

·        Network proxy database

·        Account login directory trees

·        User account disk quotas

·        OpenVMS Mail VMSMAIL_PROFILE.DATA file

What Is anOpenVMS Management Domain?

An OpenVMSManagement Domain is a system or collection of systems that you want tomanage as one unit. You can think of a Domain as a “manageable unit.” OpenVMSManagement Domains are the principal building blocks in the managementhierarchy.

When you design yourhierarchy, you determine what you want your manageable units to be. The systemsin the OpenVMS Management Domain depend on your needs. For example, they mightbe some of the clusters in a network, all of the systems on a given floor of abuilding, or a mix of clusters and nonclustered nodes.  You create the OpenVMS Management Domainbased on how you want to manage the systems under your control.

Once you have createdyour management domain, you can manage the user accounts on the systems in thedomain.

How AreSystems in the Domain Organized?

Youuse OpenVMS Management Domainsto group OpenVMS systems.  OpenVMSManagement Domains can include the following, as shown in Figure 2:

                OpenVMS Cluster systems

                   OpenVMS nodes

                 Other OpenVMS ManagementDomains

Figure 2  Example of an OpenVMS ManagementDomain

You can think of anOpenVMS Management Domain as a “manageable unit”; that is, the system, orcollection of systems, that you want to manage is one unit.  OpenVMS Management Domains are the principalbuilding blocks in the management hierarchy.

When you design yourhierarchy you determine what you want your manageable units to be.  The systems in the OpenVMS Management Domain dependon your needs.  They might be some of theclusters in a network, all of the systems on a given floor of a building, a mixof clusters and nonclustered nodes, and so forth.  You create the OpenVMS Management Domainbased on how you want to manage the systems under your control.

Once you have createdyour management domain, you can manage the user accounts on the systems in thedomain.

What isthe Scope of an Operation?

The scope of an operation is the set ofOpenVMS systems on which that operation takes place.  When you perform a management operation, suchas creating a user account, you need to be able to specify where you want theaccount to be created.  For example, youmight want to create the account on every OpenVMS system in your environment oron only one or two specific OpenVMS systems. OpenVMS Management Station gives you complete control of an operation'sscope.

The scope isdetermined by the object you select in the hierarchy. Think of the objects inthe hierarchy as parents and children. Parents contain otherobjects. Children are contained within parents and "inherit" theeffects of operations that are performed on their parents. 

If you perform anoperation on an object in the hierarchy, that operation is also performed onall of that object's children.  If thechild object has children of its own, the operation is performed on thosechildren as well.

AvoidSurprises

If you perform amanagement operation without thinking about its scope, you might be surprisedby the results.  For example, there mightbe a huge difference between creating a printer on one system and creating theprinter on every system in your building.

To avoid surprises,carefully consider scope when you create your management hierarchy.  Think about the logical relationships betweensystems and how to arrange those systems. 

You should alsoconsider what you want the scope of a management operation to be before youperform the operation.  Think about thesystems on which you want the operation to take place.  Pay particular attention to the item youselect in the hierarchy.

Choosinga Transport

When you create anOpenVMS Cluster object or OpenVMS Node object in an OpenVMS Management Domain,you choose whether to use DECnet or TCP/IP for all communications withthis system.

If you choose DECnet,other OpenVMS systems will use the DECnet transport when communicating withthis system.  If you choose TCP/IP, thattransport is used instead.  

Currently the OpenVMSManagement Station client supports only TCP/IP connections for primaryservers.  That is, the OpenVMS ManagementStation client will use only TCP/IPto communicate with any primary server; at least one OpenVMS system must berunning TCP/IP.  However, this does not prevent the OpenVMSsystems from communicating with each other using DECnet.

For TCP/IPconnections, OpenVMS Management Station uses the existing Windows SocketsDynamic Link Library (WINSOCK.DLL) and TCP/IP stack on your PC to establishconnections to your OpenVMS systems. 

On the OpenVMS system,the OpenVMS Management Station server automatically detects both the DECnet andTCP/IP protocols.  You do not have totake any specific action to tell the server which protocol to use.

Other Features

With OpenVMS Management Station you can create multiplemanagement windows.  Multiple windowsenable you to view and switch to multiple parts of the console interface atonce.  This means that each window canhave a different view of the current OpenVMS Management Domain.  For example, you could view printers in onewindow and storage in another.

Once you have created an OpenVMSManagement Domain you are satisfied with, you can save it to a "consolefile" (with the default extension of .MSC).  Loading the file later recreates all the savedmanagement domain settings.

AreThere Restrictions on the Systems in an OpenVMS Management Domain?

You canmanage any number of OpenVMS Cluster or node objects, with the followingconditions:

·        Managing cluster members as individual nodes isnot supported.  OpenVMS Cluster systemsare treated as indivisible entities; you cannot perform operations onindividual cluster members.

·        Creating nodes in a cluster or deleting themfrom a cluster is not supported.

·        Clusters with multiple user authorization files(UAFs) are not supported.

2

Before You Begin

Before you install or use thecurrent version of OpenVMS Management Station, you must read the Release Notesin Chapter 3.  The Release Notes contain criticalinformation pertaining to the current release of OpenVMS ManagementStation.  It is especially important foryou to know on which versions of the operating system it will run, itscompatibility with previous versions, and the currently supported configurations.  Please read the Release Notes in Chapter 3before you proceed.

Where to Find Information

The OpenVMS Management Station helpfile contains a complete example of how to get started with OpenVMS ManagementStation.

This chapter describes how to createa simple OpenVMS Management Domain consisting of one OpenVMS node.  The chapter also provides an example of howto manage user accounts on that system.

Depending on the systems you need tomanage, your own OpenVMS Management Domain might include many OpenVMS Clustersystems, OpenVMS nodes, or other OpenVMS Management Domains.

GettingStarted

1.     Select OpenVMS Management Station from theStart menu, as shown below. 

The main viewer dialog box isdisplayed.  The Cluster/Node Wizardrecognizes that you do not have an existing OpenVMS Management Domain and askswhether you want to add an OpenVMS Cluster system or OpenVMS node to thedomain. 

2.     You will use the wizard to create the firstentry in the OpenVMS Management Domain. Click Yes, then click Next, as shown.

3.     Select OpenVMS Cluster or OpenVMSsystem.  If you have both OpenVMS Clustersystems and nonclustered nodes in your environment, you can choose eitherone.  To get started, you might find itconvenient to make the display name the cluster or node name, as shown in theexample below.

4.     Fill in the name or IP address of anOpenVMS Cluster system or OpenVMS node on which you want to try OpenVMSManagement Station operations.  (The OpenVMSManagement Station server must be running on this system.)  If you do not specify the IP domain, thedefault IP domain is assumed.

5.     Specify a user name for the OpenVMSsystem.  Although you are using a PC tomanage your OpenVMS system, the account name you use to connect to the OpenVMSsystem must have all privileges (set as default privileges).  The user name and password will be subject tothe same security checks as they would if you were logging in directly to theOpenVMS system. 

It might be easier if your OpenVMS user name is the same as your Windows NTuser name.

6.     Click Finish tocomplete the process.

7.       Select (single click) the OpenVMS Accountsobject to display a list of user accounts.

(At this point you can also expand the OpenVMS Printersobject to view printers, queues, and jobs, and the OpenVMS Storage object toview disk volumes.)

8.       Enter your password for the OpenVMS system andclick OK.  (You need to enter yourpassword when you first establish a connection.)

9.     Select an OpenVMS User Accounts object inthe right-hand pane.

10.   Right-clickand choose Properties to display the account attributes for that useraccount.  This displays the OpenVMS UserAccount Properties dialog box shown below.

11.   Clickeach tab in the dialog box to see how the account attributes arepresented.  When you are done, clickCancel to return to the viewer. 

12.   Expandthe OpenVMS Printers object to view printers, queues, and jobs, and the OpenVMSStorage object to view disk volumes, as shown below.

13.   Optionally,you can create multiple management windows, in which each window has adifferent view of the current OpenVMS Management Domain.  You can select the object you want to be the"root" object in that view.  Todo this:

a.       Select the object for which you want to startthe new window.

b.      Select New window from herefrom the right-click options.

For example, you could create a window that displays only theprinter components for a given OpenVMS system, as shown below:

Next Steps

Examine how the account, printer, and storageattributes are presented in OpenVMS Management Station.  This is a good time to become familiar withthe layout of the dialog boxes and attributes. 

Click the tabs at the top of the dialog box to examine other attributes.  You can switch between attribute groups andmake changes anywhere. 

When working with attributes in a dialog box, keep the following in mind:

StorageManagement Operations

OpenVMS Management Station supports the following storagemanagement operations.  Commands areavailable from the Action menu or from the right-click options.

PrinterManagement Operations

OpenVMS Management Station supports thefollowing printer management operations. Commands are available from the Action menu or from the right-clickoptions.

AccountManagement Operations

OpenVMS Management Station supports thefollowing account management operations. Commands are available from the Action menu or from the right-clickoptions.

This chapter contains important information regarding thecurrent version of the OpenVMS Management Station software.  This information might not be available inthe installation guide or in online help. Read this chapter before you begin using OpenVMS Management Station.

Supported Platforms

Version 3.2 of the OpenVMS Management Station client is supportedon:

·        Windows NT 4.0 (Service Pack 3 or higher)

·        Windows 95

·        Windows 98

·        Windows 2000

·        Windows Me

The OpenVMS Management Station server is supported on:

·        OpenVMS Version 6.2

·        OpenVMS Version 7.2

·        OpenVMS Version 7.3

Compatibilitywith Previous Versions

OpenVMSManagement Station Version 3.2 is a 32-bit application and is compatible withthe management domains created with OpenVMS Management Station Version3.0.  If you are running a version ofOpenVMS Management Station prior to Version 3.0, you must re-create existingOpenVMS Management Domains for use with Versions 3.2 and 3.0. 

If you install Version 3.2 of the client software on yourPC, install Version 3.2 of the server on all of the OpenVMS systems that youwant to manage.  When it first starts up,the OpenVMS Management Station server will update an existing Version 2.1database and journal to Version 3.2 status. This update cannot be reversed and will render the files unusable with Version2.1.

You may never need theVersion 2.1 files again, but as a safeguard, the installation backs up thefollowing files for you:

·        TNT$UADB.DAT

·        TNT$ACS.DAT

·        TNT$JOURNAL.TNT$TRANSACTION_JOURNAL

SupportedConfigurations

The following table shows thesupported configurations for the current version of OpenVMS Management Station.

Important Notes

·        This version of the Microsoft Management Consolerequires that files provided by Microsoft Internet Explorer 4.01 or higher be present on the system.

·        The OpenVMS Management Station client supportsonly TCP/IP connections for primary servers, so at least one OpenVMS system must be running TCP/IP.

·        If you are running Version 6.2 of OpenVMS andplan to manage shadow volumes, you will need remedial kits.  See the OpenVMS installation guide fordetails.

·        Additional TCP/IP stacks for OpenVMS have notbeen tested.  However, TCP/IP stacks thatare 100% compliant with the QIO interface for Compaq TCP/IP Services forOpenVMS should also work.  Contact yourTCP/IP vendor for additional information and support issues.

KnownProblems and Restrictions

This section detailsknown problems and restrictions in the OpenVMS Management Stationsoftware.  

OnlyCluster-Unique Devices Managed

This release ofOpenVMS Management Station manages and displays only disks that are visible toall nodes in a cluster.  This means thatyou will not be able to display or manage public volumes mounted on"unmanaged" devices, such as an InfoServer device.

It also means thatOpenVMS Management Station does not manage SCSI disks connected to VAX systems.

BoundVolumes Limited in Number of Members

OpenVMS Management Station can manage boundvolumes with these restrictions:

·        If every member volume is a shadow set with onemember, the maximum number of member volumes is 28.

·        If every member volume is a nonshadowed disk,the maximum number of member volumes is 42.

Privately Mounted and Foreign Volumes NotManaged

OpenVMSManagement Station handles privately mounted and foreign volumes as specialcases and does not display or manage them.

Files Created After Error Is Logged

When the OpenVMS Management Stationserver is first installed on a system, the TNT$SERVER_ERROR.LOG error logcontains errors that indicate that the TNT$ACS.DAT and journal files could notbe found.  These files are, in fact,created immediately after the errors are logged.  You can ignore the errors.

Write-LockedShadow Sets Not Supported

This version of OpenVMS ManagementStation does not support write-locked shadow sets.

ClickingStop to Interrupt an Operation

Expanding an OpenVMS Storage objectoccasionally results in a "Retrieving    information from the server..." message window being displayed. Ifyou click the Stop button while this message is displayed, the following errormight be reported:

      TNT-F-Writelock Locked against write access

            SYSTEM-W-NOTQUEUED, Request not queued

To work around this problem, selectthat same OpenVMS Storage Object, and refresh the display either by using theF5 key or by choosing Refresh from the Action menu.

ServerBusy Message

If the OpenVMS Management Stationserver returns a "busy, try again later" message, it usually meansthat multiple clients are using the server at the same time. Retry theoperation.

Settingthe 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 Stationconsiders the DMA control to be set.

If DMA support is later added forthe device, you must clear the DMA attribute and then reset it in order toenable DMA support on the physical device. You cannot just set DMA againbecause the OpenVMS Management Station believes it is already set and will notset it again until it is first cleared.

DECnetPhase IV Database and Proxies Issue

OpenVMS Management Station does notupdate the DECnet Phase IV NETPROXY.DAT file. If you add a proxy using OpenVMSManagement Station, applications such as DFS (prior to Version 2.0) and DECnetPhase IV (components such as file access listener [FAL]) that read the Phase IVdatabase do not see the proxy.

Use OpenVMS Authorize utility(AUTHORIZE) to add a proxy if you require access by DFS (prior to Version 2.0)and DECnet Phase IV components such as FAL.

RenamingUsers Resets New Mail Count

If you rename a user account thathas unread new mail messages, the new mail count for the renamed account is setto zero. However, the user can use the READ/NEW command to read the new mailmessages.

ManuallyEditing the UIC Group Number

If you manually edit the UIC Groupcontrol on the Advanced UIC dialog box, the Next Available Member and NextHighest Member controls are not updated.

If you select an existing group fromthe list, the Next Available Member and Next Highest Member controls areproperly updated. Please see the online help for more information. 

TCPwarePrint Symbiont Limitation

Queues that are based upon TCPware'sprint symbiont TCPWARE_TSSYM cannot    be made autostartable. As such, this type of queue cannot be used as thereference printer during a Create Printer operation.

PrinterRename Fails for Reconciled Printers with DQS Queues

If you rename a printer at theOpenVMS Management Domain level, and the   printer you select is a reconciled printer with two or more DQS queuesfrom the same node, the rename operation fails to rename all reconciledprinters.

DuplicateQueue Names on Create

When creating a printer at theOpenVMS Management Domain level based on a    reference printer accessed using DQS, the queue-naming algorithmsometimes     generates duplicate queuenames. To work around this problem, check the queue names anduse the Rename control to correct any duplicates.

DestinationField Not Shown

When viewing the devices for aprinter made up of DQS and unknown (other) devices, the Destination Node fieldis not shown for the DQS device.

Installationon OpenVMS Version 7.2 and Later

OpenVMS Management Station 3.0B is apart of the OpenVMS Version 7.2 operating system. During installation ofOpenVMS Management Station Version 3.2 on this operating system, the filessupplied by OpenVMS are replaced by the new files. Because of some problems inthe POLYCENTER Software Installation utility database, the TNT objects will havetwo entries with the same name---one provided by OpenVMS Version 7.2 and othersprovided by OpenVMS Management Station Version 3.2.  The PCSI Objects corresponding to thereplaced files will have a “Conflict” status in the PCSI database.

If OpenVMS Management StationVersion 3.2 is uninstalled at a later time, the POLYCENTER SoftwareInstallation utility database reassigns ownership of those files back toOpenVMS; the files will have the status "OK.” The PRODUCT SHO OBJECT *TNT*/FULL command will no longer show any conflicts, but the files retained will bethe Version 3.2 files and not the Version 3.0B files supplied with theoperating system. 

In addition, some extra files aresupplied with OpenVMS Management Station Version 3.0B that are not supplied orrequired with Version 3.2, since they are obsolete. This problem is notspecific to OpenVMS Version 7.2; it can occur with later versions of OpenVMS aswell.

ProblemsFixed in Version 3.2

The problems described below, seen in previous versions ofOpenVMS Management Station, have been fixed in Version 3.2

Bad Magic Number Problem

When OpenVMS Management Station was upgraded from Version 2.0to Version 3.0, a "Bad Magic Number" error message was reported.  This problem was due to some formatconversion of the TNT$ACS.DAT file.

Flooding of MonitoringEvents

When the server monitored some events, it entered arace-around condition, flooding the server with collect events.  This condition resulted in over consumptionof resources.

Incorrect Updating of Mount/Dismount Status

Under certain circumstances, the server returned a successstatus for the mount/dismount operation when, in fact, the operation hadfailed.  However, the client wronglyupdated the mount status of the volume, causing confusion for users.

Server Failure

The OpenVMS Management Stationserver failed while acquiring a lock in kernel mode.

Problem Recognizing FibreChannel Disk Devices

The server had some problems recognizing Fibre Channel diskdevices.

Server Looping

The OpenVMS Management Station server used to get into a CPUbound loop, which resulted in over consumption of system resources.  This problem occurred while a server threadwas searching for a specific persona from a list of personas. (A persona is anobject that contains security information. Each thread in the server process must assume a specific persona beforedoing any operation.)

Primary Server Selection

Whileadding a new node or cluster to the OpenVMS Management Station client, theprimary server checkbox remained enabled when the DECnet option was selected.Because OpenVMS Management Station client supports only the TCP/IP protocolbetween a client PC and the OpenVMS Server, this problem is now resolved.

Server Hangs on OpenVMS Version 7.3

Because ofa change in the behavior of a DECthreads call in OpenVMS Version 7.3, theOpenVMS Management Station Version 3.0B Server used to hang on OpenVMS Version7.3.

AdditionalNotes

External Authentication

OpenVMS Version 7.1allows users to log in using an account and password maintained by an externalauthentication agent, such as a primary domain controller in a LANmandomain. 

To use thisfunctionality, you need to use the AUTHORIZE qualifier /FLAGS=EXTAUTH with theADD, COPY, MODIFY, and RENAME commands. If this flag is set and a matching account does not exist in theexternal authenticator, the user cannot log in, even if there is a matchingaccount in the OpenVMS UAF file.

OpenVMS ManagementStation does not yet display or control this flag.  However, it does propagate the flag when youcreate, modify, or rename accounts.  Forexample, when you create an account, the flag is set; however, it is set in thereference account.

When you create orrename an account and the EXTAUTH flag is set, the following warning is issued:

TNT-W-EXTAUTH, Newly created or renamed account is externallyauthenticated.
Make sure a corresponding account exists in the external domain.

This message is areminder that, in order for the login to succeed, an account that matches thenew OpenVMS account name must exist in the external authenticator's securitydomain.

To disable externalauthentication, use the AUTHORIZE command MODIFY account /FLAGS=NOEXTAUTH.

FilteringUsers by Rights Identifier

The time needed to filter users bytheir rights identifiers is directly proportional to the number of users andrights identifiers on the system.