ECO NUMBER: VAXUPDATE01_072 PRODUCT: OpenVMS VAX OPERATING SYSTEM 7.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 7.2 COVER LETTER 1 KIT NAME: VAXUPDATE01_072 2 KITS SUPERSEDED BY THIS KIT: VAXPTHR01_072, VAXDRIV01_072 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 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 V7.2 4.2 Files patched or replaced: o [SYSEXE]BACKUP.EXE (new image) o [SYSLIB]BACKUPSHR.EXE (new image) o [SYSLIB]CONVSHR.EXE (new image) o [SYSEXE]CSP.EXE (new image) o [SYSLIB]DEBUG.EXE (new image) o [SYSLIB]DEBUGSHR.EXE (new image) o [SYS$LDR]DKDRIVER.EXE (new image) o [SYS$LDR]DUDRIVER.EXE (new image) o [SYS$LDR]ECDRIVER.EXE (new image) -- COVER LETTER -- Page 2 25 August 1999 o [SYS$LDR]EFDRIVER.EXE (new image) o [SYS$LDR]EPDRIVER.EXE (new image) o [SYS$LDR]EPJDRIVER.EXE (new image) o [SYS$LDR]ESDRIVER.EXE (new image) o [SYS$LDR]ESS$LASTDRIVER.EXE (new image) o [SYS$LDR]ESS$MADDRIVER.EXE (new image) o [SYS$LDR]ETDRIVER.EXE (new image) o [SYS$LDR]EXDRIVER.EXE (new image) o [SYS$LDR]EZDRIVER.EXE (new image) o [SYS$LDR]F11AACP.EXE (new image) o [SYS$LDR]F11BXQP.EXE (new image) o [SYSEXE]F11CACP.EXE (new image) o [SYSEXE]F11DACP.EXE (new image) o [SYS$LDR]FCDRIVER.EXE (new image) o [SYS$LDR]FQDRIVER.EXE (new image) o [SYS$LDR]FXDRIVER.EXE (new image) o [SYSEXE]LANCP.EXE (new image) o [SYS$STARTUP]LICENSE_CHECK.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) o [SYS$LDR]LOGICAL_NAMES.EXE (new image) o [SYS$LDR]LTDRIVER.EXE (new image) o [SYSEXE]MAIL.EXE (new image) o [SYSLIB]MAILSHR.EXE (new image) o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) o [SYSEXE]MIME.EXE (new image) o [SYS$LDR]MKDRIVER.EXE (new image) o [SYSLIB]MOUNTSHR.EXE (new image) -- COVER LETTER -- Page 3 25 August 1999 o [SYSEXE]NETACP.EXE (new image) o [SYSEXE]OPCOM.EXE (new image) o [SYS$LDR]PAGE_MANAGEMENT.EXE (new image) o [SYSEXE]PCSI$MAIN.EXE (new image) o [SYSLIB]PCSI$SHR.EXE (new image) o [SYS$LDR]PKBDRIVER.EXE (new image) o [SYS$LDR]PKCDRIVER.EXE (new image) o [SYS$LDR]PKRDRIVER.EXE (new image) o [SYS$LDR]PUDRIVER.EXE (new image) o [SYSLIB]PTHREAD$DBGSHR.EXE (new image) o [SYSLIB]PTHREAD$RTL.EXE (new image) o [SYS$LDR]RMS.EXE (new image) o [SYSEXE]SDA.EXE (new image) o [SYS$LDR]SECURITY.EXE (new image) o [SYSEXE]SETSHOSECUR.EXE (new image) o [SYS$LDR]SHDRIVER.EXE (new image) o [SYSEXE]SHOW.EXE (new image) o [SYS$LDR]SYS$IPC_SERVICES.EXE (new image) o [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE (new image) o [SYSEXE]SYSGEN.EXE (new image) o [SYSEXE]SYSINIT.EXE (new image) o [SYSMSG]SYSMSG.EXE (new image) o [SYS$LDR]TUDRIVER.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) o [SYS$LDR]WORKING_SET_MANAGEMENT.EXE (new image) o [SYS$LDR]XEDRIVER.EXE (new image) o [SYS$LDR]XQDRIVER.EXE (new image) -- COVER LETTER -- Page 4 25 August 1999 o [SYSLIB]VMSDEBUGUIL.UID (new file) o [SYSUPD]BACKUP.CLD (new file) o [SYSUPD]MOUNT.CLD (new file) o [SYSUPD]PCSI.CLD (new file) 5 PROBLEMS ADDRESSED IN VAXUPDATE01_072 KIT o If a TZ87 is powered off and on after system boot, a MOUNT command issued to the device will cause the process to hang. Hence the MOUNT never completes. Image(s) Affected: - [SYS$LDR]PKBDRIVER.EXE - [SYS$LDR]PKCDRIVER.EXE - [SYS$LDR]PKRDRIVER.EXE o During a standalone backup operation, using an Infoserver to install OpenVMS on VAX2000 systems results in a fatal "volume not valid" error message. Image(s) Affected: - [SYS$LDR]ESS$LASTDRIVER.EXE o After an I/O to SHDRIVER, a RMSBUG crash (fatal bugcheck) can occur when the shadow driver returns R0=0 (zero status IOSB) to RMS on completion of an outstanding I/O request. Crashes result from application code not being able to handle the zero status. Image(s) Affected: - [SYS$LDR]SHDRIVER.EXE o If any send or receive failures are reported by the Ethernet LAN driver, a LATCP SHOW LINK/COUNTER command displays incorrect values in other LAN counter fields. Image(s) Affected: - [SYS$LDR]LTDRIVER.EXE -- COVER LETTER -- Page 5 25 August 1999 o When two processes are competing to dismount a volume, one process may be just a bit faster than the other. Hence, it can delete the VCB and other structures before the second process has time to finish up its processing. The result is in an UNXSIGNAL/ACCVIO crash. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o A device reporting a read error (SS$_PARITY) during read/write processing in the XQP, will attempt to record the bad blocks and FID in the BADLOG.SYS file. When the internal close operation occurs (on BADLOG), the system XQPERR bugchecks when it finds the process's dirty buffers have not been written out before cleanup. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o An UNXSIGNAL/ACCVIO error can occur at module F11BXQP. This problem can occur during MOUNT, when the primary volume is not yet mounted. Specifically, a race condition occurs. When a process is mounting Volume 2 of a Bound Volume Set (BVS), but Volume 1 (first member of set) of the BVS is not completely mounted at the time. In this case, the system will get an UNXSIGNAL/ACCVIO error at module F11BXQP. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o Disk drives with a capacity of greater than 8.6 GB have their capacity truncated to 8.6 GB upon Mount. Image(s) Affected: - [SYS$LDR]DKDRIVER.EXE - [SYS$LDR]MKDRIVER.EXE o Two problems regarding use of the MAIL$INTERNET_TRANSPORT logical can occur. 1. Defining MAIL$INTERNET_TRANSPORT forces the use of an alternate mail image, even when DECnet should be used. -- COVER LETTER -- Page 6 25 August 1999 2. If the user includes a different transport on the TO line, it is treated as part of the address and passed on the the image defined by MAIL$INTERNET_TRANSPORT, causing delivery errors. Image(s) Affected: - [SYSLIB]MAILSHR.EXE o MOUNT/SYSTEM fails with a %MOUNT-F-IVBUFLEN error, when attempting to MOUNT an ISO 9660 CDROM, which has a volume label of more than 27 characters. (The ISO 9660 specification allows volume labels of 32 characters.) Image(s) Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o A LANCP SHOW DEVICE/COUNTER command incorrectly shows sends and receives failure counts. Image(s) Affected: - [SYSEXE]LANCP.EXE o A system with a KFQSA adapter does not configure local DSSI disks. Image(s) Affected: - [SYS$LDR]PUDRIVER.EXE o The IPC system service does not support the special event flag EFN$C_ENF. Image(s) Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE o A VBNMAPFAIL/OUTSWPERR bugcheck occurs if the Page/Swap file header is corrupted. Specifically, the problem occurs when the page or swap file is improperly created, such as the system crashing in the middle of the creation of the file. The system then reboots and the file is mapped. However, WCB$L_NMAP is 0, indicating no retrieval pointers are established. -- COVER LETTER -- Page 7 25 August 1999 Image(s) Affected: - [SYSEXE]SYSGEN.EXE - [SYSEXE]SYSINIT.EXE o A MSCPCLASS fatal error can be detected by the MSCP class driver. While running CTM_HIGH_IO, a local path failover can cause this MSCPCLASS bugcheck. Note that the code can believe it has a MSCP server load balance request, when in fact a direct path is in use. Image(s) Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o Incomplete SDA displays for DSA devices occur. Image(s) Affected: - [SYSEXE]SDA.EXE o After the MSCP server loses connections to a local MSCP device, shadowset members are removed from the set and then the system crashes with a SHADDETINCON bugcheck. Image(s) Affected: - [SYS$LDR]DUDRIVER.EXE o A system crash with a SHADDETINCON bugcheck can occur in the SHD_LOCK module's SHLK$MERGE_SIGNAL routine. Image Affected: - [SYS$LDR]SHDRIVER.EXE o ACMS SI, Rdb SQL and/or DECdtm $ADD_BRANCH(W) calls can fail with an IPC-E-BCKTRNSFAIL error. Consequently, a DECnet translation failure results. The problem can occur when DECnet Plus also is running, where a distributed transaction is being initiated. In addition, DECdtm would also be passing a node name to DECnet Plus, requesting a DECnet Plus equivalent node name. Image(s) Affected: -- COVER LETTER -- Page 8 25 August 1999 - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE o The /POLICY=REQUIRE_MEMBERS and /POLICY=VERIFY_LABELS switches were added to MOUNT. This change is an enhancement. The following switch and options were added to MOUNT: 1. /POLICY=REQUIRE_MEMBERS - force all specified members to be available for MOUNT to occur The /POLICY=REQUIRE_MEMBERS option is used in disaster-tolerant configurations where another site may have a more recent disk that is not available. In effect, this option will force more human decision making. 2. /POLICY=VERIFY_LABELS - all copy targets must have label "SCRATCH_DISK" or they will not be added to the set The volume must be ODS2 and have a valid file structure. The new option will force users to use alternate volume labels. One of the biggest causes of "a wrong disk being added to a shadow set" is mistyped commands. If users are given a way to be sure that they only added "scratch" disks to shadow sets, then they will be less likely to lose data. This option is similar to /CONFIRM, except that it can be used in command procedures as well, without immediate operator intervention. It is also similar to the /NOCOPY command, except it allows copies to occur, as long as the label is "scratch". Image(s) Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE - [SYSMSG]SYSMSG.EXE o Processes can hang (deadlock) when dismounting a device. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o If OpenVMS attempts to shrink the working set of a process whose working set contains only locked pages, an infinite loop at IPL 8 will induce system hangs or CPUSPINWAIT bugchecks. Image(s) Affected: -- COVER LETTER -- Page 9 25 August 1999 - [SYS$LDR]PAGE_MANAGEMENT.EXE - [SYS$LDR]WORKING_SET_MANAGEMENT.EXE o Names passed to the F11C/D ACP are rejected with an SS$_NOSUCHFILE error when passed to the processor. Image(s) Affected: - [SYSEXE]F11CACP.EXE - [SYSEXE]F11DACP.EXE o A 'no such file' error can occur on directory extension FCBs. This problem can occur in at least two ways: 1. A file appears normal on one node but has an 'no such file' error from another node. 2. BACKUP or DUMP /HEADER encounters a read attributes error of NOSUCHFILE. This error occurs when an attempt is made to read a file header, for which the FCB for the old header is still in memory. Image(s) Affected: - [SYSEXE]F11BXQP.EXE o %MOUNT-F-VOLALRMNT errors are received when MOUNTing multiple CDs privately. Image(s) Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o Alternate file access checking does not provide the correct information for files on ODS-1 disks. That is, an ODS-1 access does not process FIB$L_ALT_ACCESS and FIB$L_STATUS. Image(s) Affected: - [SYSEXE]F11AACP.EXE o The DISKQUOTA utility does not understand ODS-1 disks. Asking DISKQUOTA to show quota entries for an ODS-1 disk causes the code to permanently loop. -- COVER LETTER -- Page 10 25 August 1999 Image(s) Affected: - [SYSEXE]F11AACP.EXE o In a multi-processor environment, the service solicitation queues may be accessed by several processors. Thus, the solicit queue can get corrupted. Hence, the system can crash with an INVEXCEPTN at around LASTDRIVER+3513 in routine LAST$TICK. Image(s) Affected: - [SYS$LDR]ESS$LASTDRIVER.EXE o If a tape is initialized on a TZ87 and then put on a TZ86 with an attempt to re-initialize the tape, the TZ86 takes an excessive amount of time to determine how to handle the tape. Hence, it times out. Image(s) Affected: - [SYS$LDR]ESS$MADDRIVER.EXE o Heavy $GETQUI use can intermittently induce a nonfatal SSRVEXCEPT error at EXE$GETQUI_CONTEXT_FIND_C+00018. It could also intermittently induce a fatal DOUBLDEALO error at EXE$DEALLOCATE_C+00114. Image(s) Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE o A SSRVEXCEPT (ACCVIO) in SYS$TRANSACTION_SERVICES occurs when an Rdb recovery process is killed after it has been identified as stalling the system. Image(s) Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE o The system crashes in routine LT$XMT_RUN with an INCONSTATE error, upon having received an invalid LAT packet. While the Virtual Circuit is being shut down due to the invalid LAT packet, another session of the Virtual Circuit may continue to communicate. Due to the inconsistant state of the Virtual Circuit, a crash may occur. Image(s) Affected: -- COVER LETTER -- Page 11 25 August 1999 - [SYS$LDR]LTDRIVER.EXE o A fix to CONVERT was done to prevent SORT_ON and user mode Access Violations. As part of OpenVMS V7.2, the CONVERT utility was modified to eliminate a previous design constraint, in which the output file would temporarily become vulnerable to user access during the exchange of the file between CONVERT and the SORT32 utility. This problem would occur during the FAST load processing of the secondary keys of the file. (For more details see Section 3.21 of the OpenVMS V7.2 New Features manual.) As part of this modification, some changes were added to read records from the newly created output file, while processing alternate keys. In the case of an indexed file with fixed-length records, it turns out that the logic, for determining if both key and record compression were disabled for the primary key, was flawed. Hence, this problem can lead to a record length being incorrectly calculated. It can result in the overwriting of internal structures contiguous to a temporary convert buffer and cause various errors, ranging from sort errors (SORT_ON) to user-mode access violations. In order for this problem to occur, the indexed file must have ALL three of the following characteristics: o FIXED length record format o More than two keys o Primary key must have either key or record compression (or both) enabled Image(s) Affected: - [SYSLIB]CONVSHR.EXE o Occasional false end-of-file (EOF) errors can occur on a read operation. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o The XQP fails after an IO$_DEACCESS call with an SS$_BADPARAM error. One cannot determine whether a file is still open or not, due to the failed IO$_DEACCESS call. -- COVER LETTER -- Page 12 25 August 1999 Image Affected: - [SYSEXE]F11BXQP.EXE o Non-privileged users can change the revision date (and count) of a file for which they should have only READ access. For example, if a non-privileged user with READ-only file access tries to set the file protection, a failure occurs with an SS$_NOPRIV error as expected. However, the revision date (and count) are modified. Image Affected: - [SYSEXE]F11BXQP.EXE o In a multi-processor environment, the solicitation state of a queued solicitation may change due to a cancel. When a periodic status is requested on the queued solicit item, then the system can crash with an INVEXCEPTN. Image(s) Affected: - [SYS$LDR]LTDRIVER.EXE o 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 o Heavy use of $GETQUI could result in a fatal SSRVEXCEPT bugcheck if the context queue is modified while it is being scanned. Image(s) Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE o OpenVMS V7.2 provides a new check to determine if the disk that is being MOUNTed is initialized to a size that is larger than the number of blocks that are now available. -- COVER LETTER -- Page 13 25 August 1999 This size discrepancy occurs when a disk is moved from one controller type to another (eg. from a local SCSI connection to an HSJ), without the disk being initialized on the new controller. As a result, some data may be inaccessible through the new controller. If this condition is detected, then a fatal MOUNT-F-FILESTRUCT error is reported and the MOUNT is aborted. It has been determined that a number of customers are running with disks which are in this condition. While data may be inaccessible on the disk, the usefulness of the disk should be left to the discretion of the System Manager. Therefore, this change makes this condition issue a warning message: %MOUNT-W-INCONSIZE, inconsistent number of blocks reported, some data may not be accessible rather than a fatal error. It is recommended that the BACKUP utility be used to move data from a disk on one controller type to a disk on another controller type, especially if those controllers report a different number of blocks available for the same disk type. Once the data has been moved, the physical disk can be moved and initialized on the new controller. Image(s) Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE - [SYSMSG]SYSMSG.EXE o Massive non-paged pool corruption leads to various crashes and hangs. Another defining characteristic of this problem is pool exhaustion accompanied by an "insufficient Dynamic Memory" return status. Image(s) Affected: - [SYS$LDR]SYS$IPC_SERVICES.EXE o Extra long HW_NAMEs get truncated by the 31-byte buffer SHOW LICENSE/CHARGE. Image(s) Affected: - [SYSEXE]SHOW.EXE o The POLYCENTER Software Installation (PCSI) utility has a database corruption problem. -- COVER LETTER -- Page 14 25 August 1999 This problem occurs for three patch kits that ship the same image and then are installed out of order. For example: A full kit is installed and then an image (eg. AUTHORIZE.EXE) has a generation of 10000. Patch kit AUTHORIZE....version 1 is installed AUTHORIZE.EXE has a generation of 10001 Next, patch kit AUTHORIZE....version 3 is installed AUTHORIZE.EXE has a generation of 10003 Finally, patch kit AUTHORIZE....version 2 is installed AUTHORIZE.EXE has a generation of 10002 At the point patch version 2 is installed, the database for this image (AUTHORIZE.EXE) is corrupted and any attempt to update it will result in an ACCVIO. If the patch kits are installed in order, no problem occurs. The problem may also occur with full kits that share images between the kits. Image(s) Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE o The /SELECT qualifier for the PRODCUT LIST and the PRODUCT EXTRACT FILE FILE commands is documented to accept a list of filespecs. However, if a list is used, a DCL error is returned. An example is: $ PRODUCT EXTRACT FILE MMOV /SELECT=(*.TXT,*.HLP) /DESTINATION=[] %DCL-W-ONEVAL, list of values not allowed - check use of comma (,) \*.HLP)\ Image(s) Affected: - [SYSEXE]PCSI$MAIN.EXE - [SYSLIB]PCSI$SHR.EXE - [SYSUPD]PCSI.CLD o Changing the security profile of a cluster wide logical name table causes other nodes in the system to crash. For example, the problem can occur when the user types the DCL command: -- COVER LETTER -- Page 15 25 August 1999 SET SECURITY/CLA=LOGICAL Image(s) Affected: - [SYS$LDR]LOGICAL_NAMES.EXE - [SYS$LDR]SECURITY.EXE - [SYSEXE]SECURITY_MON.EXE - [SYSEXE]CSP.EXE o A crash with an NETNOSTATE error occurs due to a malformed username. Data is sent to DECnet in this form by the system requesting a connect. Image(s) Affected: - [SYSEXE]NETACP.EXE o Access to a corrupted directory could result in the user's process being deleted from the system through an EXEC mode exception. Note that a system bugcheck would occur if the SYSGEN parameter BUGCHECKFATAL were set. Image(s) Affected: - [SYS$LDR]RMS.EXE o Five different debugger problems can occur: 1. After an upgrade to Motif V1.2-5, the source view can "jiggle" horizontally on every source scroll change. 2. GUI STOP and SMG ^C can sometimes fail, so that the user does NOT get control. 3. DBG> SET MODULE large-ada-module can result in an %DEBUG-F-DSTNESDEP, DST nesting depth too deep in module error message. 4. The SHOW THREAD or SHOW CALL (of a thread stack) command can sometimes ACCVIO, especially if the thread has terminated. 5. Printing out "in %TASK 1" on event triggers occur, e.g. "break at" instead of the old behavior, where task 1 is silent/assumed (Ada). -- COVER LETTER -- Page 16 25 August 1999 Image(s) Affected: - [SYSLIB]DEBUG.EXE - [SYSLIB]DEBUGSHR.EXE - [SYSLIB]VMSDEBUGUIL.UID o Every five minutes, the following line shows up in the OPERATOR.LOG: OPCOM on NODE_A is trying again to talk to NODE_B, csid ########, system ##### An OPCOM process on one node could not communicate with an OPCOM process on another node. Image(s) Affected: - [SYSEXE]OPCOM.EXE o If a process attempts to mount a Bound Volume Set (BVS) and all the members of the BVS are not present, an attempt to lock the volume for REBUILDing the meta-data on the volume fails. However, the blocking lock (F11B$b) is left with the process. Image(s) Affected: - [SYS$LDR]F11BXQP.EXE o The CONVERT utility fails to create a temporary work file (CONVWORK) when the following conditions exist: 1. RMS indexed file is being created with more than two keys, and 2. sort of the primary key is not being performed, and 3. total size of the alternate keys (keys 2-7) represents a small percentage of the full record length, and 4. input file is relatively small, and 5. /SECONDARY qualifier is used to specify a value greater than the default value of 1 The effect of these conditions is that the calculated size of the work file is determined to be less than 1 block. When this size is passed to the file creation routine, the following fatal error is reported: "%CONVERT-F-CREA_ERR, error creating work file" DISK:[DIRECTORY]CONVWORK.TMP;1" -- COVER LETTER -- Page 17 25 August 1999 "-RMS-F-ALQ, invalid allocation quantity (negative, or 0 on $EXTEND)" Image(s) Affected: - [SYSLIB]CONVSHR.EXE o The modified (revised) date is not updated when the file object attributes are reset to the default with the following command: $ SET SECURITY filex.xxx /DEFAULT Testing of the original fix on ODS-2 files was successful. However, testing with ODS-5 uncovered another defect that caused errors when long (or UCS2) filenames were used: %SET-F-WRITEERR, error writing $14$DKA100:[junk^_ods5_big]ods5^_noname^_very.txt;1 -SYSTEM-W-BADFILENAME, bad file name syntax Image(s) Affected: - [SYSEXE]SETSHOSECUR.EXE o Starting with OpenVMS VAX V7.0, if a user attempts to forward a foreign file, the forward would fail and the user is returned to the MAIL> prompt. No message of any kind is displayed. Image(s) Affected: - [SYSEXE]MAIL.EXE o On a system with valid, configured Volume Shadowing Licenses installed/loaded (VOLSHD capacity license on one node with a target two-node VOLSHAD-DISK cluster), the cluster can still display License warning messages about Volume-shadowing. A sample error message is as follows: %LICENSE-E-NOAUTH, DEC VOLSHAD use is not authorized on this node %%%%%%%%%%% OPCOM 9-DEC-1998 19:48:30.68 %%%%%%%%%%% Message from user SYSTEM on I2INGR %LICENSE-E-NOAUTH, DEC VOLSHAD use is not authorized on this node -LICENSE-F-NOLICENSE, no license is active for this software product -- COVER LETTER -- Page 18 25 August 1999 -LICENSE-I-SYSMGR, please see your system manager Image(s) Affected: - [SYS$STARTUP]LICENSE_CHECK.EXE o If a member of a shadow set is removed from the set for BACKUPs, then both the still mounted shadow set and the privately mounted former member will have the same VCB$T_VOLOCKNAMs. This problem causes a variety of symptoms, including access conflicts during BACKUPs of the former member and possibly the error message: XQPERR, Error detected by file system XQP In addition, a case for which a user is unable to MOUNT multiple CDROMs privately is also attributable to this problem. Note: An unresolved problem is that if a disk is write-locked, it will not successfully complete mount verification. Consequently, the device will be marked as "wrong volume". Image(s) Affected: - [SYSLIB]MOUNTSHR.EXE o An ACCVIO can occur due to double deallocation of the system default transaction data structure (XDCB) XDCB. The specific error is SSRVEXCEPT in module SYS$TRANSACTION_SERVICES. For example, if a user stops an ACMS application ($ ACMS /STOP APPL xxxx), then the application that uses RDB causes recovery processes to run against the database. One of the ACMS servers, that is attached to the database, hangs and holds a lock that prevents the execution of the recovery processes. The user stops this server using AMDS and then the system crashes. Image(s) Affected: - [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE o An XQP system crash occurs in XQP IO after a datacheck error occurs (SS$_DATACHECK) during a Shadowset copy operation. Image(s) Affected: - [SYS$LDR]SHDRIVER.EXE -- COVER LETTER -- Page 19 25 August 1999 o When using the MIME NEW command, the process can report a DCL error and then hang. Other related problems are: 1. EditPart() needs to prepend "EDIT/" to the edit command buffer for NEW command to avoid error %DCL-W-IVVERB, unrecognized command verb 2. %MIME-E-OPNFILERR problem in main() such that lib$find_file resultantFileSpec was space character padded 3. Space needed for MIME> prompt, i.e. ' promptDesc ' 4. Status handling for CLI$_ABSENT in ParseFileNameList() 5. Incorrect dynamic memory freeing using current pointer continuously in MIME.C FreeMsgDir() 6. Automatic LIST needed for OPEN command 7. Double error message printout Image(s) Affected: - [SYSEXE]MIME.EXE o Applications based upon the BACKUP API may experience various failures when BACKUP is updated from V7.1 to later versions. An obsolete references to STRUCTURE (keyword/qualifier) was also removed. Image(s) Affected: - None o Although the documentation states that a process joins the system and default group resource domains when created, the process could only join the system domain. The first $ENQ results in the process joining the default group domain. If, however, a process begins to issue $GETLKI system services, without having issued an $ENQ prior to the $GETLKI calls, the process will get back SS$_ILLRSDM errors. The $GETLKI system service was changed to join the default group resource domain, if the process has not yet done so. In addition, if a process is able to do a $GETLKI operation on a lock due to having WORLD privilege, READ access will be allowed on the value block and the SS$_ILLRSDM error will not be returned. -- COVER LETTER -- Page 20 25 August 1999 Image(s) Affected: - [SYS$LDR]LOCKING.EXE o Heavy use of $GETQUI can result in a fatal SSRVEXCEPT bugcheck. Image(s) Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE o A LANCP SHOW DEVICE/COUNTER command can return a %LANCP-E-ABORT error for LAN adapters that maintain hardware counters. Image(s) Affected: - [SYS$LDR]ECDRIVER.EXE - [SYS$LDR]EFDRIVER.EXE - [SYS$LDR]EPDRIVER.EXE - [SYS$LDR]EPJDRIVER.EXE - [SYS$LDR]ESDRIVER.EXE - [SYS$LDR]ETDRIVER.EXE - [SYS$LDR]EXDRIVER.EXE - [SYS$LDR]EZDRIVER.EXE - [SYS$LDR]FCDRIVER.EXE - [SYS$LDR]FQDRIVER.EXE - [SYS$LDR]FXDRIVER.EXE - [SYS$LDR]XEDRIVER.EXE - [SYS$LDR]XQDRIVER.EXE 6 PROBLEMS ADDRESSED IN VAXDRIV01_072 KIT o When initializing a FIBRECHANNEL (DG) device from a client, one of the two following errors is returned to the user (disk only, not tape): 1. INIT-F_DIAGPACK, disk is a diagnostic pack OR -- COVER LETTER -- Page 21 25 August 1999 2. INIT-W-NOBADDATA, bad block data not found on volume Note that an INIT of the same devices succeed on the server. Image(s) affected: - [SYS$LDR]SYS$DUDRIVER.EXE 7 PROBLEMS ADDRESSED IN VAXPTHR01_072 KIT o ADA compiles are erroneously returning 'success' after OpenVMS VAX V7.2 is installed. ACS RECOMPILE returns an incorrect status and allows command files to continue on from what should be a fatal error. 8 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. 9 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 VAXUPDATE01_072 [location of the saveset] The saveset location may be a tape drive, CD, 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 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. -- COVER LETTER -- Page 22 25 August 1999 Copyright (c) Compaq Computer Corporation, 1999 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.