Kit Name: DEC-AXPVMS-VMS732_QMAN-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 1760 blocks Installation Rating: INSTALL_3 Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS732_UPDATE-V0700 or later VMS732_PCSI-V0300 or later Optional Kit Dependencies: None VMS732_QMAN-V0100.PCSI-DCX_AXPEXE Checksum: 3196754622 DEC-AXPVMS-VMS732_QMAN-V0100--4.PCSI Checksum: 3919059016 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_QMAN-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V7.3-2 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0300 - VMS732_UPDATE-V0700 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_QMAN-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 Maximum Job Limit On Batch Queues Increased 5.1.1.1 Functionality Description: The maximum Job limit of 255 on batch queues has been increased to 65535. Images Affected: - Maximum Job Limit On Batch Queues Increased - [SYSEXE]QUEMAN.EXE - [SYSEXE]QMAN$QUEUE_MANAGER.EXE 5.2 Problems addressed in this kit 5.2.1 SHOW ENTRY/USER=NAME Command Loops 5.2.1.1 Problem Description: When more than one queue manager is defined, a SHOW ENTRY/USER=NAME command loops, redisplaying entry numbers greater than one million. Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 2 LOGIN UNAME Holding On stopped batch queue CSG40_BATCH 000002 LOGIN UNAME Holding On stopped batch queue CSG40_BATCH 1000009 LOGIN UNAME Holding On stopped batch queue CSG40_BATCH 10001 LOGIN UNAME Pending On stopped batch queue DAVES_BATCHQ Page 3 20002 LOGIN UNAME Pending On stopped batch queue QMAN_THREE_BATCHQ2 1000002 LOGIN UNAME Holding On stopped batch queue CSG40_BATCH 1000009 LOGIN UNAME Holding On stopped batch queue CSG40_BATCH . . . . Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) 75-13-762 5.2.1.3 Problem Analysis: Code did not exist to terminate the system service retry logic when the following conditions existed: o Multiple queue managers are in use o Entry numbers are extended into the million range o At least one queue manager is running and at least one queue manager is stopped. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 Page 4 5.2.1.5 Work-arounds: None. 5.2.2 QUI$V_SEARCH_THIS_JOB Flag gives %JBC-E-NOJOBCTX Error 5.2.2.1 Problem Description: Using the QUI$V_SEARCH_THIS_JOB flag from a subprocesses in batch jobs sometimes fails unexpectedly with a %JBC-E-NOJOBCTX, no job context error. $ X = F$GETQUI("DISPLAY_ENTRY","ENTRY_NUMBER",,"THIS_JOB") %JBC-E-NOJOBCTX, no job context Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) %JBC-E-NOJOBCTX, no job context 5.2.2.3 Problem Analysis: The queue manager code did not return message resend information to the system service for this_job GETQUI requests. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 Page 5 5.2.2.5 Work-arounds: None. 5.2.3 Batch Process Does Not Exit Immediately After DELETE/ENTRY=NUMBER 5.2.3.1 Problem Description: When a DELETE/ENTRY=NUMBER of a batch process system is done, the process may not not exit immediately and one or more of the following entries may be observed in the log file: o Multiple "%JBC-F-JOBABORT, job aborted during execution" messages o One or more "%RMS-F-ISI, invalid internal stream identifier (ISI) value" messages o Multiple job accounting data may be output Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) None. 5.2.3.2.2 QAR(s) 75-102-1309, 75-109-400 5.2.3.3 Problem Analysis: When the queue manager receives a SJC_BATCH_SERVICE request from a batch process in the aborting state, it assumes the process did not receive the $exit request and reissues the request to delete the process. The Loginout image condition handler calls a routine to terminate the batch job which sends the final exit status to the queue manager via a sndjbcw while the job is in aborting state. This begins a cycle of exit requests sent to the batch process, causing the loginout handler to run sending and Page 6 another sndjbc request, etc... 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.3.5 Work-arounds: None. 5.2.4 Batch Job Fails with SYSTEM-F-INSFMEM Error 5.2.4.1 Problem Description: When a user account has more then 1024 identifiers, a batch job submitted by the user will fail with a SYSTEM-F-INSFMEM error. Images Affected: - [SYSEXE]JBC$JOB_CONTROL.EXE - [SYSEXE]QMAN$QUEUE_MANAGER.EXE - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000310652 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: If a user has more then 1024 identifiers, then the QMAN message size exceeds the 22K limit size and gets an INSFMEM error. Page 7 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.4.5 Work-arounds: None. 5.2.5 Unnecessary QMAN-W-LOWMEMORY Warning Message 5.2.5.1 Problem Description: Systems which have a very large physical memory (more then 10GB) and a large PAGEFILE.SYS sometimes produce the following QMAN error messages. %QMAN-W-LOWMEMORY, the queue manager process may require more virtual memory than is currently available. %QMAN-F-ALLOCMEM, error allocating virtual memory -LIB-F-INSVIRMEM, insufficient virtual memory %JBC-E-QMANDEL, unexpected queue manager process termination This may also result in a system crash. Images Affected: - [SYSEXE]QMAN$QUEUE_MANAGER.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) QXCM1000312108 5.2.5.2.2 QAR(s) None. 5.2.5.3 Problem Analysis: With a large PAGEFILE.SYS, the check for available memory in the Queue Manager may overflow a longword. The results of this overflow are the unnecessary LOWMEMORY warnings and the possible system crash. Page 8 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2. 5.2.5.5 Work-arounds: None. 6 FILES PATCHED OR REPLACED: o [SYSEXE]JBC$COMMAND.EXE (new image) Image Identification Information image name: "JBC$COMMAND" image file identification: "X-5" image file build identification: "XA99-0060111003" link date/time: 1-MAR-2006 07:39:22.83 linker identification: "A11-50" Overall Image Checksum: 4175406559 o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) Image Identification Information image name: "JBC$JOB_CONTROL" image file identification: "X-15A1" image file build identification: "XA99-0060111003" link date/time: 1-MAR-2006 07:39:22.48 linker identification: "A11-50" Overall Image Checksum: 4091774775 o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) Image Identification Information image name: "MESSAGE_ROUTINES" image file identification: "X-4" image file build identification: "XA99-0060111043" link date/time: 31-MAY-2006 14:03:12.29 linker identification: "A11-50" Overall Image Checksum: 547236015 o [SYSEXE]QMAN$QUEUE_MANAGER.EXE (new image) Image Identification Information image name: "QMAN$QUEUE_MANAGER" image file identification: "X-3" image file build identification: "XA99-0060111008" link date/time: 14-APR-2006 09:01:58.19 linker identification: "A11-50" Overall Image Checksum: 663333502 Page 9 o [SYSEXE]QUEMAN.EXE (new image) Image Identification Information image name: "QUEMAN" image file identification: "X-18" image file build identification: "XA99-0060111012" link date/time: 1-MAR-2006 07:41:00.69 linker identification: "A11-50" Overall Image Checksum: 3444893068 o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable .PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_QMAN-V0100.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] Page 10 The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the"Decompress into (file specification)" question, either a or an alternate directory specification 7.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS732_QMAN[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE Page 11 o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS732_QMAN-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_QMAN/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Page 12 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 HP 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.