ECO NUMBER: VAXQMAN05_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXQMAN05_062 2 KITS SUPERSEDED BY THIS KIT: VAXQMAN04_062 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 V6.2 4.2 Files patched or replaced: o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) o [SYSEXE]QUEMAN.EXE (new image) o [SYSEXE]SUBMIT.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXQMAN05_062 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: -- COVER LETTER -- Page 2 20 January 1999 $ SUBMIT X.COM/QUE=TEST/NOLOG/NOTIFY %%%%%%%%%%% OPCOM 3-MAR-1998 12:08:20.38 %%%%%%%%%%% 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. 6 PROBLEMS ADDRESSED IN VAXQMAN04_062 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. -- COVER LETTER -- Page 3 20 January 1999 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. 7 PROBLEMS ADDRESSED IN VAXQMAN03_070 KIT FOR OPENVMS V6.2 o Being re-issued to keep Message Routines current with Library RTL kit. There are no new fixes in this kit. 8 PROBLEMS ADDRESSED IN VAXQMAN02_070 KIT FOR OPENVMS VAX V6.2 o Delete/Entry on a starting job fails to stop the job. The job stays in an aborting state and processes to completion. o When executing at DCL, for some queue manager information using F$GETQUI, certain combinations of items can hang the process. o Queue manager process stops after the following messages in OPCOM: %%%%%%%%%%% OPCOM 8-MAY-1996 14:52:17.83 %%%%%%%%%%% Message from user QUEUE_MANAGE on HULAW3 %QMAN-W-LOWMEMORY, the queue manager process may require more virtual memory than is currently available %%%%%%%%%%% OPCOM 8-MAY-1996 14:53:07.20 %%%%%%%%%%% Message from user QUEUE_MANAGE on HULAW3 %QMAN-F-ALLOCMEM, error allocating virtual memory %%%%%%%%%%% OPCOM 8-MAY-1996 14:53:07.24 %%%%%%%%%%% Message from user QUEUE_MANAGE on HULAW3 -LIB-F-INSVIRMEM, insufficient virtual memory -- COVER LETTER -- Page 4 20 January 1999 9 PROBLEMS ADDRESSED IN VAXQMAN01_070 KIT FOR OPENVMS VAX V6.2 o Latsym symbiont processes running with less than the maximum number of queues assigned. 10 PROBLEMS ADDRESSED IN VAXQMAN01_062 KIT FOR OPENVMS VAX V6.2 o With OpenVMS V6.2, a wildcard submit command fails to create a batch job. This is a change in behavior from OpenVMS V6.1. For example: If you create a file called CHECK_FOR_DUPES.COM and then enter the command $SUBMIT *DUP*, on OpenVMS VAX V6.1 the job runs and creates a log file, CHECK_FOR_DUPES.LOG. On OpenVMS Alpha V6.1, the job runs, but no log is created. On OpenVMS Alpha V6.2, the job does not run and the operator gets a message: %%%%%%%%%%% OPCOM 16-MAY-1995 09:58:15.69 %%%%%%%%%%% Message from user AUDIT$SERVER on NODENAME Security alarm (SECURITY) and security audit (SECURITY) on NODENAME, system id: Auditable event: Batch process login failure Event time: 16-MAY-1995 09:58:15.69 PID: 20200057 Process name: BATCH_1 Username: USERNAME Process owner: [USERNAME] Image name: $1$DKB200:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE Status: %RMS-F-WLD, invalid wildcard operation o The log files created via SUBMIT commands executed from within SYSTARTUP_VMS.COM (via SUBMIT/NOPRINT command) creates the log files in SYS$SYSTEM: and *NOT* in SYS$MANAGER: as expected. This is not consistent with the behavior of SYSTARTUP_VMS.COM on all previous versions of the operating system. o The queuing system journal file, SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL, grows to a large size (approx. 41K blocks) after upgrading from OpenVMS V6.1 to OpenVMS V6.2 11 PROBLEMS ADDRESSED IN VAXQMAN01_062 KIT FOR OPENVMS VAX V6.2 o Over time the number of symbiont processes running on the system increases. -- COVER LETTER -- Page 5 20 January 1999 o When image accounting is enabled, the ASTCNT for a batch job grows from its initial setting, and the batch job subsequently fails with the following messages: RMS-F-BUG, Fatal RMS Condition ,process deleted. R0 = 1C (EXQUOTA) R2 = FFFFFFF8 (CANTDOAST) Each time an image is activated and terminated in a batch process, the AST quota of the process is incremented by 1. 12 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: INSTALL_3 : To be installed by customers experiencing the problems corrected. 13 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 VAXQMAN05_062 [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. -- COVER LETTER -- Page 6 20 January 1999 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.