How Are the Systems to be Managed Organized?

You use OpenVMS Management Domains to group OpenVMS systems.

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.

Once you have created your management domain, you can manage the user accounts on the systems in the domain.

What is the Scope of an Operation?

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 operation 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.

Avoid Surprises

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.

In the following example, if you create a user account for the Entire Building OpenVMS Management Domain object, that account is created for the SITAR and PCAPT clusters that comprise the First Floor OpenVMS Management Domain and for the node MYNODE.

If you create the same account for the First Floor OpenVMS Management Domain, the account is created for the SITAR and PCAPT clusters but not for MYNODE.

Choosing a Transport

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, your PC and other OpenVMS systems will use the DECnet transport when communicating with this system. If you choose TCP/IP, that transport is used instead. Note that Windows NT and Windows 95 support TCP/IP connections only.

For TCP/IP connections, OpenVMS Management Station then uses the existing Windows Sockets V1.1 Dynamic Link Library (WINSOCK.DLL) and TCP/IP stack on your PC to establish connections to your OpenVMS systems.

OpenVMS Management Station should work with any Windows Sockets V1.1 compliant WINSOCK.DLL.

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.

What About Compatibility With Previous Versions?

If you install Version 2.1 of the client software on your PC, install Version 2.1 of the server on all of the OpenVMS systems that you want to manage. Upgrading both the client and server software to Version 2.1 ensures the best compatibility and ease of use.

What About Existing Management Domains?

• Version 2.1 of OpenVMS Management Station is compatible with the management domains created with Version 1.5 of OpenVMS Management Station. No changes to the existing management domains are required.
• If you are using any version of OpenVMS Management Station prior to Version 1.5, you must re-create your OpenVMS Management Domain for use with Version 2.1.
  
  Note that you can use your existing management domain if you are willing to perform some customization, as described in the Release Notes section of this document.

Are There Restrictions on the Systems in an OpenVMS Management Domain?

You can manage any number of OpenVMS Cluster or node objects, with the following conditions:

1. Managing cluster members as individual nodes is not supported. OpenVMS Cluster systems are treated as indivisible entities; you can't perform an operation on individual cluster members.
2. Creating nodes in a cluster or deleting them from a cluster is not supported.
3. Clusters with multiple user authorization files (UAFs) are not supported.

Does OpenVMS Management Station Work With PATHWORKS and ManageWORKS Workgroup Administrator?

You do not need the PATHWORKS client software to run OpenVMS Management Station. OpenVMS Management Station installs into its own directory and includes all of the ManageWORKS components it needs to run.

If you happen to have PATHWORKS or ManageWORKS Workgroup Administrator installed, both will continue to function independently of OpenVMS Management Station.

Configuring Under PATHWORKS or ManageWORKS Workgroup Administrator

You can configure PATHWORKS or the ManageWORKS Workgroup Administrator to load the OpenVMS Management Station software if you want to. This process is described in the installation guide. OpenVMS Management Station works with the following specific ManageWORKS versions:

• PATHWORKS V5.1 for DOS and Windows client software
• ManageWORKS Workgroup Administrator, Version 2.2

Note: PATHWORKS for Windows 95 is not supported.

PATHWORKS and DECnet

OpenVMS Management Station does not have any DECnet dependencies and can run in a TCP/IP-only environment. If you do want to use DECnet connections, PATHWORKS V5.1 for DOS and Windows must be installed somewhere on the PC and must be listed in the PC's PATH statement.

Note that when running under Windows NT and Windows 95, OpenVMS Management Station supports TCP/IP connections only.

3

How to Get Started

The OpenVMS Management Station help file contains a complete example, including a walk-through, of how to get started with OpenVMS Management Station.

This chapter describes how to create a simple OpenVMS Management Domain consisting of one OpenVMS Cluster system. The chapter also describes how to manage user accounts and printers 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.

Getting Started Steps

1. Open the OpenVMS Management Station program group and click on the OpenVMS Management Station icon.

The main Viewer dialog box is displayed.

2. Select (single click on) the OpenVMS Management Domain in the viewer.

3. Click on Expand in the toolbar to reveal the contents of the OpenVMS Management Domain.

