OpenVMS VAXUPDATE01_072 OpenVMS VAX V7.2 ECO Summary
TITLE: OpenVMS VAXUPDATE01_072 OpenVMS VAX V7.2 ECO Summary
Modification Date: 08-OCT-1999
Modification Type: Corrected image information in Table of Kit
Information
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 1999. All rights reserved.
OP/SYS: OpenVMS VAX
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXUPDATE01_072
ECO Kits Superseded by This ECO Kit: VAXDRIV01_072, VAXPTHR01_072
ECO Kit Approximate Size: 14508 Blocks
Saveset A - 14508 Blocks
Kit Applies To: OpenVMS VAX V7.2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: 1 - To be installed on all systems running
the listed version(s) of OpenVMS.
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:
None
ECO KIT SUMMARY:
An ECO kit exists for OpenVMS VAX V7.2. This kit addresses the following
problems:
PROBLEMS ADDRESSED IN VAXUPDATE01_072 KIT
o TZ87 MOUNT hangs after power cycle
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 Fatal Volume Not Valid error - install during backup using
Infoserver
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 RMSBUG crash when SHADOWING returns zero IOSB
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 LATCP> SHOW LINK/COUNTER display problem
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
o UNXSIGNAL/ACCVIO crash during dismount
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 XQPERR bugcheck at F11BXQP when buffers not written out
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 UNXSIGNAL/ACCVIO crash during MOUNT
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
Work-arounds:
For BVS, one should not attempt to concurrently mount many
volumes in subprocesses. Hence, do not use "spawn" process
for mounting disks of BVS. Instead, use the command serially.
i.e. asynchronous MOUNTS of BVS members.
o Capacity > 8.6GB for disks not allowed
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 Incorrect MAIL$INTERNET_TRANSPORT usage
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.
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 CDROMs with long labels
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 LANCP> SHOW DEVICE/COUNTER display error
A LANCP SHOW DEVICE/COUNTER command incorrectly shows sends
and receives failure counts.
Image(s) Affected:
- [SYSEXE]LANCP.EXE
o System does not configure local DSSI disks
A system with a KFQSA adapter does not configure local DSSI
disks.
Image(s) Affected:
- [SYS$LDR]PUDRIVER.EXE
o IPC system service not supporting EFN$C_ENF
The IPC system service does not support the special event flag
EFN$C_ENF.
Image(s) Affected:
- [SYS$LDR]SYS$IPC_SERVICES.EXE
o VBNMAPFAIL/OUTSWPERR bugcheck
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.
Image(s) Affected:
- [SYSEXE]SYSGEN.EXE
- [SYSEXE]SYSINIT.EXE
o MSCPCLASS fatal error detected by MSCP class driver
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
Incomplete SDA displays for DSA devices occur.
Image(s) Affected:
- [SYSEXE]SDA.EXE
o SHADDETINCON crashes after Shadowset members removed
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 SHADDETINCON crashes in SHLK$MERGE_SIGNAL
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 DECnet translation failure with IPC-E-BCKTRNSFAIL error
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:
- [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE
o Add /POLICY=(REQUIRE_MEMBERS,VERIFY_LABELS) to MOUNT
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 hang when dismounting a device
Processes can hang (deadlock) when dismounting a device.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
o System hang or CPUSPINWAIT bugchecks
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:
- [SYS$LDR]PAGE_MANAGEMENT.EXE
- [SYS$LDR]WORKING_SET_MANAGEMENT.EXE
6o ACP rejects lower case file names
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 "No such file" error on directory extension FCBs
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 VOLALRMNT errors when mounting multiple CDs
%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 on ODS-1 disks
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 ACPCONTROL not returning ILLIOFUNC for illegal functions
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.
Image(s) Affected:
- [SYSEXE]F11AACP.EXE
o Service solicitation queues being accessed by several
processors
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 Re-initialize of TZ86 tape times out
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 $GETQUI induced nonfatal SSRVEXCEPT or fatal DOUBLDEALO error
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 ACCVIO when rundown handler runs twice
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 System crashes in routine LT$XMT_RUN
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:
- [SYS$LDR]LTDRIVER.EXE
o SORT_ON and user mode Access Violations
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 False EOF errors on read operation
Occasional false end-of-file (EOF) errors can occur on a read
operation.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
o XQP failure with SS$_BADPARAM error
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.
Image Affected:
- [SYSEXE]F11BXQP.EXE
o Non-privileged users can revise file
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 Crash for queued solicit item
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
The INVEXCEPTN crash can occur in the LT$CRASH routine (module
LTDRIVER_SOLICIT) if the periodic timeout event is delared
when SSB$B_SOL_STATE = 0.
Also, if a periodic status is requested on a queued solicit
item, then before declaring a timeout event, a check to see if
SSB$B_SOL_STATE is NOT equal to zero must be made. Otherwise,
if a timeout event is declared with SSB$B_SOL_STATE=0, then
the system will crash. This event is illegal in a ZERO
solicit state.
Note:
In a muli-processor environment, SSB$B_SOL_STATE may be
cleared by a cancel, etc.
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
o $GETQUI - fatal SSRVEXCEPT if context queue modified while
being scanned
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 Demote FILESTRUCT error to a warning for size violation
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.
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 leading to crashes and
hangs
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
Work-arounds:
Clearing the item code prevents moving of data, when no
DISCONNECT data exists.
o Extra long HW_NAMEs get truncated
Extra long HW_NAMEs get truncated by the 31-byte buffer SHOW
LICENSE/CHARGE.
Image(s) Affected:
- [SYSEXE]SHOW.EXE
o POLYCENTER Software Installation utility database corruption
The POLYCENTER Software Installation (PCSI) utility has a
database corruption problem.
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 PCSI utility: PRODUCT LIST/SELECT, PRODUCT EXTRACT/SELECT
failure
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 security profile causes other nodes to crash
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:
SET SECURITY/CLA=LOGICAL
Image(s) Affected:
- [SYS$LDR]LOGICAL_NAMES.EXE
- [SYS$LDR]SECURITY.EXE
- [SYSEXE]SECURITY_MON.EXE
- [SYSEXE]CSP.EXE
o Crash with NETNOSTATE error due to malformed username
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 corrupted directory results in process deletion
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 Debugger fixes
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).
Image(s) Affected:
- [SYSLIB]DEBUG.EXE
- [SYSLIB]DEBUGSHR.EXE
- [SYSLIB]VMSDEBUGUIL.UID
For the five problems:
1. The line number column appears to be resized on every
source view change, first to maximum width and then its
actual width.
The line number column XmNresizeWidth was changed to
false. Note that this change does NOT inhibit a column
width change when the number of actual line number digits
change!
2. DBG$SEARCH_GLOBAL saves and then clears the
DBG$V_CONTROL_STOP bit and intends to restore it before
returning.
However, DBG$SEARCH_GLOBAL fails to restore
DBG$V_CONTROL_STOP for one of its return paths. (The
problem was introduced in March 1998 with some GST
performance improvement work.)
3. The Ada module compiles into a DST, with a very deeply
scoped DST.
Currently, SET MODULE can only handle scopes nested 100
levels. The solution was to increase the maximum nested
level to 200.
4. STACK_INFO/process_next_frame returns DBG$_UNASETTAS
status as an address of a virtual frame.
However, STACK_INFO should return bad status, i.e. 0, if
it cannot find a frame. Also, its callers (most already
do) should check this status and handle it appropriately.
This problem especially affects DBG_SERVER's callstack
code. SET THREAD/VISIBLE should return to the last
visible thread if the new thread cannot be setup, e.g. no
top level registers are available.
5. The last round of PTHREAD debugger caused the printing out
"in %TASK 1" (regression).
The solution was to have PRINT_TASK_NUMBER take into
account the language setting. If Ada, print "in %TASK"
only if it is NOT for %TASK 1. Also, make a change to
print "in THREAD" for non-ADA language settings.
o OPCOM processes unable to communicate between nodes
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 BVS - stray lock left on LOCK_VOLUME
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 CONVERT utility fails to create temporary work file
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"
"-RMS-F-ALQ, invalid allocation quantity
(negative, or 0 on $EXTEND)"
Image(s) Affected:
- [SYSLIB]CONVSHR.EXE
o Modified date not updated when file object attributes
reset to default
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
The SETSECUR.B32 PROCESS_FILE routine handles the
/DEFAULT qualifier in a unique fashion. It does its own
$QIO instead of calling $SET_SECURITY, as it does for
other qualifiers. This situation led to two problems:
1. The 'attribute control block' ($QIO P5 parameter),
normally contains information of what should be
modified when you CREATE, DEACCESS, or MODIFY a file.
This ATR block was missing.
2. For OpenVMS VAX V7.2 and up, the FIB extended name
fields were filled in prior to the $QIO call, but
they were then cleared prior to initializing other
FIB attributes. This problem caused improper
handling of ODS-5 (long/or UCS2) files.
o Restore forwarding of foreign files
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 Volume-shadowing "customer is not licensed" error
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
-LICENSE-I-SYSMGR, please see your system manager
Image(s) Affected:
- [SYS$STARTUP]LICENSE_CHECK.EXE
o Access conflicts during BACKUPs of member of a shadow
set
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 ACCVIO due to double deallocation of system XDCB
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 Datacheck to XQP IO after Shadowset copy results in XQP
crash
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
o Hang for MIME NEW command; related fixes
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
The original problem was due to the way in which the edit
command buffer was constructed. Also, EDT (TPU, and
TECO) are not command verbs, but qualifiers to the EDIT
command.
The other fixes are:
1. Added check for editor type; append ' edtCmd '
accordingly
2. %MIME-E-OPNFILERR ASCIZ terminates lib$find_file
resultantFileSpec, that was space character padded
3. Added space to MIME> prompt - ' promptDesc '
4. Added status handling for CLI$_ABSENT in
ParseFileNameList()
5. Changed freeing ' item ' to free( thisItem )
6. Added automatic LIST to OPEN command
7. Fixed double error message printout by 'oring'
STS$M_INHIB_MSG in MAIN() exit status
o Bugfix BACKUP API compatibility with prior versions
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
Work-arounds:
Re-compile all backup-related applications using the new
definitions.
o Process did not join default group resource domain
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.
Image(s) Affected:
- [SYS$LDR]LOCKING.EXE
o Heavy use of $GETQUI results in SSRVEXCEPT
Heavy use of $GETQUI can result in a fatal SSRVEXCEPT
bugcheck.
Image(s) Affected:
- [SYS$LDR]MESSAGE_ROUTINES.EXE
GETQUI_CONTEXT_NEW was executing in EXEC mode and was:
1. allocating some pool for a new context block, and
2. placing it on the context queue, and
3. initializing the context block once it was in the
queue
If an AST routine interrupts after 2), and scans the
context blocks in the queue, and then deallocates the new
context block before GETQUI_CONTEXT_NEW finished the
operation, then the context block could be initialized
*after* it was on the parameter P1 space freelist (or
already reused by someone else).
Often the EXEC stack will show a return PC to
GETQUI_CONTEXT_NEW (in MESSAGE_ROUTINES) in the resulting
crash dump.
For a solution, switch the order that the task is done.
As other code is inserting the context block into the
context queue do the following:
1. allocate some pool for a new context block, and
2. initialize the context, and
3. place it on the context queue
Hence, the block cannot be found and deallocated by an
AST until it has been initialized. If an AST does occur
between 2) and 3), it will not find the context block to
deallocate.
o LANCP SHOW DEVICE/COUNTER returns %LANCP-E-ABORT for LAN
adapter
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
PROBLEMS ADDRESSED IN VAXDRIV01_072 KIT
o hl 2 FIBRECHANNEL Initialization
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
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
PROBLEMS ADDRESSED IN VAXPTHR01_072 KIT
o ADA compiles erroneously returning 'success'
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.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxupdate01_072.README
vaxupdate01_072.CHKSUM
vaxupdate01_072.CVRLET_TXT
vaxupdate01_072.a-dcx_vaxexe
vaxupdate01_072.CVRLET_TXT
|
