ECO NUMBER: VAXDOSD09_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXDOSD09_062 2 KITS SUPERSEDED BY THIS KIT: VAXDOSD08_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: VAXCLUSIO01_062, VAXSYSA02_062 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]AGEN$FEEDBACK.EXE (new image) o [SYSEXE]VMB.EXE (new image) o [SYSUPD]AUTOGEN.COM (new file) o [SYSHLP]SYSGEN.HLB (new file) 5 PROBLEMS ADDRESSED IN VAXDOSD09_062 KIT o The VAXDOSD08_062 remedial kit was replacing the VMB.EXE image but a WRITEBOOT on the new image was not being done. o The VAXDOSD08_062 and VAXSYSA02_062 kits both contained EXCEPTION.EXE. The image in the VAXSYSA02_062 was a newer image. This caused installation conflict errors if the -- COVER LETTER -- Page 2 17 May 1999 VAXDOSD08_062 kit was installed after the VAXSYSA02_062 kit. To correct the problem, since it is the older image, the EXCEPTION.EXE has been removed from the VAXDOSD kit and the VAXSYSA02_062 has been made a dependency. 6 PROBLEMS ADDRESSED IN VAXDOSD08_062 KIT o A 6000-class VAX machine, that booted off a DSSI disk, kept getting into the DOSD code. The system then concluded that the configuration could not support DOSD and terminated at TESTFILES. Member disks of a shadowed boot disk were tested for DOSD support, before the configuration was tested for support eligibility. The problem appeared to be complicated more because DUMPFILE_DEVICE was defined to the string "SYS$SYSDEVICE:". 7 PROBLEMS ADDRESSED IN VAXDOSD07_062 KIT o If the VAXCLUSIO01_062 remedial kit was installed before the VAXDOSD06_062 kit, the VAXDOSD06_062 kit would fail to install. o Attempting to write a full dump file on a system with 2GB of memory failed with various error messages such as: **** Total memory too big for SDA, attempting subset dump This failure was due to a restriction in BUGHCECKLD which will be removed as part of this changespec. or **** Memory dump complete, dump written to unit number 598 This failure indicated dump successfully written when in fact the system wrote nothing to the dump file. or Error writing 4290773008 block(s), starting at VBN 1 - status = 00000CDA This failure was due to an incorrect value for a disk transfer being passed to PABTDRIVER due to a calculation error in BUGCHECKLD. In addition, the dump writing status as indicated by the writing of dots on the console was not working for 2GB dumps. Note that, if your dump files are 2 GB, you may see the following error message: -- COVER LETTER -- Page 3 17 May 1999 %SYSINIT-E, error reading system dump file error log buffers, status = 00000014 This error does not affect the functionality or integrity of the dump. The contents of the error log buffers are in the crash dump file and can be retrieved by issuing the command: SDA> clue errlog This problem will be corrected in a future OpenVMS Alpha remedial kit 8 PROBLEMS ADDRESSED IN VAXDOSD06_062 KIT o The VAX 7000 console revision referenced was no longer valid. This kit updates the console requirement information listed under the section "Problems addressed in VAXDOSD01_062 kit". o The V6.2 saveset needed the AUTOGEN.COM and SMISERVER.EXE images. 9 PROBLEMS ADDRESSED IN VAXDOSD05_062 KIT o The KITINSTAL.COM in the VAXDOSD04_062 kit included a "set verify" command that caused unnecessary text to be output to the console. There are no new DOSD problem fixes in this kit. If you have installed the VAXDOSD04_062 kit you do not need to install the VAXDOSD05_062 kit. 10 PROBLEMS ADDRESSED IN VAXDOSD04_062 KIT o The KITINSTAL procedure for the VAXDOSD03_062 did not copy the VMB.EXE and SYSBOOT.EXE images contiguously. This prevented the system from re-booting after the kit was installed. 11 PROBLEMS ADDRESSED IN VAXDOSD03 KIT DOSD (Dump off System Disk) will probably guarantee that we will see dumps which would not fit in a 1GB user area. SDA's crash dump analysis is being changed to use RMS I/O to read the information instead of using $CRMPSC to map the dump file as part of the user address space. This change will also give two additional benefits: -- COVER LETTER -- Page 4 17 May 1999 o Analyze crash dumps with smaller virtual page count in the analyzing process. o Capability to analyze crash dumps using FAL on remote machines. 12 PROBLEMS ADDRESSED IN VAXDOSD02_062 KIT o Add the SYSGEN.EXE and SYSGEN.HLB images to allow the VAX7000 to use the full range of the DUMPSTYLE parameter. 13 PROBLEMS ADDRESSED IN VAXDOSD01_062 KIT o Under the following restricted set of configurations, OpenVMS VAX customers can write the system dump to a device other than the system disk. To enable the bugcheck code to write the dump to an alternate device, you must correctly enable the DUMPSTYLE system parameter. See the DUMPSTYLE system parameter in the OpenVMS System Management Utilities Reference Manual for the values (relevant excerpt from that manual is included below). Configuration Requirements: If the following configuration requirements are met, it will be possible to configure and use a device other than the system disk for writing the system crash dump file: 0 The system must be connected directly to and must boot from CI controllers. 0 The dump device must physically connect to the same two HSx CI controllers as the boot device. 0 The dump device directory structure must resemble the current system disk structure. The [SYSn.SYSEXE]SYSDUMP.DMP file will reside there, using the same boot time system root. On OpenVMS V6.2, you can use AUTOGEN to create this file. In the MODPARAMS.DAT file, the following symbol prompts AUTOGEN to create the file: DUMPFILE_DEVICE = $nnn$ddcuuuu There is support for this feature under OpenVMS VAX V6.1. 0 The volume label can be up to twelve characters long. The ASCII string DOSD_DUMP must be part of this volume label. For example, all of the following are valid volume labels: -- COVER LETTER -- Page 5 17 May 1999 DOSD_DUMP, DOSD_DUMP_12, 12_DOSD_DUMP. This label is read and retained in a memory boot data structure. 0 The dump device cannot be part of a volume set. Digital recommends that the dump device not be part of a shadow set. 0 The dump device cannot be MSCP unit zero (0); only unit numbers 1 to 4095 ( 1 - FFF ) will be supported. You can designate the dump device as follows: - On VAX 7000 configurations, by using bits 16 through 27 of the DUMPSTYLE system parameter. - On configurations other than the VAX 7000, by using bits 16 through 27 of register 3 (R3). This portion of the register can specify the desired dump device. The VAX7000 has special DUMPSTYLE requirements (listed below) to implement this feature. o Excerpt from the OpenVMS V6.2 System Management Utilities Reference Manual Parameters DUMPSTYLE DUMPSTYLE specifies the method of writing system dumps. DUMPSTYLE has AUTOGEN and DYNAMIC attributes. DUMPSTYLE is a 32-bit mask with the following values. ___________________________________________________________ Bit___________Mask______Description________________________ 0 00000001 0 = Full dump (SYSGEN default). The entire contents of physical memory will be written to the dump file. 1 = Selective dump. The contents of memory will be written to the dump file selectively to maximize the usefulness of the dump file while conserving disk space. 1 00000002 0 = Minimal console output. 1 = Full console output (includes stack dump, register contents, so on). -- COVER LETTER -- Page 6 17 May 1999 2 (VAX 00000004 0 = Dump to system disk. only)[1] 1 = Dump off system disk (DOSD) to an alternate disk. 3 (Alpha 00000008 0 = Do not compress. only)[2] 1 = Compress. (See note below.) 4 - 14 Reserved to Digital. 15 [3] 00008000 0 = Disable use of bits 16 - 27. 1 = Enable use of bits 16 - 27. 16 - 27 0FFF0000 Range of DOSD unit numbers. 28 - 31 Reserved to Digital. [1]Alpha systems do not support dumping to an alternate disk. [2]VAX systems do not support dump compression. [3]Specific to VAX 7000s. o Implementation Requirements - VAX6000 Systems Register R3 must be used to stipulate the DOSD device unit number. Note that Bit 31 must be a zero,therefore the system disk cannot be a Volume Shadow Phase I shadow set device. R3 = 0001EX006 Bits# | \ / \ / | | | +-------> (11 -> 00) Boot Unit Number | | | | | +-------------> (27 -> 16) DOSD Unit Number. | Unit 30 is hex 1E | +-----------------> (31) Must be Zero $MC SYSGEN $! For a FULL dumpstyle dump, on the DOSD device. SYSGEN> SET DUMPSTYLE %X00000004 SYSGEN> WRITE CURRENT $! For a Sub-set dumpstyle dump,on the DOSD $! device. SYSGEN> SET DUMPSTYLE %X00000005 SYSGEN> WRITE CURRENT SYSGEN> EXIT $ -- COVER LETTER -- Page 7 17 May 1999 Reboot the VAX6000 o Implementation Requirements - VAX7000 Systems VAX7000 Use of DUMPSTYLE for DOSD In order to stipulate the dump device on this platform, the SYSGEN parameter DUMPSTYLE must be used. Bits sixteen (16) through twenty-seven (27) will be checked by SYSBOOT for the unit number of the dump device ... IF bit fifteen (15) is also set. For example, to use unit thirty (30) as the dump device, and have a full (as versus a subset) dump take place: $MC SYSGEN SYSGEN> SET DUMPSTYLE %X001E8002 SYSGEN> WRITE CURRENT Reboot the VAX7000 Bit# %X001E8006 / (0) = 0 Full Dump \ / | | / (1) = 1 Full Console Output at | | | / Bug Check | | +------> (2) = 1 Use Dump Off System | | \ Disk device | | \ (3) = · | | | | / (12) = · | | / (13) = · | +---------> (14) = · | (15) = 1 Enable Flag for bits | 27 - 16 for DOSD on | VAX7000 +------------> (27->16) DOSD Unit Number ... Unit 30 in hex o VAX7000 CONSOLE REQUIREMENT In order to use DUMPSTYLE for DOSD on VAX 7000 type systems you must install version 4.3 or later of the VAX 7000 console firmware. Contact your Digital Service Representative to get the latest version of the console firmware. Later versions of the VAX 7000 console firmware support all LASER VAX processors and the BOOT_ALT environment variable, which allows the operator to specify the alternate path to the system disk for the console to use during shutdown in the event of a path failover. All consoles with Version numbers less than V4.0 will support the VAX 7600 system only. -- COVER LETTER -- Page 8 17 May 1999 Copy the latest console image to a MOM$SYSTEM: area on a system that can serve as a boot-host to the VAX7000. Prepare and update the console by doing the following at the console prompt of the target VAX7000 system. >>> show * .. record current environment variable settings. NOTE: If the patch for the HSJ single path problem described in BLITZ article TD# 1566 has been applied to this system, you must erase that patch before proceeding. To do this, type: >>> build eeprom >>> update -e ka7aa* Now proceed with installing the update: >>> set auto_action halt >>> boot -flag 0,0,0 -file vax7000_v07_3 exa0 # or fxa0 ... LFU is booted and run, update ka7aa*, exit ... >>> build eeprom >>> update -e ka7aa* >>> build nvr # on each cpu >>> set config >>> set xxx yyy # restore environment # variable settings # previously recorded. ---------------------------------------------------------- This is an example in the use of the 'BOOT_ALT' environment variable: The system disk (dua22) is dual ported between HSC00 and HSC02. In the following console log extract, dua21, dua22, and dua23 are all seen by HSC00, and dua22 is also seen by HSC02. >>> show device cixcd0 polling for units on cixcd0, slot 2, xmi0... · · dua21.14.0.2.0 DUA21 (HSC00) RA82 dua22.14.0.2.0 DUA22 (HSC00) RA82 dua23.14.0.2.0 DUA23 (HSC00) RA82 · · dua22.2.0.2.0 DUA22 (HSC02) RA82 · · >>> ^ | This - digit, after the first period, indicates -- COVER LETTER -- Page 9 17 May 1999 HSC NODE number. HSC00 bus node number 14 decimal. HSC02 bus node number 02 decimal. dua22.14.0.2.0 || || | | +--- hose || || | +----- slot (xmi) || || +------- channel || ++-------- node (primary HSC) ++----------- unit The system operator would set the BOOTDEF_DEV to attempt to boot dua22 first through the HSC00,to boot through the HSC02. >>> set bootdef_dev dua22.14.0.2.0, dua22.2.0.2.0 bootdef_dev set to dua22.14.0.2.0,dua22.2.0.2.0 >>> Define the BOOT_ALT environment variable to indicate to the console alternate HSC paths exist. The console then can attempt to locate the unit, if the original boot path no longer has the unit available, when the system is shut down or it crashes. >>> create -nv boot_alt 2,E boot_alt set to 2,E >>> The first argument in 'boot_alt' correlates to the first argument in the 'bootdef_dev' string, the second argument to the second string, etc. bootdef_dev dua22.14.0.2.0, dua22.2.0.2.0 ^^ ^ | | and its alternate path | | v v boot_alt 2 , E When the system crashes, a first attempt is made to locate the system disk - on the dua22.14.0.2.0 path ... if the device cannot be found, the console will replace the HSC node value in that argument with the value it finds in the first argument of boot_alt and try that path next. -- COVER LETTER -- Page 10 17 May 1999 14 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. 15 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 VAXDOSD09_062 [location of the saveset] The saveset location may be a tape drive, 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, 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 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.