OpenVMS ALPQMAN03_062 Alpha V6.2 - V6.2-1H3 Queue Manager ECO Summary

TITLE: OpenVMS ALPQMAN03_062 Alpha V6.2 - V6.2-1H3 Queue Manager ECO Summary Modification Date: 09-FEB-99 Modification Type: Updated Kit: Supersedes ALPQMAN02_062 NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 1997, 1999. All rights reserved. PRODUCT: DIGITAL OpenVMS Alpha COMPONENT: Queue Manager Job Controller SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: ALPQMAN03_062 ECO Kits Superseded by This ECO Kit: ALPQMAN02_062 ALPQMAN04_070 (For OpenVMS Alpha V6.2 *ONLY*) ALPQMAN03_070 ALPQMAN02_070 ALPQMAN01_070 ALPQMAN01_062 AXPQMAN03_061 (AXPQMAN) AXPJOBC01_061 (CSCPAT_2087 V1.2) This kit was never released. AXPQMAN01_061 (CSCPAT_2087 V1.1) AXPPRTS01_061 (CSCPAT_2087 V1.0) ECO Kit Approximate Size: 1764 Blocks Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, 6.2-1H3 System/Cluster Reboot Necessary: Yes Rolling Reboot Supported: Yes Installation Rating: INSTALL_3 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. Kit Dependencies: The following remedial kit(s) must be installed BEFORE installation of this kit: None In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None ECO KIT SUMMARY: An ECO kit exists for Queue Manager OpenVMS Alpha V6.2 through V6.2-1H3. This kit addresses the following problems: Problems addressed in ALPQMAN03_062: 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 %%%%%%%%%%% 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. Problems addressed in ALPQMAN02_062: o BATCH/PRINT problems corrected: + The DCL command SHOW QUEUE/MANAGER would hang on some nodes. The job controller process would hang in the LEF state. + 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 DCPS-F-STREAMUSE and queue become stuck in starting errors: + Occasional flagging of a DCPS-F-STREAMUSE error while starting DCPS queues. + Print Queues (either LAT, DQS or DCPS) may hang stuck in a starting state. Problems addressed in ALPQMAN04_070 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3: o Being re-issued to keep Message Routines current with Library RTL kit. There are no new fixes in this kit. Problems addressed in ALPQMAN03_070 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3: o The ALPQMAN02_070 remedial kit would not install on V6.1 and V6.2 OpenVMS Alpha hardware versions. There are no additional problem fixes in this remedial kit. Problems addressed in ALPQMAN02_070 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3: 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 F$GETQUI is used at DCL to obtain queue manager information, certain combinations of items can hang the process. o The queue manager stops after the following messages are issued 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 Problems addressed in ALPQMAN01_070 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2: o LATSYM symbiont processes run with less than the maximum number of queues assigned. NOTE: According to OpenVMS Engineering, the fixes discussed below have been included in OpenVMS Alpha V7.0. There are some fixes that have been included in previous versions of OpenVMS and those versions are specified in text following the problem descriptions. Problems addressed in ALPQMAN01_062 for OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, and V6.2-1H3: o Queue System Response is sporadically slow. This reduction in performance occurs most frequently on systems with many queues and forms. On large production systems, the delays may become severe if the problem occurs during queue journal file checkpointing. The Queue Manager may crash with a BADLOGIC error in the WILD_MASTER_NAME routine. o An extra line feed occurs on the top of printouts for FORTRAN Carriage control files that contain a zero-length first record. o The log files created via the 'SUBMIT/NOPRINT' command executed from within SYSTARTUP_VMS.COM are placed in the SYS$SYSTEM directory instead of the SYS$MANAGER directory as expected. This is not consistent with the behavior of SYSTARTUP_VMS.COM on all previous versions of the operating system. o The SYS$COMMON:[SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL queueing system journal file extends to approximately 41,000 blocks after the upgrade from OpenVMS Alpha V6.1 to OpenVMS Alpha V6.2. o With OpenVMS Alpha V6.2, a 'SUBMIT' command using a wildcard character fails to create a batch job. This is a change in behavior from OpenVMS V6.1. o Over time, the number of symbiont processes running on the system increases. 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. INSTALLATION NOTES: The images in this kit will not take effect until the system is rebooted. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image. If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed.

This patch can be found at any of these sites:

Files on this server are as follows:

alpqman03_062.README
alpqman03_062.CHKSUM
alpqman03_062.CVRLET_TXT
alpqman03_062.a-dcx_axpexe