4. Choose Create from the Actions menu. (The OpenVMS Management Domain object is already selected.)

5. Select (single click on) OpenVMS Cluster or OpenVMS Node from the Create dialog box and click OK. If you have both OpenVMS Cluster systems and nonclustered nodes in your environment, you can choose either one. (You can also select an OpenVMS Management Domain, but ignore this option for now to simplify the example.)

6. 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.) Specify your user name and accept the default for the Primary Server control.

If you select the DECnet transport, your PC must have the network name and address of this OpenVMS Cluster system or OpenVMS node defined in its DECnet database.

If you select the TCP/IP transport, your hosts file or name server must be able to resolve the IP name or address. See the online help for additional TCP/IP information.

7. Select (single click on) the OpenVMS Accounts object, and click on

Expand in the toolbar to display a list of user accounts.

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 (single click on) an OpenVMS User Accounts object.

10. Click on in the toolbar to display the account attributes for that user account.

11. Take some time to see how the account attributes are presented. When you are done, click Cancel to return to the viewer.

12. Select (single click on) the OpenVMS Printers object .

13. Click on in the toolbar to display the available printers for this system.

14. Select (single click on) an OpenVMS Printer object .

15. Click on in the toolbar to display the printer attributes. Again, take some time to see how the attributes are displayed.

The hyperjump buttons are a powerful feature. Be sure to read about them in the OpenVMS Printer Management help file!

What's Next?

Examine how the account and printer 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 on the tabs at the top of the dialog box to examine other attributes. You can switch between attribute groups and make changes anywhere.

You can click OK to make changes and return to the viewer, Apply Now to make changes without returning to the viewer, or Cancel to return to the viewer without making any changes.

A Word About Selecting Multiple User Accounts or Printers

You can use OpenVMS Management Station to easily select multiple user accounts or printers in one or more OpenVMS Management Domains. For example, you can open three domains and select one OpenVMS User object from each domain. You can then perform operations on all of the selected objects or on particular objects.

Perform the following steps to select multiple user accounts. The steps are similar for selecting multiple printers.

1. To select sequential user accounts, click on the first OpenVMS User object that you want to select. Press and hold the Shift key while you click on the last OpenVMS User object that you want to select.

To select nonsequential user accounts, press and hold the Ctrl key while you click on the objects you want to select.

To cancel a selection, press and hold the Ctrl key while you click on the selected object.

2. Choose Properties (zoom) from the Actions menu, or from the toolbar, to zoom on the accounts. The account characteristics dialog box contains the attributes for the first user account you selected.

3. When you make changes, you can choose either Apply to apply changes to one account or Apply to All to apply the changes to all of the selected accounts.

4

Release Notes

This chapter contains important information regarding the OpenVMS Management Station software that is not described in the installation guide or in online help. Read this chapter before you begin using OpenVMS Management Station.

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 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.

32-Bit ManageWORKS

Version 2.1 of OpenVMS Management Station is a 16-bit application and is not compatible with any future 32-bit version of ManageWORKS.

Existing Version 1.5 Management Domains Are Used

Version 2.1 of OpenVMS Management Station is compatible with the management domains created with Version 1.5 of OpenVMS Management Station. No changes to the existing management domains are required.

If you are using a version of OpenVMS Management Station prior to Version 1.5, you must re-create your OpenVMS Management Domain for use with Version 2.1.

Note that you can use your existing management domain if you are willing to perform some customization.

1. First, copy the following files from your existing OpenVMS Management Station installation ( most likely in the PATHWORKS or ManageWORKS Workgroup Administrator directory) to your new OpenVMS Management Station directory (most likely \VMSTNT):
   
   CLASS.IDX
   CLASS.POD
   CONTAIN.IDX
   CONTAIN.POD
   OBJECT.IDX
   OBJECT.POD
2. Open your management domain and look for "Unknown Object" errors. Version 2.1 of OpenVMS Management Station expects to find only known objects, such as the OpenVMS Management Domain object , the OpenVMS Cluster object , and so forth. All other objects you might have created with ManageWORKS will be unknown.
   
   Delete the unknown objects from this copy of the database.

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.

