ECO NUMBER: VMS721H1_MANAGE-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 COVER LETTER 1 KIT NAME: VMS721H1_MANAGE-V0200. 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: VMS721H1_UPDATE-V0400. 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 Alpha V7.2-1H1. 4.2 Files patched or replaced: o [SYSLIB]SMI$SHR.EXE (new image) o [SYSEXE]SMISERVER.EXE (new image) o [SYSEXE]AGEN$FEEDBACK.EXE (new image) o [SYSUPD]AUTOGEN.COM (new file) o [SYS$STARTUP]VMS$CONFIG-050_LMF.COM (new file) o [SYS$STARTUP]VMS$CONFIG-050_JOBCTL.COM (new file) -- COVER LETTER -- Page 2 12 June 2001 5 PROBLEMS ADDRESSED IN VMS721H1_MANAGE-V0200 KIT o The SYSMAN security profile is supposed to be identical on all nodes in a cluster that uses the same security environment. However, SYSMAN may use the authorization privileges from the UAF (user authorization file) instead of the locally set privileges on SOME nodes. See the following cluster example below in which NODE1 should have same privilege settings as NODE2: SYSMAN> set env/clus %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> show profile %SYSMAN-I-DEFDIR, default directory on node NODE2 -- SYS$SYSROOT:[SYSMGR] %SYSMAN-I-DEFPRIV, process privileges on node NODE2 -- TMPMBX OPER NETMBX %SYSMAN-I-DEFDIR, default directory on node NODE1 -- SYS$SYSROOT:[SYSMGR] %SYSMAN-I-DEFPRIV, process privileges on node NODE1 -- CMKRNL CMEXEC SYSNAM GRPNAM ALLSPOOL TMPMBX OPER NETMBX Images Affected: - [SYSLIB]SMI$SHR.EXE o OpenVMS-ALPHA and OpenVMS-ALPHA-USER licenses do not always load at boot on Galaxy. When the OpenVMS-ALPHA license does not meet the required number of units to load, as per the LURT table, for a Galaxy processor with multiple CPU's, the license loads successfully and allows full access to the system as long as an OpenVMS-ALPHA-User license is also loaded. Images Affected: -- COVER LETTER -- Page 3 12 June 2001 - [SYS$STARTUP]VMS$CONFIG-050_LMF.COM o The QUEUE_MANAGER process crashes and produces the following error messages: Message from user QUEUE_MANAGE on MAUAX1 %QMAN-F-WRITEERR, error writing $20$DKA204:[SYSCLUSTER.] [SYSEXE]SYS$QUEUE_MANAGER.QMAN$JOURNAL;1 Message from user QUEUE_MANAGE on MAUAX1 -RMS-F-SYS, QIO system service request failed Message from user QUEUE_MANAGE on MAUAX1 -RMS-F-SYS, QIO system service request failed Message from user QUEUE_MANAGE on MAUAX1 -NONAME-W-NOMSG, Message number 00000000 Message from user QUEUE_MANAGE on MAUAX1 -SYSTEM-F-EXQUOTA, process quota exceeded Crash Summary Information: -------------------------- Current Process: QUEUE_MANAGER Current Image: Failing PC: FFFFFFFF.D24FAAE4 IO_ROUTINES_PRO+02AE4 Failing PS: 00000000.00000000 Module: IO_ROUTINES Offset: 0002EAE4 Images Affected: - [SYS$STARTUP]VMS$CONFIG-050_JOBCTL.COM o Issuing SYSMAN Class Scheduler commands to a node that does not support Class Scheduling, causes the SMI server on that node to aborted. See example output below: SYSMAN> do show time %SYSMAN-I-OUTPUT, command execution on node NODE1 16-NOV-2000 14:34:29 %SYSMAN-I-OUTPUT, command execution on node NODE2 16-NOV-2000 14:34:29 SYSMAN> class add XX1 /pri=(mon,tue,wed,thur,fri,nosat,nosun)/cpu=(prim,0-23=25 ,sec,0-23=100) %SYSMAN-I-NODERR, error returned from node NODE1 -SMI-E-NAMCONFLICT, class name already exists in class scheduler database file %SMI-I-CLASSEXISTS, scheduling class already exists on node NODE2 -- COVER LETTER -- Page 4 12 June 2001 %SYSMAN-I-NODERR, error returned from node NODE3 -SMI-E-ABORT, SMI Server has aborted SYSMAN> do show time %SYSMAN-I-OUTPUT, command execution on node NODE1 16-NOV-2000 14:35:20 %SYSMAN-I-OUTPUT, command execution on node NODE2 16-NOV-2000 14:35:20 %SYSMAN-I-OUTPUT, command execution on node NODE3 %SYSMAN-I-NODERR, error returned from node NODE3 -SMI-E-NOSERVER, SMI Server not running in target node Images Affected: - [SYSLIB]SMI$SHR.EXE o The system crashes with "Kernel stack invalid" after an AUTOGEN reboot. Large values of NPAGEDYN could result in values computed for NPAGEVIR that are too large to fit into the available system space. Images Affected: - [SYSUPD]AUTOGEN.COM - [SYSEXE]AGEN$FEEDBACK.EXE o The system crashes with a negative BALSETCNT while an AUTOGEN reboot is in progress following an increase in VCC_MAXSIZE. VCC_MAXSIZE may be sized too big to fit into the system. Images Affected: - [SYSUPD]AUTOGEN.COM - [SYSEXE]AGEN$FEEDBACK.EXE o The BALSETCNT error message does not display the VCC_MAXSIZE limit, which would help determine how to set VCC_MAXSIZE properly. Images Affected: - [SYSUPD]AUTOGEN.COM - [SYSEXE]AGEN$FEEDBACK.EXE o AUTOGEN's DIGITAL command language (DCL) arithmetic overflows and generates incorrect data. See the example below: $ SEARCH SYS$SYSTEM:AGEN$FEEDBACK.DAT;373 HDR,DIR DIRHITS = 559996826 DIRATTEMPTS = 694808213 -- COVER LETTER -- Page 5 12 June 2001 HDRHITS = 289151114 HDRATTEMPTS = 394307611 ACP_DIRCACHE_CUR = 2000 AUTOGEN will then perform operations similar to the following, which overflows and turns negative. $WRITE report " Attempt rate: ",(HDRattempts*10)/feedback_uptime,"attempts Csc64 $ write sys$output 394307611*10 -351891186 In this case, no warnings were generated to the feedback report. Images Affected: - [SYSUPD]AUTOGEN.COM - [SYSEXE]AGEN$FEEDBACK.EXE o Previously authorized SYSMAN commands fail on remote systems with insufficient privilege errors. Images Affected: - [SYSEXE]SMISERVER.EXE 6 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_1 : To be installed by all customers 7 INSTALLATION INSTRUCTIONS: Install this kit with the {Installation Utility} utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS721H1_MANAGE /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. -- COVER LETTER -- Page 6 12 June 2001 Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt This kit requires a system reboot. Compaq 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. Copyright (c) Compaq Computer Corporation, 2001 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.