Installation manual

Preparing to Use OpenVMS Management Station
G.1 Preparing Your OpenVMS System
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 seven versions.
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 devices.
G.1.7.1 When is the Database Updated?
The database is updated:
• As part of the OpenVMS Management Station installation.
• When you specifically invoke TNT$UTILITY.COM.
• At periodic intervals as a server background thread. Two logical names
control how often this server thread runs:
Logical Name Description
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 is running.
Preparing to Use OpenVMS Management Station G–5