HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
12.10 Analyzing Audit Log Files
The Audit Analysis utility (ANALYZE/AUDIT) enables system managers and site security administrators to selectively extract and display information from security audit log files. Using ANALYZE/AUDIT qualifiers, you can choose from among a variety of report formats and select the event criteria to be included in the report. Refer to the OpenVMS Guide to System Security for a description of how to use the utility.
|Specifying the location of the queue database||Section 13.3|
|Displaying information about queue managers||Section 13.4|
|Starting the queue manager and creating the queue database||Section 13.5|
|Customizing queue manager failover||Section 13.6|
|Stopping and restarting the queue manager||Section 13.7|
|Using multiple queue managers||Section 13.8|
|Saving and restoring the queue database||Section 13.9|
|Maximizing queuing system performance||Section 13.10|
|Solving queue manager problems||Section 13.11|
|Reporting a queuing system problem to Compaq||Section 13.12|
This chapter explains the following concepts:
|The queue manager||Section 13.1|
|The queue database||Section 13.2|
|Multiple queue managers||Section 13.8.1|
Note that this chapter contains many references to DCL commands. You
can find additional information about all DCL commands in the
OpenVMS DCL Dictionary.
13.1 Understanding the Queue Manager
To use a printer or batch processing on your system, you must use queues. The queue manager controls queue activity. The queue database consists of a master file as well as queue and journal files, which store information about queues and jobs.
Before you can perform any queue operation, you must start the queue manager and create the queue database. Section 13.5 contains instructions for doing this.
Figure 13-1 illustrates how the queue manager works to manage queue activity in an OpenVMS Cluster environment.
Figure 13-1 OpenVMS Batch and Print Queuing System
When a user submits a batch or print job to a queue, the queue manager performs the following tasks:
One or more queue manager processes control queuing for all processes on a node or in an OpenVMS Cluster environment. Jobs can be submitted from one node and executed on a queue running on another cluster node. User processes, symbionts, and job controllers on each node communicate directly with queue managers.
You can specify the order in which OpenVMS Cluster nodes claim the queue manager process; you can also limit the nodes that can run the queue manager. For more information, see Section 13.6.
To work around CPU, disk space, or memory limitations, you can use multiple queue managers to distribute the batch and print work load among nodes as well as to distribute the database files among disks.
For example, you might create separate queue managers for batch queues and print queues. Run the batch queue manager on one node and the print queue manager on a different node. You can also maintain queue and journal files on separate disks.
The queue database contains files that store information used to keep the queuing system operating, including information about jobs, queues, and the queue manager. The queue database for the default queue manager, SYS$QUEUE_MANAGER, is made up of the following files:
|Contains the queue definitions formed when you create, start, or modify queues.|
Contains information allowing the queue manager to return to the last
known state if:
The journal file also contains job definitions.
On systems with multiple queue managers, the queue database contains an additional queue file and journal file for each additional queue manager. Additional queue files are named in the format name_of_manager.QMAN$QUEUES. Additional journal files are named in the format name_of_manager.QMAN$JOURNAL.
Figure 13-2 shows a queue database containing a master file that lists two queue managers, PRINT_MANAGER and BATCH_MANAGER. Each queue manager has its own queue and journal files.
Figure 13-2 Queue Database
SYS$COMMON:[SYSEXE] is the default location for all queue database
files. However, you can store the files in another location. The next
section explains why and how to do this.
13.3 Specifying the Location of the Queue Database
You can move queue database files in either of the following ways:
Section 13.3.1 explains how to specify the location of the master file;
Section 13.3.2 explains how to specify the locations of queue and
13.3.1 Specifying the Location of the Queue Master File
To specify the location of the queue master file, perform the following steps before starting the queue manager:
DEFINE/SYSTEM/EXECUTIVE_MODE QMAN$MASTER equivalence-name
In an OpenVMS Cluster environment, the directory you specify for the master file must be available to all nodes in the cluster. If the directory specification is a concealed logical name, you must define it identically on all nodes in the cluster; you must also mount the disk on all cluster member nodes early in system startup.
$ START/QUEUE/MANAGER DUA2:[SYSQUE]
This command specifies that the queue and journal files are to be located in the directory DUA2:[SYSQUE].
In an OpenVMS Cluster environment, the directory you specify for the queue and journal files must be available to all nodes that can run the queue manager. If the directory specification is a concealed logical name, you must define it identically on all nodes in the cluster. You must also mount the disk on all nodes capable of running the queue manager.
The directory location you enter with START/QUEUE/MANAGER is stored in
the queue database master file and becomes the default. Therefore, if
you must restart the queue manager, you do not need to respecify this
13.4 Displaying Information About Queue Managers
$ SHOW QUEUE/MANAGERS Queue manager PRINT_MANAGER, running, on NODEA:: Queue manager SYS$QUEUE_MANAGER, running, on NODED::
$ SHOW QUEUE/MANAGERS/FULL Master file: SYS$SPECIFIC:[SYSEXE]QMAN$MASTER.DAT; Queue manager PRINT_MANAGER, running, on NODEA:: /ON=(NODEA,NODEB,*) Database location: DUA2:[SYSQUE] Queue manager BATCH_MANAGER, running, on NODED:: /ON=(NODEC,NODED,NODEE,*) Database location: SYS$SYSROOT:[SYSEXE]
Figure 13-3 shows the locations of the queue database files shown in the second example.
Figure 13-3 Locations of Queue Database Files
Before you can create queues, you must create a queue database by entering a command in the following format:
Specifies that new queue database files are to be created:
Specify the /NEW_VERSION qualifier only if you want to create new database files. If your queuing system is already functioning, creating new database files is not necessary.
|/ON= (node,...)||Allows you to customize failover of the queue manager. For more information, see Section 13.6.|
|dirspec||Specifies the location of the queue and journal files, as explained in Section 13.3.2. Use this parameter if you are creating the queue and journal files in a location other than the default.|
Specify the /NEW_VERSION qualifier only if you do not have a currently functioning queue database. If you specify this qualifier and you already have queue database files, the system overwrites your current queue database files.
The job controller automatically starts the queue manager during reboot unless you enter a STOP/QUEUE/MANAGER/CLUSTER command. For this reason, including START/QUEUE/MANAGER in your startup command procedure is unnecessary.
This section describes how to start the queue manager and create the queue database files on systems and clusters with a single system disk. For systems in a cluster with multiple system disks, including mixed-architecture OpenVMS Cluster systems, you must prepare a shared environment, as described in Chapter 5 of OpenVMS Cluster Systems.
If the queue manager does not start, see Section 13.11.1 for a troubleshooting checklist.
The following example specifies that:
$ DEFINE/SYSTEM/EXECUTIVE_MODE QMAN$MASTER DUA4:[MASTER] $ MOUNT/SYSTEM/NOASSIST DUA4: $ ! $ ! Add the two previous commands to SYLOGICALS.COM $ ! $ START/QUEUE/MANAGER/NEW_VERSION DUA2:[SYSQUE]
By default, all nodes in an OpenVMS Cluster environment are able to run
the queue manager, in no specified order of preference. The /ON
qualifier of the START/QUEUE/MANAGER command lets you specify a list of
OpenVMS Cluster member nodes in the order that they should claim the
queue manager process. Compaq recommends that you specify an asterisk
(*) at the end of the node list to make sure that at least one node is
always available to run the queue manager.
13.7 Stopping and Restarting the Queue Manager
To stop and restart the queue manager, you need to enter DCL commands.
13.7.1 Stopping the Queue Manager
To shut down the queue manager on a standalone node or an OpenVMS Cluster node, enter the following command:
The queue manager performs the following tasks:
Once you enter STOP/QUEUE/MANAGER/CLUSTER, the queue manager process remains stopped; requests to that queue manager are denied until you restart the queue manager by entering START/QUEUE/MANAGER. (Note that the queue system remains running as long as one or more queue managers are running.)
OpenVMS Cluster transitions do not change the state of the queue manager. Newly available nodes do not attempt to start the queue manager (unless you enter START/QUEUE/MANAGER).
Use the /CLUSTER qualifier to stop a clusterwide queue manager. If you enter the obsolete command STOP/QUEUE/MANAGER (without the /CLUSTER qualifier), the command performs the same function as STOP/QUEUES/ON_NODE. (Use STOP/QUEUES/ON_NODE to stop all queues on a single node without stopping the queue manager.)