SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS VMS73_RMS-V0300 Alpha V7.3 RMS ECO Summary

TITLE: OpenVMS VMS73_RMS-V0300 Alpha V7.3 RMS ECO Summary Modification Date: 11-APR-2002 Modification Date: Not Applicable Modification Type: NEW KIT NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. For OpenVMS savesets, the name of the compressed saveset file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS saveset is copied to your system, expand the compressed saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe. For PCSI files, once the PCSI file is copied to your system, rename the PCSI file to kitname.pcsi-dcx_axpexe, then it can be expanded by typing RUN kitname.pcsi-dcx_axpexe. The resultant file will be the PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 2002. All rights reserved. OP/SYS: OpenVMS Alpha COMPONENT: RMS SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VMS73_RMS-V0300 DEC-AXPVMS-VMS73_RMS-V0300--4.PCSI ECO Kits Superseded by This ECO Kit: None ECO Kit Approximate Size: 2768 Blocks Kit Applies To: OpenVMS Alpha V7.3 System/Cluster Reboot Necessary: Yes Rolling Re-boot Supported: Yes Installation Rating: INSTALL_1 1 - To be installed on all systems running the listed version(s) of OpenVMS. Kit Dependencies: The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS73_UPDATE-V0100 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None ECO KIT SUMMARY: An ECO kit exists for RMS on OpenVMS Alpha V7.3. This kit addresses the following problems: PROBLEMS ADDRESSED IN VMS73_RMS-V0300 KIT: o Fix for RMS global buffer hang due to abort ($delprc) rundowns. An application may experience a hang under the following conditions: - RMS global buffers are enabled on some files. - Many processes are terminated with $delprc (e.g., STOP/ID) when files are still open. - The application is restarted after the process terminations without rebooting the system. The symptom for this problem is that during the restart of the application, a process enters a tight loop in executive mode. Once encountered, a system reboot is required to clear the problem. Images Affected: [SYS$LDR]RMS.EXE [SYSLIB]SDARMS$SHARE.EXE o RMS fix for inconsistent secondary key index structure. Any application that does a lot of deleting or does updates that change a no duplicate secondary key value to another value in an indexed file is a potential candidate for this problem. An ANALYZE/RMS_FILE of the indexed file reports the following error for a secondary key: "Index bucket references missing data bucket with VBN nnn" The problem may be that the secondary index structure has duplicate index value entries and there should never be duplicates in the index structure. If the secondary index allows a binary search (is uncompressed), records could be hidden using an exact secondary key lookup. This problem results from the entire space being inappropriately reclaimed for the physically last SIDR record in some secondary data bucket which contains only deleted entries. This problem is restricted to an indexed file with a secondary key that allows no duplicates. The primary key contents will be intact and correct, and a convert of the file will rebuild the secondary indexes and leave the file in a consistent state. Images Affected: [SYS$LDR]RMS.EXE o Fix to prevent the CONVERT/RECLAIM utility from producing an inconsistent index structure in an indexed file during a reclamation. An ANALYZE/RMS_FILE reports the following error: "Index bucket references missing data bucket with VBN nnn" A level 1 index record associated with a data (level 0) bucket that was reclaimed was not removed from the index bucket, as it should have been. It is extremely difficult to detect in advance of doing a convert/reclaim whether an indexed file is vulnerable if a reclaim were applied to it. For example, one condition is that one of the initial level 1 index buckets associated with data buckets eligible for reclamation has some condition (for example, only one index record) that will cause a rollback of a removed index record during a reclamation. Without the fix, doing a full convert (without the /RECLAIM qualifier) ensures avoiding this problem. Images Affected: [SYSEXE]RECLAIM.EXE [SYSEXE]CONVERT.EXE [SYSLIB]CONVSHR.EXE o Fix to the CONVERT utility to prevent the signal of a fatal read error (CONV-F-READERR) with an RMS-S-NORMAL secondary status when callable convert is invoked within a threaded application. This correction prevents the erroneous error signal when the end of the input file is reached. Although callable convert is not a thread safe application, it is possible to invoke the callable interface from within a single instance within a single thread. Images Affected: [SYSEXE]CONVERT.EXE [SYSLIB]CONVSHR.EXE o Fix to the CONVERT utility to prevent a convert which uses either network or tape input from creating an empty output indexed file. Images Affected: [SYSEXE]CONVERT.EXE [SYSLIB]CONVSHR.EXE INSTALLATION NOTES: 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. INSTALLATION INSTRUCTIONS: 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 VMS73_RMS /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt SPECIAL INSTALLATION INSTRUCTIONS: o 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V3.0 - De-assign the logicals assigned For example, a sample command file to install the VMS73_RMS-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS73_RMS/PROD=DEC/BASE=AXPVMS/VER=V3.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit All trademarks are the property of their respective owners.



Files on this server are as follows:

dec-axpvms-vms73_rms-v0300--4.README
dec-axpvms-vms73_rms-v0300--4.CHKSUM
dec-axpvms-vms73_rms-v0300--4.pcsi-dcx_axpexe
vms73_rms-v0300.CVRLET_TXT

privacy and legal statement