HP OpenVMS Systems Documentation
OpenVMS VAX Version 7.3
OpenVMS Management Station writes error log information to the file
TNT$SERVER_ERROR.LOG. This error log is created in the
SYS$SPECIFIC:[SYSEXE] directory. If you start the OpenVMS Management
Station server on multiple nodes in a cluster, which is recommended,
there will be multiple server error logs.
G.1.4 Update the Printer and Storage Database
When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node. If this installation was an upgrade, the server converts the existing OpenVMS Management Station database to the V3.0 format. If this was a new installation, the server creates an initial version of the database file TNT$ACS.DAT and invokes the update functions automatically.
To complete the database, start the OpenVMS Management Station server
on each node in your cluster. The instances of the server communicate
with each other to determine device, queue, and volume information, and
the server must be running on each node for this communication to take
G.1.5 Edit the System Files
To start the OpenVMS Management Station server from your system startup files, insert one of the following commands into your system startup procedures (probably SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but immediately prior to the ENABLE AUTOSTART/QUEUES.
Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station.
OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started.
|Command||Parameter 1||Parameter 2||Description|
|@TNT$STARTUP||blank||N.A.||Starts the server. Does not start printer queues or mount volumes.|
|@TNT$STARTUP||RESTART||N.A.||Shuts down a running server, then starts the server. Does not start printer queues or mount volumes.|
|@TNT$STARTUP||BOOT||blank||Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station.|
|@TNT$STARTUP||BOOT||ALL||Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station.|
|@TNT$STARTUP||BOOT||PRINTERS||Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station.|
|@TNT$STARTUP||BOOT||STORAGE||Starts the server. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station. Does not start any printer queues.|
Note that the effect of TNT$STARTUP BOOT, with no second parameter, has not changed from earlier releases. This command starts any printer queues that are not yet started and are managed by OpenVMS Management Station, but does not mount any volumes.
Add the following command line to the system shutdown file,
It is not necessary to remove your existing queue startup and volume mount DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue or mounted a volume with your command procedures and will assume that you want it that way.
As you become familiar with the server's management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer and storage environment.
In addition, the OpenVMS Management Station server periodically (every 24 hours) 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 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 name of the generated file is TNT$EMERGENCY_MOUNT.COM. TNT$EMERGENCY_MOUNT.COM is created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if that logical name exists.
The OpenVMS Management Station server limits TNT$EMERGENCY_MOUNT.COM to
G.1.7 Keeping Your Printer Environment Up to Date
The OpenVMS Management Station server installation creates a file named
SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS
system and updates the database of known printers, queues, and related
G.1.7.1 When is the Database Updated?
The database is updated:
|TNT$PRINTER_RECON_INTERVAL||How often the thread should run, in minutes, from when the server was last started on this node. If you do not define this logical, the default value is 1440 minutes (24 hours).|
|TNT$PRINTER_RECON_INTERVAL_MIN||The minimum number of minutes that must elapse before the thread should run again, starting from when the database was last updated. If you do not define this logical, the default value is 60 minutes (1 hour).|
You can think of these logicals as meaning "run the thread this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN)."
Because you can run TNT$UTILITY.COM yourself, and because the OpenVMS Management Station server also updates the database, the TNT$PRINTER_RECON_INTERVAL_MIN logical prevents the database from being updated more frequently than is actually needed.
If you want to change the defaults for one of these logicals, define
the logical on all nodes on which the OpenVMS Management Station server
G.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually?
If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM.
However, if you or someone else uses DCL to make a change --- for example, if you use the DELETE /QUEUE command to delete a queue --- the configuration files will not be synchronized. In this case, the OpenVMS Management Station client will advise you to run TNT$UTILITY.COM to resynchronize the database.
Run the following procedure on one node in the cluster to make the database match your system:
$ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS
For example, if you or someone else used DCL to delete a queue, you
need to delete that queue from the database. TNT$UTILITY.COM assumes
that your system is set up and running the way that you want it to, so
you should fix any problems before you run TNT$UTILITY.COM.
G.1.7.3 Are There Any Requirements for Running TNT$UTILITY.COM?
You need the SYSNAM privilege to run TNT$UTILITY.COM.
TNT$UTILITY.COM connects to the OpenVMS Management Station server on the current OpenVMS system to determine device and queue information. Therefore, the OpenVMS Management Station server must be running on the node where you run TNT$UTILITY.COM.
The OpenVMS Management Station server then connects to the other OpenVMS Management Station servers in the OpenVMS Cluster to determine device and queue information. It is generally a good idea to keep the OpenVMS Management Station server running on the other nodes in an OpenVMS Cluster to keep the database up to the minute.
However, if the OpenVMS Management Server is not able to connect to the
OpenVMS Management Station server on a given node, it uses the known
information about that OpenVMS node from the database. That is, in the
absence of a valid connection to that OpenVMS node, the information in
the database is assumed to be correct.
G.1.8 Keeping Your Storage Environment Up to Date
The TNT$UTILITY.COM utility accepts parameters (UPDATE STORAGE) to
update the storage database. However, the storage database is updated
dynamically every time you use the OpenVMS Management Station client to
perform a storage management operation. Therefore, you do not need to
run TNT$UTILITY.COM to update the storage database.
G.1.9 Enabling Disk Quotas
Before installing OpenVMS Management Station, you might have disabled disk quotas on the SYSTEM disk. If so, you should reenable the quotas and then rebuild to update quota information by entering the following commands:
$ RUN SYS$SYSTEM:DISKQUOTA DISKQUOTA> ENABLE DISKQUOTA> REBUILD DISKQUOTA> EXIT
OpenVMS Management Station uses two logical names to determine how often to refresh cached (in-memory) storage configuration data.
min = 180 default = 1800 (30 minutes) max = 18000 (5 hours)
min = 6 default = 60 (1 minute) max = 600 (10 minutes)
For both logical names, smaller values result in the OpenVMS Management Station server consuming more CPU cycles in periodic purges or surveys.
If you do not accept the defaults, you might find that larger OpenVMS Cluster systems behave better with values on the high end of the allowed range.
If you do not define these logicals, the OpenVMS Management Station
server uses the default values. If you do define these logical names,
the values are used only if they are within the minimum to maximum
G.1.11 Running Third-Party TCP/IP Stacks
Compaq TCP/IP Services for OpenVMS Version 3.2 or higher is the only supported TCP/IP stack. Additional stacks have not been tested. However, TCP/IP stacks that are 100 percent 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.)
For the best chance of success, check the following:
If you encounter a problem while using OpenVMS Management Station, please report it to Compaq. Depending on the nature of the problem and the type of support you have, you can take one of the following actions:
If you use the POLYCENTER Software Installation utility to remove OpenVMS Management Station from the OpenVMS system, the following files are not removed:
Do not delete these files unless you have already removed OpenVMS
G.2 Preparing Your PC
During the OpenVMS installation or upgrade procedure, you selected the OpenVMS Management Station client software files to be installed on your OpenVMS system disk (or you added them later using the DCL command PRODUCT INSTALL TNT). After you have prepared your OpenVMS system to run the server software, you must next prepare your PC to run the client software.
This section includes the following information:
Your PC requires 13 MB of free disk space to install the OpenVMS Management Station
G.2.2 Distribution Files
There are two versions of the OpenVMS Management Station client kit: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and TNT030_A.EXE for Alpha Windows NT systems. Both of these files are located in the SYS$COMMON:[TNT.CLIENT] directory.
The Intel kit will not install under FX!32 running on Alpha processors;
use the Alpha native kit in this case.
G.2.3 Required Software
Microsoft Windows NT Versions 4.0 (Service Pack 3 or higher) or Windows 95 or higher (Intel only) must be installed on each PC on which you want to install the OpenVMS Management Station client.
The version of MMC included in this baselevel requires files provided
by Microsoft Internet Explorer. Version 3.02 or later of Internet
Explorer must be present on the system.
G.2.4 Time Required for Installation
The time required to install the OpenVMS Management Station client software is
approximately 5 minutes.
G.2.5 Copy the Client File to the PC
The client files TNT030_I.EXE (Intel) and TNT030_A.EXE (Alpha) are located in the SYS$COMMON:[TNT.CLIENT] directory. Copy either client file to a temporary directory the PC using any of the following procedures:
The installation procedure allows you to select the installation
directory, and suggests \Program Files\OpenVMS Mgmt Station\ as the
G.2.7 Installation Procedure
Run TNT030_I.EXE (Intel) or TNT030_A.EXE (Alpha) from a temporary
directory. These are self-extracting executable files that automate the
OpenVMS Management Station installation.
G.2.8 Recovering from Errors
If an error occurs during installation, you will receive an error message describing the problem. This information can help you determine the cause of the problem. An error can occur during the installation if one or more of the following conditions exist:
When you create an OpenVMS Cluster or OpenVMS Node object in an OpenVMS Management Domain, you select the transport you want to use for all connections to that system. You can choose DECnet Phase IV for OpenVMS VAX or TCP/IP.
OpenVMS Management Station uses this transport for all communications between the PC and this system, or between any other OpenVMS system that is running the OpenVMS Management Station server and this system.
The OpenVMS Management Station client supports only TCP/IP connections for primary servers. That is, the connection between the PC and the OpenVMS system uses only TCP/IP. Therefore, at least one OpenVMS system must be running TCP/IP.
You do need to make sure that your PC can connect to the primary-server
systems, as described in the following sections. OpenVMS Management Station connects
your PC to the primary-server system and then routes management
operations to the target systems.
G.4 Defining TCP/IP Nodes
Your hosts file or name server must be able to resolve the IP name or
address of all primary-server systems. If you can successfully ping the
primary-server systems from your PC, then this condition is met.
G.5 Uninstalling Version 2.1 of the OpenVMS Management Station Client
Version 3.0 of the OpenVMS Management Station client is not dependent
on Version 2.1 and does not share any files with this prior version.
After installing the Version 3.0 client, you can uninstall the Version
2.1 client software.
G.6 Uninstalling OpenVMS Management Station
If you need to uninstall the OpenVMS Management Station client software, make sure you first exit OpenVMS Management Station. The uninstallation fails if OpenVMS Management Station is currently running.
If you run the OpenVMS Management Station Help, the following files might be created:
The OpenVMS Management Station Uninstall program does not delete these files. To complete the uninstall:
Note that the OpenVMS Management Station Uninstall program does not
uninstall the Microsoft Management Console (MMC) support files.
G.7 Getting Started with OpenVMS Management Station