Document revision date: 19 July 1999

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-1998 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:

• Make the stocks match by mounting a different form on the queue (for example, using SET QUEUE/FORM_MOUNTED) or by specifying a different form with the job (for example, using SET ENTRY/FORM).
• Move the job to a queue on which the stock of the mounted form matches the stock of the job's form (for example, using SET ENTRY/REQUEUE).
• Delete the job (for example, using DELETE/ENTRY).

See Section 13.6.7 for more information about forms.

13.8.2.2 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-1998 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:

• Move the job to a queue on which the characteristics match those of the job (for example, using SET ENTRY/REQUEUE).
• Delete the job (for example, using DELETE/ENTRY).
• Make the characteristics match by assigning new characteristics to the queue (for example, using SET QUEUE/CHARACTERISTICS).

See Section 13.6.3 for more information about characteristics.

13.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 13.7.1.10. When the problem is fixed, deassign the logical queue and start the queue by entering START/QUEUE.

13.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.

Example

$ ENABLE AUTOSTART/QUEUES/ON_NODE=KATY::(1) $ SHOW QUEUE KATY_BATCH Batch queue KATY_BATCH, stopped, autostart inactive, on KATY::(2) $ START/QUEUE KATY_BATCH(3) $ SHOW QUEUE KATY_BATCH/ALL Batch queue KATY_BATCH, idle, on KATY::(4)

The numbers in following list correspond to numbers in the example:

1. ENABLE AUTOSTART/QUEUES attempts to start autostart queues on node KATY.
2. The SHOW QUEUE display shows that the autostart batch queue KATY_BATCH did not start. The display also reveals that the queue is inactive for autostart; the queue was either not activated initially or it was deactivated with STOP/QUEUE/NEXT or STOP/QUEUE/RESET.
3. START/QUEUE activates the queue for autostart.
4. SHOW QUEUE informs you that the queue is started.

If you are having problems deleting a queue, form, or characteristic, make sure you have met the following requirements:

• When deleting a form or characteristic with DELETE/FORM or DELETE/CHARACTERISTICS, you must specify the name assigned to the form or characteristic. (The form or characteristic number cannot be used with the DELETE command.) To determine the name of a form or characteristic, enter SHOW QUEUE/FORM or SHOW QUEUE/CHARACTERISTICS.
• A queue must be stopped before being deleted.
• All references to a queue, form, or characteristic must be removed before you can delete the queue, form, or characteristic.

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:

1. Enter SHOW QUEUE/FULL/ALL_JOBS/OUTPUT=filespec, where filespec is a name of a file to which the display output of the command is to be sent.
2. Use the SEARCH command to search the output file for the name of the form or queue, or the number of the characteristic to be deleted. The result of your search will include all references to the queue, form, or characteristic.
3. If the SEARCH command reveals any queues with references to the queue, form, or characteristic you are trying to delete, perform the following steps:
   1. Use STOP/QUEUE/NEXT to stop each queue with an offending reference.
   2. Use START/QUEUE with the appropriate qualifiers to restart each queue without the reference.
4. If the SEARCH command reveals any jobs with references to the queue, form, or characteristic you are trying to delete, perform the following steps to eliminate the job reference:
   1. Wait for the job to complete. (You might want to raise the priority of the job as explained in Section 13.6.5.2, so the job will be scheduled for processing sooner.)
   2. Perform either of the following actions:
      • Delete the job as explained in Section 13.7.2.6.
      • Modify the options for the job as explained in Section 13.7.2.2, or ask the owner of the job to do so.

Example

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:

1. The DELETE/QUEUE command attempts to delete the queue.
2. The message indicates that the queue is not stopped.
3. The STOP/QUEUE/NEXT command stops the queue after allowing the current job to complete.
4. The DELETE/QUEUE command again attempts to delete the queue.
5. This time, the message indicates that references to the queue exist.
6. The SHOW QUEUE/FULL command shows information about all queues. However, the only reference to JADE_BATCH names the queue as a target queue for the generic queue CLUSTER_BATCH.
7. The STOP/QUEUE/NEXT command stops the generic queue that targets JADE_BATCH.
8. The START/QUEUE command eliminates the reference to JADE_BATCH by restarting the generic queue without specifying JADE_BATCH as a target.
9. The DELETE/QUEUE command successfully deletes the queue.

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.

13.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:

1. Enter a command in the following format:

   SHOW QUEUE/FULL/OUTPUT=filespec

   
   where filespec is the name of a file to which the display output of the command is to be sent.

2. Use the SEARCH command to search the output file for the name of the library.

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.

If you cannot stop the queues immediately, perform the following steps:

1. Use the COPY command to copy the library to be modified into your own directory.
2. Add the module to the copy, or delete the module from the copy.
3. Use the COPY command to copy the library back to the directory SYS$COMMON:[SYSLIB]. As long as you use the same name for the modified library, the library will be picked up by each queue when the queue is stopped and restarted.

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 Section 13.6.8.3.

13.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:

1. Contact your Compaq support representative
2. Delete the queue and create a new queue to replace it.

If you encounter a problem with your queues, and you want to report it to Compaq, please provide as much information as possible. Section 12.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:

Task	Section
Converting your customized parameter settings for use with AUTOGEN	Section 14.3
Modifying system parameter values with AUTOGEN (recommended method)	Section 14.5
Controlling AUTOGEN's parameter settings with MODPARAMS.DAT	Section 14.5.1
Automating AUTOGEN reports	Section 14.6
Managing system parameters with SYSMAN	Section 14.7
Managing system parameters with SYSGEN	Section 14.8
Managing system parameters with a conversational boot	Section 14.9

This chapter explains the following concepts:

Concept	Section
System parameters	Section 14.1
Default, current, and active values of system parameters	Section 14.1.1
Pages and pagelets	Section 14.1.2
The recommended method for changing system parameter values	Section 14.2
The AUTOGEN command procedure	Section 14.4
AUTOGEN feedback	Section 14.4.1
The AUTOGEN feedback report (AGEN$PARAMS.REPORT)	Section 14.4.2
AUTOGEN phases	Section 14.4.3
The AUTOGEN parameter file (MODPARAMS.DAT)	Section 14.4.4

14.1 Understanding System Parameters

• Memory management
• Scheduling
• Security attributes
• System caches
• Windowing system choice
• Terminal configuration
• VAXcluster or OpenVMS Cluster system attributes

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.

Parameter Types

System parameters can be one or more of the following types:

Type	Description
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 14.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:

Category	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.
User-defined	The following parameters can be user-defined: USERD1 (dynamic) USERD2 (dynamic) USER3 USER4

	privacy and legal statement
6017PRO_064.HTML