HP OpenVMS 8.x manual When Is the Database Updated?

G.1.7.1 When Is the Database Updated?

The database is updated:

•As part of the OpenVMS Management Station installation.

•When you specifically start 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.

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 the TNT$UTILITY.COM procedure.

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 are not synchronized. In this case, the OpenVMS Management Station client tells you to run the TNT$UTILITY.COM procedure 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 uses DCL to delete a queue, you need to delete that queue from the database. The TNT$UTILITY.COM procedure 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 What Are the Requirements for Running TNT$UTILITY.COM?

You need the SYSNAM privilege to run TNT$UTILITY.COM.

The TNT$UTILITY.COM procedure 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

G.1 Preparing Your OpenVMS System 261