OpenVMS ALPBACK05_071 Alpha V7.1 Backup Utility ECO Summary

TITLE: OpenVMS ALPBACK05_071 Alpha V7.1 Backup Utility ECO Summary NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 1998, 1999. All rights reserved. Modification Date: 24-SEP-1999 Modification Type: Updated Kit Supersedes ALPBACK04_071 NOTE: The documentation for this kit calls out a dependency on the ALPMOUN05_071 remedial kit. This MOUNT kit has been superseded by ALPMOUN06_071, and that kit was superseded by ALPMOUN07_071. PRODUCT: OpenVMS Alpha COMPONENT: BACKUP Utility SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: ALPBACK05_071 ECO Kits Superseded by This ECO Kit: ALPBACK04_071 ALPBACK03_071 ALPBACK02_071 ALPBACK01_071 ECO Kit Approximate Size: 1530 Blocks Kit Applies To: OpenVMS Alpha V7.1, V7.1-1H1, V7.1-1H2 System/Cluster Reboot Necessary: No Installation Rating: INSTALL_3 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. Kit Dependencies: The following remedial kit(s) must be installed BEFORE installation of this kit: None In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: ALPSYSA02_071 ALPDISM01_071 ALPINIT01_071 ALPMOUN05_071 [superseded; latest is ALPMOUN07_071] ALPMTAA01_071 ECO KIT SUMMARY: An ECO kit exists for BACKUP on OpenVMS Alpha V7.1 through V7.7-1H2. This kit addresses the following problems: PROBLEMS ADDRESSED IN ALPBACK05_071 KIT o BACKUP/BY_OWNER %BACKUP-F-BADOPTVAL when using Identifier String An %BACKUP-F-BADOPTVAL error can occur when using an Identifier String for a BACKUP/BY_OWNER qualifier value. For example: $ BACKUP SOURCE:*.*/BY_OWNER=USER TAPE:A.BCK/SAV %BACKUP-F-BADOPTVAL, invalid callable interface option value, argument position 7, option type = 59, option value = 2147549409 Image(s) Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE Problem Analysis: An OWNER UIC check assumes that values would be less or equal to UIC$K_WILD_GROUP. However, Rights Identifiers typically have values greater than UIC$K_WILD_GROUP. For a solution, OWNER_IN_VALUE and OWNER_OUT_VALUE checks simply determine if the [unsigned] value is greater than zero (0) or equal to zero (0). (OWNER_OUT_VALUE checks do not allow wildcard group or member values.) If a wildcard value is specified for the OWNER output qualifier value, an ININVQALVAL message is now output, instead of a BADOPTVAL. Hence, the latest version of BACKUP is more compatible with prior versions of BACKUP. In addition, the BACKUP Version Identifier Strings will be updated to reflect this fix (controlled by BACKLUPBLD.COM). Work-arounds: None. o Bugfix BACKUP API compatibility with prior versions Using OpenVMS VAX V7.1 [SSB] as the basis for API definitions, ONLY add new definitions (since V7.1). An obsolete reference to STRUCTURE (keyword/qualifier) was also removed. Image(s) Affected: - None Problem Analysis: Results of incremental changes to BACKUP API definitions were not compared to prior version definitions. Although HSM products used their own modified version of BACKUP, in the future they will use main-line BACKUP functions. Work-arounds: None. o Backport bug fixes from V7.2R to V7.1R The following five problems are fixed: 1. BACKUP/SINCE and /BEFORE produces unexpected results. 2. BACKUP/OWNER=FRED results in an error. 3. A process dump cannot be produced if BACKUP fails. 4. Using BACKUP/ENCRYPT in BATCH results in an %BACKUP-F-ENCNOTSUP error. 5. The default for /BEFORE=(value) is now the same as /SINCE=(value). Image(s) Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE - [CLD]BACKUP.CLD Problem Analysis: The problems occurred because: 1. A check for conflicting qualifier usage was corrected and was deferred to API checks. The solution was to correct a check for conflicting qualifier usage and it was also deferred to API checks. 2. Identifier [valid] values are now assumed to be < UIC$K_WILD_GROUP The solution was to change a UIC validity test to pass a user-specified value to system service(s). 3. A handler was declared which prevented signal and mechanism information from reaching handlers external to BACKUP. The solution was to allow a process logical name definition to disable registering of the API handler. 4. Encryption initialization was deferred to the API parameter checks, but the test for this initialization status return was not removed. The solution was to defer encryption initialization to the API parameter checks, but not remove the test for the initialization status return. 5. Having the default /BEFORE=(value) the same as /SINCE= (value) is a new customer-requested feature. The design was to specify default="TODAY" for the DCL command line qualifier (/BEFORE). Work-arounds: None. PROBLEMS ADDRESSED IN ALPBACK04_071 KIT: o After installation of the ALPBACK03_071 remedial kit, BACKUP commands could not be executed. Users saw the following error message: %CLI-F-SYNTAX, error parsing 'SNAPSHOT' -CLI-E-ENTNF, specified entity not found in command tables PROBLEMS ADDRESSED IN ALPBACK03_071 KIT: o MailBox Read synchronization problem in MME_MBX_COMM A possible system crash occurs during Host Based RAID Unbinds with MME code enabled. A mailbox read synchronization problem causes the crash. This problem only occurs when a host-based RAID UNBIND command is done while an MME-based application is running. This problem may occur in several different code areas of the operating system. In order to eliminate all instances of this problem, the following remedial kits (or their supersedants) will also need to be installed: ALPSYSA02_071 ALPDISM01_071 ALPMOUN05_071 ALPINIT01_071 ALPMTAA01_071 PROBLEMS ADDRESSED IN ALPBACK02_071 KIT: o A %BACKUP-F-WAITIDLEBCB error is possible when a media error is encountered with the BACKUP utility. PROBLEMS ADDRESSED IN ALPBACK01_071 KIT: o Four major problems occurred: 1. Incremental restores may get an INCDELERR error message and loop continuously when attempting to perform a directory tree delete on a specific DIR filespec. The following text is an example of the message syntax: %BACKUP-E-INCDELERR, error deleting $4$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1 -SYSTEM-W-NOSUCHFILE, no such file 2. A possible ACCVIO (access violation) can occur when backing up volume sets, particularly individual relative volumes. 3. A problem with the /OWNER and /BY_OWNER qualifiers occurred with an error message such as: BACKUP/LOG TEST.BCK/SAVE/BY_OWNER=[20,0] X.X %BACKUP-F-BADOPTVAL, invalid callable interface option value, argument position 7, option type = 59, option value = 1048576 4. Since upgrading to OpenVMS V7.1 from OpenVMS V6.2, BACKUP procedures could not be run. BACKUP fails with an ACCVIO error PC=0000000000000000. Although the problem matches the contents of the article listed below, workarounds described in the article failed at the customer site. Identifier: CTI_SRC970415001958 VEGA Item Number: 55327 Title:[OpenVMS] BACKUP Fails W/ACCVIO At PC=0000000000000000 INSTALLATION NOTES: The system does not need to be rebooted after this kit is installed. However, if you have other nodes in your OpenVMS VMScluster, they should be rebooted or you should install this kit on each system in order to make use of the new image(s).

This patch can be found at any of these sites:

Files on this server are as follows:

alpback05_071.README
alpback05_071.CHKSUM
alpback05_071.CVRLET_TXT
alpback05_071.a-dcx_axpexe
alpback05_071.CVRLET_TXT