ECO NUMBER: VAXQMAN02_071 ----------- PRODUCT: OpenVMS VAX Operating System -------- UPDATED PRODUCT: OpenVMS VAX Operating System 7.1 ---------------- APPRX BLCK SIZE: 558 ---------------- COVER LETTER 1 KIT NAME: VAXQMAN02_071 2 KITS SUPERSEDED BY THIS KIT: VAXQMAN01_071 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.1 4.2 Files patched or replaced: o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXQMAN02_071 KIT o Submitting a job to a batch queue, set up with a default protection, generated a CONTROL access audit alarm, even though the user did not request control access. As a result, OPERATOR.LOG was flooded with security audit messages. For example, doing $ SET AUDIT/CLASS=QUEUE/ALARM/ENA=ACCESS=FAIL: $ SUBMIT X.COM/QUE=TEST/NOLOG/NOTIFY %%%%%%%%%%% OPCOM 3-MAR-1998 12:08:20.38 %%%%%%%%%%% -- COVER LETTER -- Page 2 21 January 1999 Message from user AUDIT$SERVER on CHEN Security alarm (SECURITY) on CHEN, system id: 65422 Auditable event: Object access Event time: 3-MAR-1998 12:08:20.38 PID: 000000DF Source PID: 000000CE Username: USER Process owner: [LASTNAMEO,FIRSTNAMEO] Object class name: QUEUE Object name: TEST Object owner: [SYSTEM] Object protection: SYSTEM:M, OWNER:D, GROUP:R, WORLD:S Access requested: CONTROL Status: %SYSTEM-F-NOPRIV, insufficient privilege or object protection violation Job X (queue TEST, entry 4) started on TEST $ Job X (queue TEST, entry 4) completed o Two spool problems occurred: 1. Files copied to a spooled device were not deleted from the spool area when its corresponding entry was deleted from the queue. 2. Prior to OpenVMS V6.2, a spooled batch queue could run without a problem, even if the command procedure was broken. However, on OpenVMS V6.2 and OpenVMS V7.1, a broken command procedure passed to a spooled batch queue would result in lost files. o An error can occur when the Default Form reference count is incremented in two similar circumstances: 1. The error can occur while batch queues are being created. 2. It can also occur when generic queues are initialized. Changing the stock on the DEFAULT form can result in an error, even when there are no references (jobs, queues, ...) to the DEFAULT form. The following error was observed: $DEFINE/FORM /STOCK=NEW_STOCK DEFAULT 0 %JBC-E-STKNOTCHANGE, the stock associated with a form NOTE: If a customer uses multiple Queue Managers on a system, ALL Queue Managers must be running in order for a form update to occur. If all Queue Managers are not running, the STKNOTCHANGE error will occur. -- COVER LETTER -- Page 3 21 January 1999 6 PROBLEMS ADDRESSED IN VAXQMAN01_071 KIT o Several problems were corrected: o The DCL command SHOW QUEUE/MANAGER would hang on some nodes. The job controller process would hang in the LEF state. o After queue manager failover from VAX to Alpha, the job controller process (on Alpha) hangs in LEF causing the queues on the Alpha system to remain in a starting state. The queues remain there until the job controller is stopped and restarted. Also the SHOW QUEUE/MANAGER command hangs. o When booting in a new node or failing over the queue manager, the cluster appears to hang. The job controller continually produces dump files at SYS$SYSTEM:JBC$JOB_CONTROL.DMP. The error reported in the dump is "feature incompatible with previous system version". o Two problems have been fixed: o Occasional flagging of a DCPS-F-STREAMUSE error while starting DCPS queues. o Print Queues (either LAT, DQS or DCPS) may hang stuck in a starting state. o When SJC$_DELETE_FILE_ALWAYS deletes a print job, created through PATHWORKS, the spool file. is not always deleted. It deletes only when the job is in execution state. 7 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 3 : To be installed by customers experiencing the problems corrected. -- COVER LETTER -- Page 4 21 January 1999 8 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXQMAN02_071 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. If you have other nodes in your VMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. Copyright (c) Compaq Computer Corporation, 1999 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.