![[Compaq]](../../images/hp.gif)
![[Go to the documentation home page]](../../images/buttons/hp_bn_site_home.gif)
![[How to order documentation]](../../images/buttons/hp_bn_order_docs.gif)
![[Help on this site]](../../images/buttons/hp_bn_site_help.gif)
![[How to contact us]](../../images/buttons/hp_bn_comments.gif)
![[OpenVMS documentation]](../../images/hp_ovmsdoc_sec_head.gif)
| Document revision date: 15 July 2002 | |
|
|
|
|
|
|
OpenVMS Management Station
Overview and Release Notes
Order Number: AA-QJGCE-TE
June 2002
This document
provides an overview of OpenVMS Management Station and describes how to get
started using the software. This
document also includes release notes for OpenVMS Management Station.
Revision/Update
Information: This manual supersedes the OpenVMS Management Station Overview and
Release Notes, Version 3.0.
Software
Version: OpenVMS
Management Station Version 3.2
Operating
System: OpenVMS Alpha
Version 7.3-1
OpenVMS VAX Version 7.3
Compaq Computer
Corporation
©
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 Information
Technologies Group, L.P. in the
Microsoft, MS-DOS, Visual C++,
Windows, and Windows NT are trademarks of Microsoft Corporation in the
All other product names mentioned
herein may be
trademarks of their respective companies.
Confidential
computer software. Valid license from Compaq 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.
Compaq shall not be liable for
technical or editorial errors or omissions contained herein. The information in
this document is provided “as is” without warranty of any kind and is subject
to change without notice. The warranties for Compaq products are set forth in
the express limited warranty statements accompanying such products. Nothing
herein should be construed as constituting an additional warranty/
The Compaq OpenVMS documentation set is available on CD-ROM.
ents
What Is
OpenVMS Management Station?
What
Is an OpenVMS Management Domain?
How
Are Systems in the Domain Organized?
What
is the Scope of an Operation?
Are
There Restrictions on the Systems in an OpenVMS Management Domain?
Compatibility
with Previous Versions
Known
Problems and Restrictions
Only
Cluster-Unique Devices Managed
Bound
Volumes Limited in Number of Members
Privately
Mounted and Foreign Volumes Not Managed
Files
Created After Error Is Logged
Write-Locked
Shadow Sets Not Supported
Clicking
Stop to Interrupt an Operation
DECnet
Phase IV Database and Proxies Issue
Renaming
Users Resets New Mail Count
Manually
Editing the UIC Group Number
TCPware
Print Symbiont Limitation
Printer
Rename Fails for Reconciled Printers with DQS Queues
Duplicate
Queue Names on Create
Installation
on OpenVMS Version 7.2 and Later
Incorrect
Updating of Mount/Dismount Status
Problem
Recognizing Fibre Channel Disk Devices.
Server
Hangs on OpenVMS Version 7.3
Filtering
Users by Rights Identifier
Figures
Figure
1 Volume Properties Dialog Box……………………
Figure 2 Example of
an OpenVMS Management Domain…
Intended Audience
This document is intended for system
managers, operators, and others who want to use OpenVMS Management Station to
manage user accounts, printers, and storage.
Document Structure
This document is divided into the
following chapters:
Chapter 1 provides an overview of OpenVMS
Management Station and introduces new features for Version 3.2.
Chapter 2 describes how to get started
using the OpenVMS Management Station software.
Chapter 3 provides the release notes that
you should read before you start to use OpenVMS Management Station.
Reader's Comments
Compaq welcomes your comments on
this manual. Please send comments to
either of the following addresses:
Internet openvmsdoc@compaq.com
Mail Compaq
Computer Corporation
OSSG Documentation
Group, ZKO3-4/U08
How To
Order Additional Documentation
Visit the following World Wide Web address
for information about how to order additional documentation:
http://www.openvms.compaq.com/
1
OpenVMS Management
Station is a powerful Microsoft Windows based management tool for system
managers and others who perform management tasks on OpenVMS systems. OpenVMS Management Station provides a
comprehensive user interface to OpenVMS account, printer, and storage
management.
OpenVMS Management
Station is based on the Microsoft Management Console (MMC). The Microsoft Management Console provides a
common management framework for various administration programs. OpenVMS Management Station is implemented as
an MMC snap-in and includes all of the MMC components you need.
OpenVMS
Management Station allows you to organize the systems you need to manage in
ways that are meaningful to you and your environment, and allows you to manage user
accounts, printers, and storage on those systems.
In addition, you can
easily manage user accounts, printers, and storage across multiple OpenVMS
systems. For example, assume that you
have an account on three different OpenVMS Cluster systems. With OpenVMS Management Station, you can
easily update a process quota, add a privilege, grant a rights identifier, and
so forth, for each instance of the account.
OpenVMS Management
Station consists of two components. You
install the client software on a PC to perform all management operations. You install the server component on all of
the OpenVMS systems you want to manage.
You do not interact directly with the server component.
·
Remote
Management Support
You can use OpenVMS Management Station to remotely manage
your OpenVMS systems. Once you establish
a TCP/IP dialup connection, you can use OpenVMS Management Station to manage
your OpenVMS systems from home, while traveling, and so forth.
·
Integrated
Web Features
MMC lets you insert World Wide Web URLs directly into the viewer and access them
using Microsoft Internet Explorer. You can use this feature to add
web links of your own. For example, you
might add a link to either an internal help desk page or to a system management
procedures page.
·
Version
3.2 New Features
Version 3.2 of the OpenVMS Management
Station Client is supported on Windows 95, Windows 98, Windows 2000, and
Windows Me. The OpenVMS Management
Station Server is supported on OpenVMS Versions 6.2, 7.2, and 7.3.
OpenVMS Management Station Version 3.2
provides Fibre Channel disk device support and architectural changes to make
the product more stable. Read the
release notes in Chapter 3 for more release-specific information.
Version 3.0 of OpenVMS
Management Station added storage management support, making it easy for you to
manage your disk storage devices across multiple OpenVMS Cluster systems. You no longer need to maintain complicated
command files to control your storage environment. You can create, delete, and manage storage
from an easy-to-use Windows interface.
OpenVMS Management
Station makes it easy for you to manage a wide range of storage devices across
multiple OpenVMS Cluster systems. It
provides a database that can automatically determine and configure your
system's storage configuration at system startup.
Some of the tasks you
can perform are:
·
Monitor your storage configuration
·
Examine and modify storage attributes
·
Create volumes
·
Control configuration over reboots
Figure 1 shows an example of how
OpenVMS Management Station displays volume properties.
Figure 1 Volume Properties Dialog Box
Features include:
·
Storage configuration
management
You can create, delete, and manage a disk volume under one
interface. Wizards make it easy to
create a volume.
·
Configuration
control over reboots
If you allow it to, OpenVMS Management Station preserves the
disk configuration across reboots.
OpenVMS Management Station can mount and maintain your storage
configuration without intervention.
And, OpenVMS Management Station enhances performance because
it mounts volumes much faster than is possible with DCL or command procedures.
·
Coexistence
with established environments
You do not have to change your existing DCL command
procedures. You can use the display capabilities of OpenVMS Management Station
without having to use the automated mount feature. In this way, you can give OpenVMS Management
Station as little or as much control as you want.
In addition, the OpenVMS Management Station server
periodically generates a DCL command procedure that includes the commands to
mount all of the volumes managed by OpenVMS Management Station. If you are familiar with DCL, you can look at
this command procedure to see what actions OpenVMS Management Station performs
for you. And, in the event of either an
unforeseen system problem or a corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you could use this command procedure to mount
the volumes. The following is the name
of the generated file:
SYS$SYSTEM:TNT$EMERGENCY_MOUNT.COM.
The OpenVMS Management Station server limits
this file to seven versions.
OpenVMS Management Station makes it easy for you to manage a wide
range of printers and print queues across multiple OpenVMS Cluster systems and
OpenVMS nodes. In addition, the printer
monitoring feature allows you to quickly detect and correct printer problems.
You no longer need to
maintain complicated command files to control your printer environment. You can create, delete, and manage a printer
and its related queues, as well as manage print jobs for those printers from an
easy-to-use Windows interface.
Some of the tasks you
can 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
You can use OpenVMS
Management Station to manage OpenVMS user accounts in a convenient, easy
manner. For example, when creating an
account, 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 can
easily manage user accounts across multiple
OpenVMS systems. For example, suppose
you have an account on three different OpenVMS Cluster systems. OpenVMS Management Station makes it easy to
update a process quota, add a privilege, grant a rights identifier, and so
forth, for each instance of your account.
OpenVMS Management
Station 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
An OpenVMS
Management Domain is a system or collection of systems that you want to
manage as one unit. You can think of a Domain as a “manageable unit.” OpenVMS
Management Domains are the principal building blocks in the management
hierarchy.
When you design your
hierarchy, you determine what you want your manageable units to be. The systems
in the OpenVMS Management Domain depend on your needs. For example, they might
be some of the clusters in a network, all of the systems on a given floor of a
building, or a mix of clusters and nonclustered nodes. You create the OpenVMS Management Domain
based on how you want to manage the systems under your control.
Once you have created
your management domain, you can manage the user accounts on the systems in the
domain.
You
use OpenVMS Management Domains
to group OpenVMS systems. OpenVMS
Management Domains can include the following, as shown in Figure 2:
OpenVMS Cluster systems
OpenVMS nodes
Other OpenVMS Management
Domains
Figure 2 Example of an OpenVMS Management
Domain
You can think of an
OpenVMS Management Domain as a “manageable unit”; that is, the system, or
collection of systems, that you want to manage is one unit. OpenVMS Management Domains are the principal
building blocks in the management hierarchy.
When you design your
hierarchy you determine what you want your manageable units to be. The systems in the OpenVMS Management Domain depend
on your needs. They might be some of the
clusters in a network, all of the systems on a given floor of a building, a mix
of clusters and nonclustered nodes, and so forth. You create the OpenVMS Management Domain
based on how you want to manage the systems under your control.
Once you have created
your management domain, you can manage the user accounts on the systems in the
domain.
The scope of an operation is the set of
OpenVMS systems on which that operation takes place. When you perform a management operation, such
as creating a user account, you need to be able to specify where you want the
account to be created. For example, you
might want to create the account on every OpenVMS system in your environment or
on only one or two specific OpenVMS systems.
OpenVMS Management Station gives you complete control of an operation's
scope.
The scope is
determined by the object you select in the hierarchy. Think of the objects in
the hierarchy as parents and children. Parents contain other
objects. Children are contained within parents and "inherit" the
effects of operations that are performed on their parents.
If you perform an
operation on an object in the hierarchy, that operation is also performed on
all of that object's children. If the
child object has children of its own, the operation is performed on those
children as well.
If you perform a
management operation without thinking about its scope, you might be surprised
by the results. For example, there might
be a huge difference between creating a printer on one system and creating the
printer on every system in your building.
To avoid surprises,
carefully consider scope when you create your management hierarchy. Think about the logical relationships between
systems and how to arrange those systems.
You should also
consider what you want the scope of a management operation to be before you
perform the operation. Think about the
systems on which you want the operation to take place. Pay particular attention to the item you
select in the hierarchy.
When you create an
OpenVMS Cluster object or OpenVMS Node object in an OpenVMS Management Domain,
you choose whether to use DECnet or TCP/IP for all communications with
this system.
If you choose DECnet,
other OpenVMS systems will use the DECnet transport when communicating with
this system. If you choose TCP/IP, that
transport is used instead.
Currently the OpenVMS
Management Station client supports only TCP/IP connections for primary
servers. That is, the OpenVMS Management
Station client will use only TCP/IP
to communicate with any primary server; at least one OpenVMS system must be
running TCP/IP. However, this does not prevent the OpenVMS
systems from communicating with each other using DECnet.
For TCP/IP
connections, OpenVMS Management Station uses the existing Windows Sockets
Dynamic Link Library (WINSOCK.DLL) and TCP/IP stack on your PC to establish
connections to your OpenVMS systems.
On the OpenVMS system,
the OpenVMS Management Station server automatically detects both the DECnet and
TCP/IP protocols. You do not have to
take any specific action to tell the server which protocol to use.
With OpenVMS Management Station you can create multiple
management windows. Multiple windows
enable you to view and switch to multiple parts of the console interface at
once. This means that each window can
have a different view of the current OpenVMS Management Domain. For example, you could view printers in one
window and storage in another.
Once you have created an OpenVMS
Management Domain you are satisfied with, you can save it to a "console
file" (with the default extension of .MSC). Loading the file later recreates all the saved
management domain settings.
You can
manage any number of OpenVMS Cluster or node objects, with the following
conditions:
·
Managing cluster members as individual nodes is
not supported. OpenVMS Cluster systems
are treated as indivisible entities; you cannot perform operations on
individual cluster members.
·
Creating nodes in a cluster or deleting them
from a cluster is not supported.
·
Clusters with multiple user authorization files
(UAFs) are not supported.
2
Before you install or use the
current version of OpenVMS Management Station, you must read the Release Notes
in Chapter 3. The Release Notes contain critical
information pertaining to the current release of OpenVMS Management
Station. It is especially important for
you to know on which versions of the operating system it will run, its
compatibility with previous versions, and the currently supported configurations. Please read the Release Notes in Chapter 3
before you proceed.
The OpenVMS Management Station help
file contains a complete example of how to get started with OpenVMS Management
Station.
This chapter describes how to create
a simple OpenVMS Management Domain consisting of one OpenVMS node. The chapter also provides an example of how
to manage user accounts on that system.
Depending on the systems you need to
manage, your own OpenVMS Management Domain might include many OpenVMS Cluster
systems, OpenVMS nodes, or other OpenVMS Management Domains.
1. Select OpenVMS Management Station from the
Start menu, as shown below.
The main viewer dialog box is
displayed. The Cluster/Node Wizard
recognizes that you do not have an existing OpenVMS Management Domain and asks
whether you want to add an OpenVMS Cluster system or OpenVMS node to the
domain.
2. You will use the wizard to create the first
entry in the OpenVMS Management Domain.
Click Yes, then click Next, as shown.
3. Select OpenVMS Cluster or OpenVMS
system. If you have both OpenVMS Cluster
systems and nonclustered nodes in your environment, you can choose either
one. To get started, you might find it
convenient to make the display name the cluster or node name, as shown in the
example below.
4. Fill in the name or IP address of an
OpenVMS Cluster system or OpenVMS node on which you want to try OpenVMS
Management Station operations. (The OpenVMS
Management Station server must be running on this system.) If you do not specify the IP domain, the
default IP domain is assumed.
5. Specify a user name for the OpenVMS
system. Although you are using a PC to
manage your OpenVMS system, the account name you use to connect to the OpenVMS
system must have all privileges (set as default privileges). The user name and password will be subject to
the same security checks as they would if you were logging in directly to the
OpenVMS system.
It might be easier if your OpenVMS user name is the same as your Windows NT
user name.
6. Click Finish to
complete the process.
7.
Select (single click) the OpenVMS Accounts
object to display a list of user accounts.
(At this point you can also expand the OpenVMS Printers
object to view printers, queues, and jobs, and the OpenVMS Storage object to
view disk volumes.)
8.
Enter your password for the OpenVMS system and
click OK. (You need to enter your
password when you first establish a connection.)
9. Select an OpenVMS User Accounts object in
the right-hand pane.
10. Right-click
and choose Properties to display the account attributes for that user
account. This displays the OpenVMS User
Account Properties dialog box shown below.
11. Click
each tab in the dialog box to see how the account attributes are
presented. When you are done, click
Cancel to return to the viewer.
12. Expand
the OpenVMS Printers object to view printers, queues, and jobs, and the OpenVMS
Storage object to view disk volumes, as shown below.
13. Optionally,
you can create multiple management windows, in which each window has a
different view of the current OpenVMS Management Domain. You can select the object you want to be the
"root" object in that view. To
do this:
a.
Select the object for which you want to start
the new window.
b.
Select New window from here
from the right-click options.
For example, you could create a window that displays only the
printer components for a given OpenVMS system, as shown below:
Examine how the account, printer, and storage
attributes are presented in OpenVMS Management Station. This is a good time to become familiar with
the 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 and
make changes anywhere.
When working with attributes in a dialog box, keep the following in mind:
|
If you want to |
Then |
|
Make changes and return to the viewer |
Click OK |
|
Make changes without returning to the viewer |
Click Apply Now |
|
Return to the viewer without making changes |
Click Cancel |
OpenVMS Management Station supports the following storage
management operations. Commands are
available from the Action menu or from the right-click options.
|
For this task |
Use this command |
|
Create a volume |
New Volume |
|
Monitor storage |
Monitor |
|
Modify volume and device attributes |
Properties |
|
Delete a volume and move its |
Delete |
|
Mount/dismount a volume |
Mount and Dismount |
|
Add/remove a volume set |
Add Member/ |
OpenVMS Management Station supports the
following printer management operations.
Commands are available from the Action menu or from the right-click
options.
|
For this task |
Use this
command |
|
Create
a printer and its queues |
Create
|
|
Monitor
printers |
Monitor |
|
Modify
printer, queue, and print job attributes |
Properties |
|
Delete
a printer and its queues |
Delete |
|
Rename
a printer |
Rename |
|
Stop,
start, or restart a printer or queue |
Stop, Start, or Restart |
OpenVMS Management Station supports the
following account management operations.
Commands are available from the Action menu or from the right-click
options.
|
For this task |
Use this command |
|
Create user accounts |
Create
|
|
Modify user accounts (any aspect) |
Properties
|
|
Delete user accounts |
Delete |
|
Rename user accounts |
Rename |
|
Display user account attributes |
Properties |
This chapter contains important information regarding the
current version of the OpenVMS Management Station software. This information might not be available in
the installation guide or in online help.
Read this chapter before you begin using OpenVMS Management Station.
Version 3.2 of the OpenVMS Management Station client is supported
on:
·
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
OpenVMS
Management Station Version 3.2 is a 32-bit application and is compatible with
the management domains created with OpenVMS Management Station Version
3.0. If you are running a version of
OpenVMS Management Station prior to Version 3.0, you must re-create existing
OpenVMS Management Domains for use with Versions 3.2 and 3.0.
If you install Version 3.2 of the client software on your
PC, install Version 3.2 of the server on all of the OpenVMS systems that you
want to manage. When it first starts up,
the OpenVMS Management Station server will update an existing Version 2.1
database and journal to Version 3.2 status. This update cannot be reversed and will render the files unusable with Version
2.1.
You may never need the
Version 2.1 files again, but as a safeguard, the installation backs up the
following files for you:
·
TNT$UADB.DAT
·
TNT$ACS.DAT
·
TNT$JOURNAL.TNT$TRANSACTION_JOURNAL
The following table shows the
supported configurations for the current version of OpenVMS Management Station.
|
OpenVMS Server Software |
||
|
OpenVMS VAX OpenVMS Alpha |
AND |
Compaq TCP/IP Services for OpenVMS DECnet for OpenVMS (optional) |
|
PC Client Software |
||
|
Microsoft Windows NT Windows 95 Windows 98 Windows 2000 Windows Me Microsoft Internet Explorer |
AND |
Compliant TCP/IP stack, |
·
This version of the Microsoft Management Console
requires that files provided by Microsoft Internet Explorer 4.01 or higher be present on the system.
·
The OpenVMS Management Station client supports
only 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 and
plan to manage shadow volumes, you will need remedial kits. See the OpenVMS installation guide for
details.
·
Additional TCP/IP stacks for OpenVMS have not
been tested. However, TCP/IP stacks that
are 100% compliant with the QIO interface for Compaq TCP/IP Services for
OpenVMS should also work. Contact your
TCP/IP vendor for additional information and support issues.
This section details
known problems and restrictions in the OpenVMS Management Station
software.
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.
OpenVMS Management Station can manage bound
volumes with these restrictions:
·
If every member volume is a shadow set with one
member, the maximum number of member volumes is 28.
·
If every member volume is a nonshadowed disk,
the maximum number of member volumes is 42.
OpenVMS
Management Station handles privately mounted and foreign volumes as special
cases and does not display or manage them.
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.
This version of OpenVMS Management
Station does not support write-locked shadow sets.
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 either by using the
F5 key or by choosing Refresh from the Action menu.
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.
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.
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 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.
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.
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.
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.
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.
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.
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.
OpenVMS Management Station 3.0B is a
part of the OpenVMS Version 7.2 operating system. During installation of
OpenVMS Management Station Version 3.2 on this operating system, the files
supplied by OpenVMS are replaced by the new files. Because of some problems in
the POLYCENTER Software Installation utility database, the TNT objects will have
two entries with the same name---one provided by OpenVMS Version 7.2 and others
provided by OpenVMS Management Station Version 3.2. The PCSI Objects corresponding to the
replaced files will have a “Conflict” status in the PCSI database.
If OpenVMS Management Station
Version 3.2 is uninstalled at a later time, the POLYCENTER Software
Installation utility database reassigns ownership of those files back to
OpenVMS; 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 be
the Version 3.2 files and not the Version 3.0B files supplied with the
operating system.
In addition, some extra files are
supplied with OpenVMS Management Station Version 3.0B that are not supplied or
required with Version 3.2, since they are obsolete. This problem is not
specific to OpenVMS Version 7.2; it can occur with later versions of OpenVMS as
well.
The problems described below, seen in previous versions of
OpenVMS Management Station, have been fixed in Version 3.2
When OpenVMS Management Station was upgraded from Version 2.0
to Version 3.0, a "Bad Magic Number" error message was reported. This problem was due to some format
conversion of the TNT$ACS.DAT file.
When the server monitored some events, it entered a
race-around condition, flooding the server with collect events. This condition resulted in over consumption
of resources.
Under certain circumstances, the server returned a success
status for the mount/dismount operation when, in fact, the operation had
failed. However, the client wrongly
updated the mount status of the volume, causing confusion for users.
The OpenVMS Management Station
server failed while acquiring a lock in kernel mode.
The server had some problems recognizing Fibre Channel disk
devices.
The OpenVMS Management Station server used to get into a CPU
bound loop, which resulted in over consumption of system resources. This problem occurred while a server thread
was searching for a specific persona from a list of personas. (A persona is an
object that contains security information.
Each thread in the server process must assume a specific persona before
doing any operation.)
While
adding a new node or cluster to the OpenVMS Management Station client, the
primary server checkbox remained enabled when the DECnet option was selected.
Because OpenVMS Management Station client supports only the TCP/IP protocol
between a client PC and the OpenVMS Server, this problem is now resolved.
Because of
a change in the behavior of a DECthreads call in OpenVMS Version 7.3, the
OpenVMS Management Station Version 3.0B Server used to hang on OpenVMS Version
7.3.
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 and 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 you
create, modify, or rename 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 message is a
reminder that, in order for the login to succeed, an account that matches the
new OpenVMS account name must exist in the external authenticator's security
domain.
To disable external
authentication, use the AUTHORIZE command MODIFY account
/FLAGS=NOEXTAUTH.
The time needed to filter users by
their rights identifiers is directly proportional to the number of users and
rights identifiers on the system.
|
|
| privacy and legal statement | ||
| OMS_OVERVIEW_AND_RELEASE_NOTES.HTM | ||