Updating the Viewer After Changes to OpenVMS Accounts and Printers

The OpenVMS User and Printer objects that are displayed after expanding the OpenVMS Accounts and OpenVMS Printers objects are a snapshot of the accounts and printers on the systems at the time the expand action was performed. As such, any changes you make using the zoom, create, delete, rename, start, stop, and other features of OpenVMS Management Station are not represented in the snapshot.

If you want to see the latest changes in the viewer, collapse and expand the OpenVMS Accounts and OpenVMS Printers objects to retrieve the updated information.

This requirement also applies to any changes, additions, or deletions you or anyone else makes to the systems with either the OpenVMS AUTHORIZE utility or DCL while the accounts and printers are displayed in the viewer.

Known Problems and Restrictions

This section details known problems in the OpenVMS Management Station software.

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 indicates 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.

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 via OpenVMS Management Station, applications such as DFS (prior to Version 2.0) and DECnet Phase IV (components such as 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.

Stack Fault in Module USER.EXE

There is a known, although rare, problem that might occur when you try to run the OpenVMS Management Station client.

If you receive the "PWMGMT caused a stack fault in module USER.EXE" error when you try to run OpenVMS Management Station, restart Windows. Then, add the following entry to the [Setup] section of the PWMGNT.INI file (usually in \VMSTNT):

Init3d=0

Once you have done this, run OpenVMS Management Station.

Undefined Dynalink/Program Error

If you receive an

Undefined Dynalink

or

Program Error -- Your program is making an invalid dynamic link to a .DLL file.

error when you try to start OpenVMS Management Station, it's likely that you have a second, incompatible version of the file MFC250.DLL in your path.

The OpenVMS Management Station installation installs this file in your Windows system directory (WINDOWS\SYSTEM, WINNT35\SYSTEM, and so forth). If you find any other version of this file in your path, rename this incompatible version to MFC250.OLD.

Stack Fault

If you receive a stack fault when using OpenVMS Management Station, it's likely that you have a second, incompatible version of the file CTL3DV2.DLL in your path.

The OpenVMS Management Station installation installs this file in your Windows system directory (WINDOWS\SYSTEM, WINNT35\SYSTEM, and so forth). If you find any other version of this file in your path, rename this incompatible version to CTL3DV2.OLD.

Blank Property Page

If you switch between property pages and a property page is blank, it's likely that you have a second, incompatible version of the file CTL3DV2.DLL in your path.

The OpenVMS Management Station installation installs this file in your Windows system directory (WINDOWS\SYSTEM, WINNT35\SYSTEM, and so forth). If you find any other version of this file in your path, rename this incompatible version to CTL3DV2.OLD.

Pressing Properties in Rapid Succession Causes a Stack Overflow

If you press the properties button on any OpenVMS object in rapid succession, a stack overflow occurs. You must restart Windows before you can run OpenVMS Management Station.

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 Creation Problem

When creating a printer at the OpenVMS Management Domain level, device overrides do not work properly. To work around this problem, first create the printer and then use Properties from the Actions menu to modify the device characteristics.

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 thye OpenVMS Management Domain level based on a reference printer accessed via 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 Name 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.

Uninstall Does Not Work with Windows for Workgroups

The client uninstall program does not work with the Windows for Workgroups platform. If you try to run the uninstall, the following error is displayed:

Error setting_ISDEL.EXE normal attribute

To complete the uninstallation, use the File Manager or the DOS DELTREE command to delete the entire /VMSTNT directory tree.

Drag and Drop Job Requeue Fails for Reconciled Printers at Domain Level

If you try to "drag and drop" requeue more than one printer job from a reconciled printer at the OpenVMS Management Domain level, the requeue fails. You can use either of the following workarounds for this problem:

• Do not drag and drop printer jobs at the OpenVMS Management Domain level. Instead, select an OpenVMS Cluster or OpenVMS Node object, expand that object to show the jobs you want to requeue, and then perform the requeue operation.
• Use the Requeue item from the Actions menu to requeue the jobs.

  6403OVER.HTML
  OSSG Documentation
  22-NOV-1996 13:06:42.07

Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

Legal