ECO NUMBER: ALPQMAN04_061 ----------- PRODUCT: OpenVMS Alpha Operating System -------- UPDATED PRODUCT: OpenVMS Alpha Operating System 6.1 ---------------- APPRX BLCK SIZE: 1602 ---------------- COVER LETTER 1 KIT NAME: ALPQMAN04_061 2 KITS SUPERSEDED BY THIS KIT: ALPQMAN04_070 for OpenVMS V6.1 Only 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced: o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) 4 PROBLEMS ADDRESSED IN ALPQMAN04_061 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 -- COVER LETTER -- Page 2 20 January 1998 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. 5 PROBLEMS ADDRESSED IN ALPQMAN04_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 o Being re-issued to keep Message Routines current with Library RTL kit. There are no new fixes in this kit. 6 PROBLEMS ADDRESSED IN ALPQMAN03_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 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. 7 PROBLEMS ADDRESSED IN ALPQMAN02_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 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 %%%%%%%%%%% -- COVER LETTER -- Page 3 20 January 1998 Message from user QUEUE_MANAGE on HULAW3 -LIB-F-INSVIRMEM, insufficient virtual memory 8 PROBLEMS ADDRESSED IN ALPQMAN01_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 o Latsym symbiont processes running with less than the maximum number of queues assigned. 9 PROBLEMS ADDRESSED IN ALPQMAN01_62 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2 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. 10 PROBLEMS ADDRESSED IN AXPQMAN03_061 KIT o The AXPJOBC01_061 kit contained both QMAN and PRTSMB ECOs. The AXPQMAN03_061 kit supersedes only the QMAN portion of the AXPJOBC01_061 kit. The PRTSMB ECOs have been separated into the AXPPRTS02_061 kit. The AXPPRTS02_061 supersedes the PRTSMB portion of the AXPJOBC01_061 kit. o The Queue name field is blank for batch accounting records on OpenVMS AXP V6.1 systems that apply patch AXPQMAN01_061. o The accounting data reported by the DCL 'ACCOUNTING/SUMMARY/REPORT=PAGES' command is sometimes incorrect. The incorrect data is reported after jobs are reprinted and occurs because the number of pages printed is accumulated in each separate accounting record instead of being overwritten. For example: Print Seq Acctng Record ACCOUNTING/SUMMARY/REPORT=PAGES number Pages Printed Output --------- -------------- ------------------------------- -- COVER LETTER -- Page 4 20 January 1998 1 3 3 2 6 9 3 9 18 The actual number of pages printed by the user is nine but the summary accounting reports eighteen pages. o At startup the queue manager dumps with a BADLOGIC error in routine WILD_MASTER_NAME. (PC 0000C67E on V6.1). It becomes necessary to recreate the queue manager to restart the queue system. o QMAN security fix. 11 PROBLEMS ADDRESSED IN AXPJOBC01_061 KIT o ECO kit AXPQMAN01_061 caused the Queue name field to be blank for batch accounting records on OpenVMS AXP V6.1 systems. 12 PROBLEMS ADDRESSED IN AXPQMAN01_061 KIT o An extra line feed occurs on the top of printouts for FORTRAN Carriage control files that have a first record of length zero. o Queue System Response gets sluggish sporadically. The performance is sluggish particularly on systems with many queues and forms. On large production systems the delays can become severe if the problem occurs during queue journal file checkpointing. Also, Queue Manager crashes with BADLOGIC error in routine WILD_MASTER_NAME. o The job controller process can crash due to access violations. o A print job may have a status of pending due to a stock type mismatch, even though the stock of the form on the print job matches the stock of the form mounted on the queue. See the following example: $ show queue/full/all 332_m_1 Terminal queue 332_M_1, idle, on UHAD6::LTA151:, mounted form DEFAULT /BASE_PRIORITY=3 /CHAR=(9) /DEFAULT=(FORM=DEFAULT) /NOENABLE_GENERIC /LIBRARY=UH_HPLASERJET Lowercase /OWNER=[VMS,SYSTEM]/PROCESSOR=LATSYM /PROTECTION=(S:M,O:D,G:M,W:RS) /SCHEDULE=(NOSIZE)/SEPARATE=(RESET= (RESET)) Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 10960 TEST SPARKS 1 Pending(stock type mismatch) -- COVER LETTER -- Page 5 20 January 1998 Submitted 23-JUN-1994 10:27 /FORM=DEFAULT/PRIORITY=100 File: _DSA0:[UHCOMMON.SHARON]TEST.TXT;2 10962 TEST SPARKS 1 Pending(stock type mismatch) Submitted 23-JUN-1994 10:27 /FORM=NOMARGIN (stock=DEFAULT) /PRIORITY=100 File: _DSA0:[UHCOMMON.SHARON]TEST.TXT;2 o The symbiont can dump with a BADLOGIC error in PSM$REPORT if a STOP/QUEUE/RESET is immediately followed by a START/QUEUE command. The queues managed by the failing symbiont are stopped and there is a loss of service. o A SET QUEUE/ENTRY DCL command for a nonexistant queue issues the following error message twice, instead of once: %JBC-E-NOSUCHQUE, no such queue o When $GETQUI is called from a nonbatch process, with DISPLAY_JOB function and THIS_JOB flag, a JOBQUEDIS error is returned even when the queue manager is running. This problem also occurred when a process was spawned from a batch process. o Memory that is allocated for storing output values for a SHOW QUEUE/MANAGER command is not deallocated after command completion. If a user does a series of SHOW QUEUE/MANAGER commands the job controller can crash with an insufficient virtual memory error. o Timed jobs are listed by priority, then by /AFTER_TIME. Jobs with the same /AFTER_TIME are listed in entry number order, not in submit time order. This fix causes a $SHOW QUEUE to list timed jobs in /AFTER_TIME order. o Timed jobs, of equal priority, sometimes execute in submit time order, not in the release time (/AFTER_TIME) order. This happens when multiple jobs are pending execution. In the example provided below, customers expect the jobs to run in 1,3,2 order, not in the 1,2,3 order. This fix corrects the execution order. Time 12:00 Entry Jobname Username Status ----- ------- -------- ------ 1 LOGIN USER Executing 3 LOGIN USER Holding until 12:30 2 LOGIN USER Holding until 13:00 Time 12:31 Entry Jobname Username Status ----- ------- -------- ------ 1 LOGIN USER Executing 3 LOGIN USER Pending 2 LOGIN USER Holding until 13:00 Time 13:01 -- COVER LETTER -- Page 6 20 January 1998 Entry Jobname Username Status ----- ------- -------- ------ 1 LOGIN USER Executing 2 LOGIN USER Pending 3 LOGIN USER Pending Entry number one finishes: Entry Jobname Username Status ----- ------- -------- ------ 2 LOGIN USER Executing 3 LOGIN USER Pending Since job 1 did not complete until both jobs 2 and 3 were pending, we see the problem the customers reported. The V5.4-3 queue manager was tested and ran the jobs in 1,3,2 order. o The file associated with a job is deleted even if the print is unsuccessful. o When a symbiont sends a TASK_STATUS request to the Queue Manager, and no job is active, then the request is rejected with the following message: Message from user QUEUE_MANAGE on ARDAS1 %QMAN-I-INVSMBMSG, invalid data in message from symbiont on queue TEST is being ignored o During a failover of the Queue Manager, if there are outstanding jobs, it is possible to get the system service error NOMOREPROC status. o With latest print symbiont, All-in-1 users may experience a blank page between each job o Issuing the PRINT/DELETE of many files (several thousand) crashes the queue manager with an ACCVIO. 13 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as 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 7 20 January 1998 14 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 ALPQMAN04_061 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). Copyright (c) Digital Equipment Corporation, 1998 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 Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment 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 DIGITAL 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.