|Document revision date: 30 March 2001|
When monitoring jobs, you might see a print job that is pending in a queue because the stock does not match that of the mounted form. For example, you might see a SHOW ENTRY display similar to the following one:
$ SHOW ENTRY 133/FULL Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 133 SET RANDOM 74 Pending (stock type mismatch) On idle printer queue SUE$PRINT Submitted 21-JAN-2000 16:14 /FORM=MANUAL (stock=HQ) /PRIORITY=100 File: _$5$DUA1:[RANDOM]SET.TXT;5
To fix jobs that are pending because of a stock mismatch, perform one or more of the following actions:
See Section 14.6.7 for more information about forms.
126.96.36.199 Fixing Jobs That Are Pending Because of Characteristics Mismatch
When monitoring jobs, you might see a batch or print job that is pending in a queue because the characteristics do not match those assigned to the queue. For example, you might see a SHOW ENTRY display similar to the following one:
$ SHOW ENTRY 882/FULL Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 882 SETHOST RANDOM 5 Pending (characteristics mismatch) On idle printer queue $PRINTER_1 Submitted 28-MAR-2000 15:21 /CHAR=(5) /FORM=DEFAULT /PRIORITY=100 File: _$5$DUA1:[RANDOM]SETHOST.LOG;5
To fix jobs that are pending because of a characteristics mismatch, perform one or more of the following actions:
See Section 14.6.3 for more information about characteristics.
14.8.3 Fixing a Stalled Output Queue
If an output queue is in the stalled state, the device on which the queue is running is malfunctioning. Check the device and fix the problem. Once the problem is fixed, the queue will leave the stalled state.
If you cannot fix the problem immediately, stop the queue by entering
STOP/QUEUE/RESET. While the queue is stopped, you might want to reroute
the jobs in the queue to a functioning queue, as explained in
Section 188.8.131.52. When the problem is fixed, deassign the logical queue
and start the queue by entering START/QUEUE.
14.8.4 Determining Why an Autostart Queue Does Not Start
If you attempt to start an autostart queue with ENABLE AUTOSTART/QUEUES and the queue does not start, the queue might not be active for autostart. ENABLE AUTOSTART/QUEUES starts only active autostart queues capable of running on a node. To activate an autostart queue, you must include the /START qualifier with INITIALIZE/QUEUE or enter START/QUEUE.
The numbers in following list correspond to numbers in the example:
If you are having problems deleting a queue, form, or characteristic, make sure you have met the following requirements:
If you see a message similar to the following one, a reference to the queue, form, or characteristic still exists:
%DELETE-E-NOTDELETED, error deleting object-name -JBC-E-REFERENCED, existing references prevent deletion
For example, the queue you are attempting to delete might be named as a target for a generic queue, or the form you are attempting to delete might be specified for a print job. All references to a queue, form, or characteristic must be removed before you can delete the queue, form, or characteristic.
How to Perform This Task
Perform the following steps to find and remove references to a queue, form, or characteristic:
The following example includes several commands used to fix problems preventing the deletion of a queue:
$ DELETE/QUEUE JADE_BATCH(1) %DELETE-E-NOTDELETED, error deleting JADE_BATCH -JBC-E-QUENOTSTOP, queue must be stopped to perform operation(2) $ STOP/QUEUE/NEXT JADE_BATCH(3) $ DELETE/QUEUE JADE_BATCH(4) %DELETE-E-NOTDELETED, error deleting JADE_BATCH(5) -JBC-E-REFERENCED, existing references prevent deletion $ SHOW QUEUE/FULL . . . Generic batch queue CLUSTER_BATCH(6) /GENERIC=(JADE_BATCH,RUBY_BATCH,OPAL_BATCH) /OWNER=[SYSTEM] /PROTECTION=(S:M,O:D,G:R,W:R) . . . $ STOP/QUEUE/NEXT CLUSTER_BATCH(7) $ START/QUEUE CLUSTER_BATCH/GENERIC=(RUBY_BATCH,OPAL_BATCH)(8) $ DELETE/QUEUE JADE_BATCH(9)
The commands this example perform the following tasks:
To delete a file using the PRINT/DELETE or SUBMIT/DELETE command, the clusterwide queue manager process must have access to the file specified. Otherwise, the file is printed or submitted but not deleted.
You can ensure that the PRINT/DELETE or SUBMIT/DELETE command deletes the specified files by mounting the disks on which the files reside clusterwide. To mount a disk clusterwide, use the /CLUSTER qualifier with the MOUNT command.
However, if your operating environment does not allow you to mount a
disk clusterwide, you can resolve this problem by running the queue
manager process on a node that has access to the disk. You can specify
the node on which the queue manager process runs by specifying the
/ON=node qualifier with the START/QUEUE/MANAGER command. For
more information about this qualifier, refer to the OpenVMS DCL Dictionary.
14.8.7 Adding or Deleting a Device Control Library Module
When attempting to add or delete a device control library module, you might see the following message:
$LIBRAR-F-OPENIN, error opening module-name -RMS-E-FLK, file currently locked by another user
To add or delete a library module, you must stop all output queues to which the library is assigned. To determine which queues the library is assigned to, perform the following steps:
where filespec is the name of a file to which the display output of the command is to be sent.
The result of your search will include all queues to which that library is assigned. Stop the queues and reenter the command to add or delete the library module.
The SHOW QUEUE/FULL display shows the library assigned to a queue only if you explicitly assigned a library for the queue by including the /LIBRARY qualifier with INITIALIZE/QUEUE or START/QUEUE. If you do not explicitly assign a library to a queue, the default library, SYSDEVCTL, is used.
If the module you are trying to delete is in the default library, SYSDEVCTL, you must stop all queues for which SHOW QUEUE/FULL displays no library. To make sure the SYSDEVCTL library appears in the SHOW QUEUE/FULL display in the future, specify /LIBRARY=SYSDEVCTL when you restart the queue.
If you cannot stop the queues immediately, perform the following steps:
If your site has a large number of different printers, you can help
prevent this problem by using more libraries, so that each library is
assigned to fewer queues. For example, you should create and assign a
different library for each type of printer, as explained in
14.8.8 Fixing a Disabled Queue
The queue manager attempts to correct any kind of corruption detected. If the queue manager detects corruption in a queue record, it might disable a queue to isolate the corruption. When a queue is disabled, the following message is written on the console and in the operator log file:
%QMAN-I-QUEDISCOR, queue 'queue_name' has been disabled due to database corruption
When a queue is disabled, any attempt to modify or submit a job to it returns the following message:
%JBC-E-QUEDISABLED, disabled queue cannot be modified, nor can a job be submitted to it
If you see either of the previous messages, perform the following actions:
If you encounter a problem with your queues, and you want to report it to Compaq, please provide as much information as possible. Section 13.12 specifies the information that is most useful to Compaq in diagnosing your queuing system problems.
When your system is installed or upgraded, values of system parameters are automatically set by the command procedure SYS$UPDATE:AUTOGEN.COM (AUTOGEN), which is supplied by Compaq. Compaq recommends that you use AUTOGEN regularly to adjust the values for system parameters to fit your hardware configuration and your system's work load.
Information Provided in This Chapter
This chapter describes the following tasks:
|Converting your customized parameter settings for use with AUTOGEN||Section 15.3|
|Modifying system parameter values with AUTOGEN (recommended method)||Section 15.5|
|Controlling AUTOGEN's parameter settings with MODPARAMS.DAT||Section 15.5.1|
|Automating AUTOGEN reports||Section 15.6|
|Managing system parameters with SYSMAN||Section 15.7|
|Managing system parameters with SYSGEN||Section 15.8|
|Managing system parameters with a conversational boot||Section 15.9|
This chapter explains the following concepts:
|System parameters||Section 15.1|
|Default, current, and active values of system parameters||Section 15.1.1|
|Pages and pagelets||Section 15.1.2|
|The recommended method for changing system parameter values||Section 15.2|
|The AUTOGEN command procedure||Section 15.4|
|AUTOGEN feedback||Section 15.4.1|
|The AUTOGEN feedback report (AGEN$PARAMS.REPORT)||Section 15.4.2|
|AUTOGEN phases||Section 15.4.3|
|The AUTOGEN parameter file (MODPARAMS.DAT)||Section 15.4.4|
15.1 Understanding System Parameters
The system uses values for system parameters to
control how the system functions. System parameters control a wide
range of system functions, including but not limited to the following
The OpenVMS System Management Utilities Reference Manual lists and describes each system parameter.
Your distribution kit provides default values for system parameters to allow you to boot any supported configuration. When your system is installed or upgraded, the SYS$UPDATE:AUTOGEN.COM command procedure executes to evaluate your hardware configuration, estimate typical work loads, and adjust the values of system parameters as needed.
Each system parameter has associated minimum and maximum values that define the scope of allowable values.
System parameters can be one or more of the following types:
|Dynamic||The value of a dynamic system parameter can be modified while the system is active by changing the active value in memory. In contrast, if you change the value of a parameter that is not dynamic, you must change the current value stored in the parameter file, and you must reboot the system for the changed value to take effect. For information about active and current values, see Section 15.1.1.|
|General||The value of a general parameter affects the creation and initialization of data structures at boot time.|
|Major||Major parameters are most likely to require modification.|
|Special||Special parameters are intended for use only by Compaq. Change these parameters only if recommended by Compaq personnel or in the installation guide or release notes of a Compaq-supplied layered product.|
Parameter Categories by Function
System parameters can be divided into the following categories, according to their function:
|ACP||Parameters associated with file system caches and Files-11 XQP (extended QIO procedure) or ancillary control processes (ACPs). 1|
|Cluster||Parameters that affect VAXcluster or OpenVMS Cluster system operation.|
|Job||Parameters that control jobs.|
|LGI||Parameters that affect login security.|
|Multiprocessing||Parameters associated with symmetric multiprocessing.|
|PQL||Parameters associated with process creation limits and quotas.|
|RMS||Parameters associated with OpenVMS Record Management Services (RMS).|
|SCS||Parameters that control system communication services (SCS) and port driver operation. The parameters that affect SCS operation have the prefix SCS.|
|SYS||Parameters that affect overall system operation.|
|TTY||Parameters associated with terminal behavior.|
The following parameters can be user-defined:
|privacy and legal statement|