![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
New files that the procedure installs at a version number higher than your existing files are referred to as new_over files. You must use these files at least until you complete the upgrade. After you have upgraded your system, you can add your customizations to these files.
New files installed at a version number lower than the existing files are referred to as new_under files. This allows you to continue to use your existing files during and after the upgrade.
If you purge a new_over file, you are left with the new version of the file provided by the distribution kit, and any customizations you might have made to the existing file will be lost. If you purge a new_under file, you are left with the file that existed before the upgrade.
In addition to the new_over and new_under files, there are certain files that are intended to contain your site-specific modifications. During an upgrade, the old versions of these files are retained if they were present before the upgrade. The new version of the file is installed only if no old version is present on your system. With the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of the site-specfic files. The new version of the .TEMPLATE file replaces the old version.
During an upgrade, the following new files are installed over (that is, at a version number higher than) the existing files:
During an upgrade, the following new files are installed under (that is, at a version number lower than) the existing files:
The following files are intended to contain site-specific modifications. Note that, with the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of these files. The new version of the .TEMPLATE file replaces the old version.
This appendix describes how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software.
The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows.
During the OpenVMS VAX installation or upgrade procedure, the OpenVMS Management Station server files are automatically installed on your OpenVMS system disk. However to obtain complete support, you must also select the OpenVMS Management Station client software files during the OpenVMS installation or upgrade procedure. Those files are required to create the installation media that you use to install the client software on your PC.
If you did not select the OpenVMS Management Station component during the installation or upgrade, you must add those files to your OpenVMS system disk before you follow the instructions in this appendix. Use the OpenVMS VAX distribution media and VMSTAILOR to add the OpenVMS Management Station files to your system. (For information about using VMSTAILOR, see Chapter 10.)
You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following:
The following files are created on your OpenVMS system when the OpenVMS Management Station server is installed:
These optional files are created when you install PC installation media files:
These files are created when the server is started:
The OpenVMS Management Station server creates three main configuration files:
In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required.
However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks.
Rules: The following rules apply:
Follow these steps to coordinate files:
$ DEFINE/SYSTEM/EXEC TNT$ACS - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT $ DEFINE/SYSTEM/EXEC TNT$UADB - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT $ DEFINE/SYSTEM/EXEC TNT$JOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL
$ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM - _$ $1$DJA16: volume-label
If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes. Enter the following command:
$ @SYS$STARTUP:TNT$STARTUP.COM
If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows:
$ @SYS$STARTUP:TNT$STARTUP.COM RESTART
When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node and created an initial version of the printer database file TNT$ACS.DAT. However, this initial version of the database might not contain complete device and queue information for your OpenVMS Cluster system.
To complete the database, first start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device and queue information, and the server must be running on each node for this communication to take place.
Once you have started the server on each node, run the following procedure to update the printer database:
$ @SYS$STARTUP:TNT$UTILITY UPDATE PRINTERS
To start the OpenVMS Management Station server from your system startup files, insert the following line into your system startup procedures (usually SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but before ENABLE AUTOSTART/QUEUES.
$ @SYS$STARTUP:TNT$STARTUP BOOT
(The best place for this is immediately prior to the ENABLE AUTOSTART/QUEUES command.)
Note
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.
Add the following command line to the system shutdown file,
SYS$MANAGER:SYSHUTDWN.COM:
$ @SYS$STARTUP:TNT$SHUTDOWN.COM
Placing the server startup before ENABLE AUTOSTART/QUEUES in the system startup procedure allows the server to start any queues not already started by your existing DCL command procedures.
It is not necessary to remove your existing queue startup DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue 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 environment.
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 devices. TNT$UTILITY.COM runs at regular intervals to keep the database files synchronized with the actual system.
The TNT$UTILITY.COM procedure runs:
| Logical Name | Description |
|---|---|
| TNT$PRINTER_RECON_INTERVAL | How often TNT$UTILITY.COM 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 TNT$UTILITY.COM 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 TNT$UTILITY.COM 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 is running.
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. TNT$UTILITY.COM runs at periodic intervals as a background thread to make sure that the database is kept up to date.
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.
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.
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
Digital 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% compliant with the QIO interface for 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 Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions:
During the OpenVMS Version 7.1 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 RECONFIGURE VMS). 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 8 MB of random-access memory (RAM) and 11.5 MB of free disk space to install the OpenVMS Management Station client software.
Table G-1 describes the software that must be installed on your PC before installing OpenVMS Management Station.
| Prerequisite Products | Purpose |
|---|---|
|
Microsoft Windows NT Version 3.51
or Microsoft Windows 95 or Microsoft Windows Version 3.1 or Microsoft Windows for Workgroups Version 3.11 |
Operating system |
| Optional Products | Purpose |
| PATHWORKS Version 5.1 for DOS and Windows client software |
Integrate with PATHWORKS,
DECnet support |
|
ManageWORKS Workgroup
Administrator, Version 2.2 |
ManageWORKS integration |
| Your TCP/IP stack | IP connections |
PATHWORKS for Windows 95 and any version of Windows NT prior to Version 3.51 are not officially supported.
If Version 1.0 of TeamLinks is installed on your PC, the OpenVMS Management Station PC installation program will ask whether to update the XTI library component of TeamLinks.
If you answer No, the OpenVMS Management Station installation terminates. However, if you allow OpenVMS Management Station to update the XTI library, Version 1.0 of TeamLinks will no longer work.
The version of the XTI library included with Version 1.0 of TeamLinks does not allow TCP/IP connections from your PC and is not supported in this version of OpenVMS Management Station. If you want to utilize both TCP/IP connections and TeamLinks, you must upgrade to a higher version of TeamLinks.
Create the PC installation media using the following procedure.
Note: You need six formatted 3-1/2-inch, high-density floppy disks.
C:\> cd temp-dir C:\temp> ftp ftp> open node Connected to node Username: username Password: password User logged in. ftp> cd sys$common:[tnt.client] ftp> type bin ftp> mget *.*
C:\> NFT COPY /BLOCK node"username password"::SYS$COMMON: [TNT.CLIENT]*.* \temp-dir
C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID1.IMG A:
This section provides the following information:
The installation procedure allows you to select the installation directory, and suggests \VMSTNT as the default.
Do not install OpenVMS Management Station into the PATHWORKS or ManageWORKS Workgroup Administrator directories. If you do want to configure PATHWORKS or ManageWORKS Workgroup Administrator to load OpenVMS Management Station, see Section G.2.7.
A:\SETUP.EXE
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:
The following files (with their directory names) are created on your PC after the OpenVMS Management Station client software is installed:
OpenVMS Management Station allows you to use both the TCP/IP and DECnet transports to establish connections.
You can have a mix of DECnet and TCP/IP connections, all DECnet connections, or all TCP/IP connections. OpenVMS Management Station does not have any DECnet dependencies and can run in a TCP/IP-only environment. Note that Windows NT and Windows 95 support TCP/IP connections only.
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.
If you select the TCP/IP transport, your host's 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.
If you want to use DECnet connections, PATHWORKS Version 5.1 for DOS and Windows must be installed somewhere on the PC and listed in the PC's path statement.
6487P013.HTM OSSG Documentation 9-DEC-1996 10:54:22.62
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.