OpenVMS VMS712_UPDATE-V0300 Alpha V7.1-2 Fixes _ Hardware Support ECO Summary
TITLE: OpenVMS VMS712_UPDATE-V0300 Alpha V7.1-2 Fixes _ Hardware Support ECO Summary
Modification Date: 23-JAN-2001
Modification Type: Placed correct kit on ftp site.
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-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 1998, 1999. All rights reserved.
PRODUCT: OpenVMS Alpha
COMPONENTS: New Images:
APB BACKUP BACKUPSHR
DCL DEBUG DEBUGUISHR
DEBUG_APB DEC$BASRTL DECW$ICBM
DECW$SERVER_DDX_GY DECW$SERVER_DDX_GZ DECW$SERVER_DDX_WMB_GY
DECW$SERVER_DIX ERRFMT ESS$LADCP
EXCEPTION EXEC_INIT F11BXQP
IO_ROUTINES IO_ROUTINES_MON LANACP
LANCP LATACP LIBRTL
LIBRTL_INSTRUMENTED LICENSE_CHECK LOCKING
MAIL MAILSHR MESSAGE_ROUTINES
MONITOR_TV.EXE MONTORSHR MOUNTSHR
OPCOM PCSI$MAIN PCSI$SHR
PPLRTL PROCESS_MANAGEMENT PROCESS_MANAGEMENT_MON
RMS SDA$SHARE SECURITY
SETSHOSECUR SHOW SORTSHR
SPISHR SVRSYSTEM_MIB SYS$BASE_IMAGE
SYS$CLUSTER SYS$CPU_ROUTINES_0C05
SYS$CPU_ROUTINES_0C08 SYS$CPU_ROUTINES_0F05
SYS$CPU_ROUTINES_1102 SYS$CPU_ROUTINES_1105
SYS$CPU_ROUTINES_1605 SYS$CPU_ROUTINES_1A05
SYS$CPU_ROUTINES_1B02 SYS$CPU_ROUTINES_1B05
SYS$CPU_ROUTINES_2005 SYS$CPU_ROUTINES_2208
SYS$DKDRIVER SYS$DQDRIVER SYS$DRDRIVER
SYS$DUDRIVER SYS$EIBTDRIVER SYS$EIDRIVER
SYS$ERDRIVER SYS$EW1000A SYS$EWBTDRIVER
SYS$EWDRIVER SYS$EWDRIVER_DE500BA
SYS$FTDRIVER SYS$FWBTDRIVER SYS$FXDRIVER
SYS$GYCDRIVER SYS$GZDRIVER SYS$GZVDRIVER
SYS$ICBM SYS$IIDRIVER SYS$IKBDRIVER
SYS$INDRIVER SYS$LAN SYS$LAN_ATM
SYS$LAN_CSMACD SYS$LAN_FDDI SYS$LAN_TR
SYS$LASTDRIVER SYS$LTDRIVER SYS$MADDRIVER
SYS$MCDRIVER SYS$MKDRIVER SYS$PIDRIVER
SYS$PJDRIVER SYS$PKEDRIVER SYS$PKQDRIVER
SYS$PKSDRIVER SYS$PKTDRIVER SYS$PKWDRIVER
SYS$SCS SYS$SHDRIVER SYS$SMDRIVER
SYS$SMHANDLER SYS$TRANSACTION_SERVICES
SYS$TUDRIVER SYS$VCC SYS$VCC_MON
SYS$VM SYSGEN SYSGETSYI
SYSINIT SYSMSG SYSTEM_PRIMITIVES
SYSTEM_PRIMITIVES_MIN TRACE
VMOUNT VPM VPM_SERVER
COMPONENTS: New Files:
EXCEPTION.STB EXEC_INIT.STB F11BXQP.STD
IO_ROUTINES.STB IO_ROUTINES_MON.STB LIBRTL.STB
LOCKING.STB MESSAGE_ROUTINES.STB
PROCESS_MANAGEMENT.STB PROCESS_MANAGEMENT_MON.STB
RMS.STB SECURITY.STB SYSGETSYI.STB
SYSTEM_PRIMITIVES.STB SYSTEM_PRIMITIVES_MIN.STB
SYS$VM.STB CLUSTER_CONFIG.COM DECDTM$STARTUP.COM
DECW$DEVICE_CONFIG_GY.COM DECW$DEVICE_CONFIG_GZ.COM
SYS$LIB_C.TLB VMSDEBUGUIL.UID STARLET.MLB
STARLET.REQ STARLET.R64 LIBRTL.IIF
SYS$CONFIG.DAT BACKUP.CLD MOUNT.CLD
PCSI.CLD
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS712_UPDATE-V0300
DEC-AXPVMS-VMS712_UPDATE-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS712_UPDATE02-V0100
VMS712_UPDATE01-V0100
VMS712_HARDWARE-V0100
VMS712_GRAPHICS-V0100
VMS712_DRIVER-V0100
VMS712_MOUNT96-V0100
VMS712_SCSI-V0100
NOTE regarding Superseded Kit Documentation:
Documentation for the superseded VMS712_UPDATE02-V0100
kit is included in a separate file called
VMS712_UPDATE02-V0100_CVRLET.TXT. This file can be found
in the [SYSHLP] directory and is also included in the kit.
It can be extracted from the kit via the DCL command:
$ PROD EXT FILE VMS712_UPDATE_FT2/-
select=VMS712_UPDATE-V0200_CVRLET.TXT
ECO Kit Approximate Size: 67,024 Blocks
Kit Applies To: OpenVMS Alpha V7.1-2
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) 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
NOTE: This kit and the VMS62TO71U2_PCSI-V0200 kit both contain PCSI
executable files and it appears as though this kit is superseded
by the files in the PCSI kit. Either of the kits can be
installed first because PCSI will do the right thing and
keep/install the latest executable.
ECO KIT SUMMARY:
An ECO kit exists for OpenVMS Alpha V7.1-2. This kit addresses the
following problems:
New Functionality Included in the VMS712_UPDATE-V0300 Kit:
o The current family of Fast Ethernet PCI adapters (DE500) have
reached their end of life. Compaq's Family of Fast Ethernet
adapters based on Intel's 82558 controller have been selected
as replacements for the DE500 family. These adapters include:
- NC3121 single port 100BaseTX adapter.
- NC3131 dual port 100BaseTX adapter.
- NC3132 dual port 100BaseTX daughter card for the NC3131.
- NC3133 single port 100BaseFX daughter card for the NC3131.
This functionality is only used if you are using Compaq's
Intel 82558 Fast Ethernet PCI adapter.
Image(s) Affected:
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIBTDRIVER.EXE
- [SYSEXE]APB.EXE
- [SYSEXE]DEBUG_APB.EXE
o This kit provides support for the Compaq PowerStorm 4D10T
(ELSA Gloria) graphics option.
After installation, graphics operation of the 4D10T option
will automatically start graphics after system boot.
The default graphics settings are 1024x768 @70Hz with 8-bit
pixels.
Additional resolutions are available, depending on the monitor
and environment:
640 x 480 8/24-bit 60, 65, 70, 75, and 85Hz
800 x 600 8/24-bit 60, 65, 70, 75, and 85Hz
1024 x 768 8/24-bit 60, 65, 70, 75, and 85Hz
1152 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1280 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1600 x 1200 8-bit only 60, 65, 70, 75Hz
1600 x 1280 8-bit only 60, 65, 70Hz
1920 x 1200 8-bit only 60, 65, 70Hz
These settings are changed by renaming:
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
to
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
and following the directions in the file (for example):
$ define/exec/system/nolog decw$server_refresh_rate 75
$ define/exec/system/nolog decw$server_pixel_depth 24
$ decw$xsize_in_pixels == 1280
$ decw$ysize_in_pixels == 1024
Note that Compaq recommends that the refresh rate be 70Hz or
above to avoid screen flicker with room lighting. In
addition, the monitor determines the highest settings. For
instance, many monitors will not support greater than
1280x1024, or may only support that resolution at lower (60Hz)
refresh rates.
For multiple heads, there can be separate values for each
monitor:
$ define/exec/system/nolog decw$server_refresh_rate 75, 60, 70
$ define/exec/system/nolog decw$server_pixel_depth 24, 8, 8
$ decw$xsize_in_pixels == "1280, 640, 1600"
$ decw$ysize_in_pixels == "1024, 480, 1280"
The 4D10T has been tested with up to 7 heads. Only 4D10T
cards should be used together. Combinations with non-4D10T
cards have not been tested, and may not work.
This functionality is only used if you are using a Compaq
PowerStorm 4D10T graphics option.
Image(s) Affected:
- [SYS$LDR]SYS$GZDRIVER.EXE
- [SYSLIB]DECW$SERVER_DDX_GZ.EXE
- [SYSLIB]DECW$SERVER_DIX.EXE
- [SYSLIB]DECW$SERVER_DDX_CFB16.EXE
o This change adds P2V chip support to the P2A code used on
ELSA.
This functionality is only used if you are using a P2V
graphics adaptor
Image(s) Affected:
- [SYS$LDR]SYS$GZVDRIVER.EXE
- [SYSEXE]SYS$CONFIG.DAT
Problems Addressed in VMS712_UPDATE-V0300 Rated as Installation 1:
o The system would crash with a PFIPLHI within the SECURITY
execlet.
Image(s) Affected:
- [SYS$LDR]SECURITY.EXE
o When two processes are accessing a file via the MOVEFILE and
READATTR/FID_TO_SPEC mechanism, such as a data collector
process running on the same volume as a defragger competing
for the same data, both processes try to delete the
'primary_fcb' used to get the information in question. In
both of these circumstances, the reference count on the FCB
has not been bumped up so both accesses appear to allow the
deletion. This results in a NOTFCBFCB Bugcheck.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
o An XQPERR Bugcheck occurs in LOCKERS when the retry limit on
F11B$x lock is reached. This happens when the owner of the $x
lock is running at a high process priority and there are a
number of processes in a clustered system that are also trying
to validate this lock but at a lower process priority. The
high priority process never really gives up the locks long
enough to let the low process priority processes continue
and either validate or release the $x lock.
To avoid this situation, after (every) 256 attempts, the
process with the most retry iterations is stalled for a short
period to allow other processes to complete their accesses to
the lock.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
NOTE: The documentation states that the following problem is
fixed in this ECO. That is incorrect. This problem
is not seen in the V7.1-2 release nor in any subsequent
remedial kit for V7.1-2.
o In the process of finding an FCB chain, the XQP switches
serialization to the primary FCB of the chain. In this
process, the FCB chain an be rebuilt or destroyed while the
process is stalled. If this FCB now points to another FCB
chain or a deleted FCB the XQP will bugcheck with either an
XQPERR bugcheck or a UNXSIGNAL (ACCVIO).
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
o Occasional INVEXCEPTN and MSCPCLASS bugchecks due to zero CDT
in CDDB.
Image(s) Affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o During a port crash, failover event or other problem, the same
CDT address may be reused for the new connection.
When a connection fails, the UCB$L_CDT field is not updated.
There exists a small window where the failed DUDRIVER CDT is
reused for another connection and an I/O will attempt to start
because the UCB$L_CDT still points to a valid, open CDT. This
can cause an INCONSTATE bugcheck.
Image(s) Affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o There is a potential for improper mount verification, during
mount verification of MSCP served disks.
Image(s) Affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o System crashes with a machine check due to a non-existent PCI
Address.
Image(s) Affected:
- [SYS$LDR]SYS$PKEDRIVER.EXE
- [SYS$LDR]SYS$PKTDRIVER.EXE
o The following corruption is a LAN packet which causes an Alpha
system to crash with "INVEXCEPTN, Exception while above
ASTDEL". The PC related to the crash is:
SYS$LAN_CSMACD_NPRO+05F80: LDL R26,#X0238(R5)
The corrupted packet looks like this:
AAAAE001 A1B50D65 0000FFFF FFFFFFFF ...e.µ¡.પ FFFFFFFF.80EF3500
|ctr|len||src address||dst address|
FFFFE001 00291147 6000FFFF FFFF0003 ..`G.)..à.. FFFFFFFF.80EF3510
| |ctrl|
|----------|<---- This being the corrupted 802E PID field
Images(s) Affected:
- [SYS$LDR]SYS$LAN.EXE
- [SYS$LDR]SYS$LAN_TR.EXE
- [SYS$LDR]SYS$LAN_FDDI.EXE
- [SYS$LDR]SYS$LAN_CSMACD.EXE
- [SYS$LDR]SYS$LAN_ATM.EXE
o A change was made to fix a problem where SWL disks do not come
out of mount verification properly. The fix insured that the
VCB$T_VOLOCKNAM matches the SCB$_VOLOCKNAME of the volume, even
for privately mounted disks. However, 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 causes a variety of symptoms, including access conflicts
during BACKUPs of the former member and in at least 1 case, an
XQPERR, Error detected by file system XQP bugcheck at
F11BXQP_PRO+0BE48.
In addition, reports of customers unable to MOUNT multiple
CDroms privately is also attributable to the original change.
The original fix has been removed to fix these problems. As a
result the original problem may still occur. If a disk is
write-locked, it will not successfully complete mount
verification. The device will be marked as "wrong volume".
Compaq OpenVMS Engineering continues to research solutions to
this problem.
Images(s) Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
o A SSRVEXCEPT machine crash occurs at TPSERV+22800
Images(s) Affected:
- [SYS$STARTUP]DECDTM$STARTUP.COM
o An RMSBUG system crash occurs due to a zero status IOSB/ IOST in
an IO to SHDRIVER. The crashes result from application code not
being able to handle the zero status. One crash has been seen
in SWAPPER others have been seen in RMS.
Images Affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
o The SHLK$MERGE_SIGNAL code can be called multiple times. This
results in an unexpected locking failure which causes
SHADDETINCON crashes in the SHD_LOCK and SHLK$MERGE_SIGNAL
routines.
Images(s) affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
o There is an XQP crash in MOVEFILE when a compare error occurs
on a file header, while a disk that is shadow copying is also
being defragged with DFO.
Images(s) affected:
- [SYS$LDR]SYS$SHDRIVER.EXE
o The following cluster-related problems can occur:
1. SYS$SCS FAST_PATH RSPID = 0: "STALE READ/WRITE
DATA-CORRUPTION" or SYS$DUDRIVER cancel-related INVEXCEPTN
bugcheck
Incorrect SYS$SCS FAST_PATH Response-ID (RSPID) handling
results in 1) RSPID=0 and 2) a "stale" CDRP in the
Response-Descriptor-Table (SCS$GL_RDT) index-0. RDT
scans on DU-connection-failover or DU-I/O "CANCELing"
will attempt to process the "stale" CDRP, with either
of the following results:
- SYS$DUDRIVER/DUTU$CANCEL (or DUTU$END_CANCEL)
INVEXCEPTN bugchecks or
- DATA-CORRUPTION due to re-issuing MSCP-I/O on "stale"
CDRP
2. SCAN_RDT STALE-CDRP "RSPID" verification to avoid
potential DATA-CORRUPTION from "STALE" CDRPs
If an SCS system application (DUDRIVER) fails to
de-allocate an "RSPID", a "stale" CDRP pointer will be
left in the RDT. A check is added for "stale" CDRPs on
RDT-scans, to avoid data corruption due to unintended
reprocessing of a recycled CDRP.
Images(s) affected:
- [SYS$LDR]SYS$SCS.EXE
o If a PARTIAL type software product is installed on the top of
existent FULL type product that has been patched by PATCH type
kits, two versions of the same product are left installed.
This results in the patches from the FULL product not being
transfered to the PARTIAL product. Eventually, this leads to
unrepairable PCSI database corruption.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o When installing FORTRAN and FORRTL products, the system hangs
if both products are selected for installation at the same
time.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o When there are multiple patch kits that ship the same image or
file and the patch kits are installed out of order, POLYCENTER
Software Installation utility can ACCVIO when trying to
resolve file conflict.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o A PGFIPLHI system crash occurs during startup. The current
process is SYSINIT.
Image(s) Affected:
- [SYSEXE]SYSINIT.EXE
Problems Addressed in VMS712_UPDATE-V0300 Kit Rated as "2":
o Memory Channel is not checked as a valid cluster interconnect
if no CI or DSSI is present. This causes CLUSTER_CONFIG.COM
to abort and not add the new cluster member.
Image(s) Affected:
- [SYSMGR]CLUSTER_CONFIG.COM
o Under some conditions, a traceback list from a fatal error in
a DEC BASIC program would indicate some incorrect line
numbers. This DEC$BASRTL.EXE fixes the stack correctly before
displaying the traceback, so the line numbers are correct.
Note that an updated TRACE.EXE may also be required to correct
all of the line numbers.
Image(s) Affected:
- [SYSLIB]DEC$BASRTL.EXE
o Customers who install or upgrade to V7.1-2 or later versions
of OpenVMS ALPHA may experience Hub Timeout errors, Memory
Channel port re-inits and virtual circuit closure on Memory
Channel 1.0 or 1.5 devices. This problem is not seen on
Memory Channel 2.0 devices. In some cases the memory channel
adapter has been set offline and the customer must reboot to
re-enable it.
Image(s) Affected:
- [SYS$LDR]SYS$MCDRIVER.EXE
Problems Addressed in VMS712_UPDATE-V0300 Rated a "3":
o The following duplicate message is reported by the PCSI
utility while an upgrade of a product is performed:
PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS
-PCSI-I-VOLSPC, 159261 required; 124344 available; -34917 net
Terminating is strongly recommended.
Do you want to terminate? [YES]
%PCSI-E-INSVOLSPC, insufficient space on volume DISK$ALPCSI_SYS
-PCSI-I-VOLSPC, 128172 required; 124344 available; -3828 net
Terminating is strongly recommended.
Do you want to terminate? [YES]
The fix ensures that only one of these two messages is
reported with proper data.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o Re-installation of a PARTIAL kit causes an ACCVIO.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o An upgrade of OpenVMS would generate an unexpected prompt to
terminate the operation.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SUSUPD]DCL.EXE
o When reinstalling a product that has a library module in its
Product Description File (PDF), the PCSI utility terminates
with an ACCVIO error.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o The way file conflict resolution was implemented in the case
of a product being re-installed was changed. Previously,
since file(s) on the system and the file(s) in the kit being
re-installed were the same, the file(s) on the system would be
selected as winning the conflict resolution and the kit
file(s) would not be re-installed. The new approach is to
declare the file(s) in the kit as the winner of the conflict
resolution and re-install them.
This allows re-installation of the files in case the file on
the system is corrupted.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o When a patch kit is applied to a full product, re-installed,
then re-installed again, the PCSI utility ACCVIOs.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o An ACCVIO occurs after the following sequence of steps is
taken:
1. A full product is installed
2. A patch is applied to it
3. The full product is reconfigured
4. The patch kit is reinstalled.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o When the execution of a PRODUCT command causes the number of
software references to another product to go to zero, the
utility normally asks the users if they want to remove this
product as part of the operation. However, it is inappropriate
to ask users if they want to remove the operating system. This
can occur, for example, if the user removes the only product that
has a stated software dependency on VMS. This change excludes
the operating system from the scope of this question.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
- [SYSUPD]PCSI.CLD
o Processes can hang (deadlock) when dismounting a device.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
- [SYS$LDR]F11BXQP.STB
NOTE: The problem described below is not addressed in this
VMS712_UPDATE-V0300 kit. It will be addressed in a
future TIMA kit.
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 a '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 Affected:
- [SYS$LDR]F11BXQP.EXE
- [SYS$LDR]F11BXQP.STB
o Occasional false end-of-file (EOF) errors can occur on a read
operation.
Image(s) Affected:
- [SYS$LDR]F11BXQP.EXE
- [SYS$LDR]F11BXQP.STB
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.
Image Affected:
- [SYS$LDR]F11BXQP.EXE
- [SYS$LDR]F11BXQP.STB
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:
- [SYS$LDR]F11BXQP.EXE
- [SYS$LDR]F11BXQP.STB
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 will
fail. However, the blocking lock (F11B$b) is left with the
process.
Images(s) Affected:
- [SYS$LDR]F11BXQP.EXE
o The System hangs. If a forced crash is performed, analysis of
the forced crash shows that many processes are waiting in a
MUTEX state. The processes are not out of TQELM or BYTLM nor
are they waiting on an owned mutex. In each case, the event
flag wait mask field (PCB$L_EFWM) contains the address of a
CFCB (cached file control block).
Image(s) Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES.STB
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYS$LDR]IO_ROUTINES_MON.STB
o If a process tries posting more QIOs than is allowed by the
process buffered I/O quota, and that process does this while
resource wait is disabled, the BIOCNT will end up larger than
it should. When the process is later deleted it will hang
waiting for the BUFIOCNT to match the BUFIOLIM - resulting in
an unkillable looping process.
Image(s) Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.STB
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.STB
o The system crashes with bugcheck code WSLVANVAL or the system
crashes with bugcheck code SECREFNEG. In either case, there
has been an I/O error on a device.
Image(s) Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYS$LDR]IO_ROUTINES.STB
- [SYS$LDR]IO_ROUTINES_MON.STB
o Heavy $GETQUI usage while scanning a list of context blocks in
which the list has changed out from under the current code
thread, could induce a nonfatal SSRVEXCEPT bugcheck at
EXE$GETQUI_CONTEXT_FIND_C+00018.
It has also induced a fatal DOUBLDEALO bugcheck at
EXE$DEALLOCATE_C+00114, trying to deallocate a P1 context
packet (in R0) that has already been deallocated.
Image(s) Affected:
- [SYS$LDR]MESSAGE_ROUTINES.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 The SYS$FAO system service could incorrectly truncate output
strings when the !XW and !XL format codes are used. SYS$FAO
could also sometimes put a null character in the last
character position of a formatted output string.
Image(s) Affected:
- [SYS$LDR]MESSAGE_ROUTINES.EXE
o INCONSTATE system crash at SYS$VCC+000087F0
Image(s) Affected:
- [SYS$LDR]SYS$VCC.EXE
- [SYS$LDR]SYS$VCC_MON.EXE
o A process can hang in RWAST state during image or process
rundown. The process has user defined virtual regions and
there is also direct I/O outstanding for this process. This
can occur if the system is running Oracle7 or Oracle8 and
MULTINET.
Image(s) Affected:
- [SYS$LDR]SYSTEM_PRIMITIVES.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES.STB
- [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB
o INCONMMGST crashes can occur. There is no specific "trigger"
to these crashes, other than heavy modified page writing.
This typically occurs on a memory starved system, or if
processes run images that greatly exceed their working set
quotas.
Image(s) Affected:
- [SYS$LDR]SYS$VM.EXE
o IPL synchronization issues in the Cluster Wide Process
Services (CWPS) code or the $GETJPI system service opens a
context corruption timing window. The problem can crash
either the sending or target node in an OpenVMS Cluster via
CWSERR or INVEXCEPTN bugchecks in SYS$CLUSTER code. In most
cases the target node crashes but the actual corruption
occurred on the sending node.
Image(s) Affected:
- [SYS]PROCESS_MANAGEMENT.EXE
- [SYSLOA]SYS$CLUSTER.EXE
o Add GETLKB bounds check to prevent crash.
Image(s) Affected:
- [SYS$LDR]LOCKING.EXE
o F$GETSYI("PALCODE_VERSION") returns a 16-byte string
consisting of 8 bytes of version number followed by 8 bytes of
null (hex 00). F$EDIT functions such as TRIM and COMPRESS do
not remove the trailing nulls.
Image(s) Affected:
- [SYS$LDR]SYSGETSYI.EXE
o The user sees an error that a device on the boot command line
could not be found, and the system halts.
Image(s) Affected:
- [SYS$LDR]EXEC_INIT.EXE
o MSCPCLASS, Fatal bugcheck error detected by MSCP class driver
Image(s) Affected:
- [SYS$LDR]SYS$DUDRIVER.EXE
- [SYS$LDR]SYS$TUDRIVER.EXE
o An INIT/DENSITY command for a TSZ07 tape drive that is locally
connected to a SCSI adapter, then TMSCP served to the clients
does not work. If the tape has been previously initialized to
and the INIT command issued specifies a new density, the
command will not fail but the requested density is not
honored. The tape remains at the old density.
Image(s) Affected:
- [SYS$LDR]SYS$TUDRIVER.EXE
o The following problems are corrected:
* When there is no video card installed in an ES40, DS20 or
DS10/VS10, an attempt to mount an IDE/ATA hard drive or
ATAPI CD-ROM or DVD-ROM drive crashes or hangs the system.
* Disk drives were occasionally timing-out upon mounting.
Image(s) Affected:
- [SYS$LDR]SYS$DQDRIVER.EXE
o If the DRDRIVER (For the KZPAC Mylex RAID controller)
configures before DQDRIVER, the DQDRIVER's DMA windows in
PCIbus space are shifted out of natural alignment. This
typically happened on an ES40 when the KZPAC was installed
in Hose 0. The DQDRIVER was not able to handle this situation
and ended up destroying other structures in memory.
Image(s) Affected:
- [SYS$LDR]SYS$DQDRIVER.EXE
o HDRFULL and BADFID errors have been traced to the handling of
NOCLU.
Image(s) Affected:
- [SYS$LDR]SYS$DRDRIVER.EXE
o In tri-host SCSI clusters it is possible for a system to see a
SCSI disk MSCP served from two other hosts before it configures
it via a local SCSI port. CHECK_EXTRAPATH in DKDRIVER simply
quits if it finds an MSCP served UCB for a device with the 2P
bit set. It does not disable either the MSCP served nor the
newly-found local UCB. Therefore, two UCBs for the same device
are configured.
Image(s) Affected:
- [SYS$LDR]SYS$DKDRIVER.EXE
o INVEXCEPTN System crash due to memory corruption. In this
particular case a driver image was overwritten by some user
data.
Image(s) Affected:
- [SYS$LDR]SYS$DKDRIVER.EXE
o A system may crash with an "INVEXCEPTN above ASTDEL", access
violation, when using HSZTERM, the HSZxxx configuration tool.
Image(s) Affected:
- [SYS$LDR]SYS$DKDRIVER.EXE
o Skipfile works until a fatal error occurs. Then it is
permanently disabled until the next reboot. This slows down
BACKUPs of appended save sets to unacceptable lengths of time.
Image(s) Affected:
- [SYS$LDR]SYS$MKDRIVER.EXE
o Process I/O hangs. The driver is unable to get mapping
resources needed for I/O.
Image(s) Affected:
- [SYS$LDR]SYS$PKEDRIVER
- [SYS$LDR] SYS$PKTDRIVER
o If a shadowset is also a Pagefile disk, and a mount
verification occurs for one of the set members, the
failure IO Status is not copied to the IOST1 field.
Whatever block was passed in the IRP$L_MEDIA field is
left as an incorrect IO status.
Image(s) Affected:
- [SYS$LDR]SYS$DKDRIVER
o After issuing a command to shutdown UCX, the system crashes
with an INVEXCEPTN at SYS$FXDRIVER+117C0.
Image(s) Affected:
- [SYS$LDR]SYS$FXDRIVER.EXE
o INCONSTATE bugchecks during boot caused by Tulip device driver
soft error handling.
Image(s) Affected:
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$ERDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
o The following switch and options are added to the MOUNT
command:
* /POLICY=REQUIRE_MEMBERS - Force all specified members to
be available for MOUNT to occur.
Used in disaster-tolerant configurations where another
site may have a more recent disk that is not available.
In effect, this will force more human decision making.
* /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 mis-typed 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 %MOUNT-F-VOLALRMNT errors are received when MOUNTing multiple
CDs privately.
Image(s) Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
o A new check is provided 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 (e.g., 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.
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, if
this condition is detected, a warning message is displayed:
%MOUNT-W-INCONSIZE, inconsistent number of blocks reported,
some data may not be accessible
Note that the warning message text will be shipped in a
separate kit, ALPMSGF04_062, which contains the SYSMSG.EXE
image. If the ALPMSGF04_062 kit has not been installed, then
the following message will be output:
%MOUNT-W-NOMSG, Message number 007290D0
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 /MEDIA_FORMAT and /DENSITY qualifiers are not always handled
properly, resulting in tapes being written in different modes
than intended.
Image(s) Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
o An access violation occurs in BACKUP if MME is installed/enabled.
The ACCVIO happens because status information in a common block
is no longer available due to the memory being freed by the time
that the EXIT_HANDLER
Image(s) Affected:
- [SYSLIB]BACKUPSHR.EXE
o Changes were made to the backup shareable image for V7.1-2
that are not backward compatible with the V7.1 BACKUPSHR.
For example, BCK_OPT_K_VERIFY is misinterpreted as
BCK_OPT_K_VALIDATE_PARAMETERS.
According to the V7.2-1 release notes, the BACKUP API for
V7.1-2 and V7.2 are not compatible across stated releases due
to a change in certain item codes and symbol definitions.
Image(s) Affected:
- [SYSLIB]BACKUPSHR.EXE
o When using an Identifier String for a /BY_OWNER qualifier
value, the user would receive an %BACKUP-F-BADOPTVAL error.
For example:
$ BACKUP SOURCE:*.*/BY_OWNER=FRED 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 The following five BACKUP problems are corrected:
1. BACKUP/SINCE and /BEFORE produces unexpected results.
2. A process dump cannot be produced if BACKUP fails.
3. Using BACKUP/ENCRYPT in BATCH results in an
%BACKUP-F-ENCNOTSUP error.
4. The default for /BEFORE=(value) is now the same as
/SINCE= (value).
5. /DRIVE_CLASS qualifier not processed properly.
(MME-related qualifier)
Image(s) Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
- [CLD]BACKUP.CLD
o INCONSTATE crash in SYS$LTDRIVER.
Image(s) Affected:
- [SYS$LDR]SYS$LTDRIVER.EXE
o An INVEXCEPTN crash will occur in the LT$CRASH routine if a
periodic timeout event is declared when SSB$B_SOL_STATE = 0.
Image(s) Affected:
- [SYS$LDR]LTDRIVER.EXE
o Problems corrected for static service lookup and LAT:
1. Sometimes unable to set or change the static rating of a
LAT service when offered by more than one node.
2. SSRVEXCEPT bugcheck with LATACP as the current image when
doing a LATCP> SHOW NODE command on a remote node.
Image(s) Affected:
- [SYSEXE]LATACP.EXE
o ACMS SI, RDb SQL and/or DECdtm $ADD_BRANCH(W) calls fail with
IPC-E-BCKTRNSFAIL. This occurs with Alpha and VAX platforms
running DECnet Plus where a distributed transaction was being
initiated.
Image(s) Affected:
- [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE
o An SSRVEXCEPT (ACCVIO) in SYS$TRANSACTION_SERVICES occurred
when an RDB recovery process was killed after it had been
identified as stalling the system.
Image(s) Affected:
- [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE
o When the user stops an ACMS application (using the command
ACMS/STOP APPL application-name), an ACMS server process
attached to the database hangs and prevents execution of the
database recovery processes. If the user then uses DECamds to
stop the server process, the system crashes with an ACCVIO
error.
Image(s) Affected:
- [SYS$LDR]SYS$TRANSACTION_SERVICES.EXE
o MOUNT/MEDIA=DENSITY DEV(x) was not handling density setting
correctly, so density was not being enabled.
Image(s) Affected:
- [SYS$LDR]SYS$MADDRIVER.EXE
o In a multi-processor environment, the service solicitation
queues may be accessed by several processors. The solicit
queue gets corrupted, crashing the system
Image(s) Affected:
- [SYS$LDR]SYS$LASTDRIVER.EXE
o If a tape is initialized on a TZ87, then that tape is put on
a TZ86 and an attempt is made to re-initialize the tape, the
TZ86 takes much more time than usual to determine how to
handle the tape.
Image(s) Affected:
- [SYS$LDR]SYS$MADDRIVER.EXE
o Tape intermittently fails to mount with a DEVREQERR error.
Image(s) Affected:
- [SYS$LDR]SYS$MADDRIVER.EXE
o The BLISS compiler produces an error message stating that
NEWVAL is not initialized in routine LADCP_SET.
Image(s) Affected:
- [SYSEXE]ESS$LADCP.EXE
o With multiple kernel threads enabled, applications which use
the C runtime library routine getenv may fail due to the stack
of the calling thread being corrupted. This usually presents
itself as random access violations. The bad address is always
a process identification (pid) of one of the kernel threads in
the process.
Applications which use getenv may also hang with all threads
in the HIB state. The initial kernel thread will have user
mode ASTs disabled
Image(s) Affected:
- [SYSEXE]DCL.EXE
o If a DCL command file is executed in batch mode and an error
occurs on an ON ERROR GOSUB command, the GOSUB pointer returns
to an incorrect line in the command file.
Image(s) Affected:
- [SYSEXE]DCL.EXE
o A BACKUP command fails with a %DCL-W-NOPAREN error if a space
separated a value from its terminating parenthesis, as in the
following command:
BACKUP saveset/SAVE/SELECT=(FOOBAR.TXT ) SYS$SCRATCH:/LOG
Image(s) Affected:
- [SYSEXE]DCL.EXE
o If the logical, SYS$LANGUAGE is set to a language not
supported by LIBRTL, the MAIL "DIRECTORY" command does not
work. For Example:
$ define SYS$LANGUAGE abcde-xyz
%DCL-I-SUPERSEDE, previous value of SYS$LANGUAGE has been
superseded
$ mail
MAIL> dir
MAIL
# From Date Subject
%LIB-W-ENGLUSED, English used, could not determine user's language
MAIL>
Image(s) Affected:
- [SYSEXE]MAIL.EXE
o EXTRACT/FOREIGN does not create the output file, and the user
is not notified.
Image(s) Affected:
- [SYSEXE]MAIL.EXE
o Starting with V7.0, if a user attempted 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 MC LCSR values are wrong in errlog device-attn entries:
* MC$INTERRUPT immediately clears the LCSR interrupt flag
bits so that subsequent interrupts will be seen. However,
this means that the DEVICE_ATTENTION error log entries are
always clear.
* Community state was being written to the PDT instead of
DMP
Image(s) Affected:
- [SYS$LDR]SYS$MCDRIVER.EXE
o The Parallel Processing Library (PPLRTL) could end up in an
infinite compute loop.
Image(s) Affected:
- [SYSLIB]PPLRTL.EXE
o Performance enhancement: RMS RU journaling file naming
change.
This enhancement reduces the directory overhead associated
with journal file creation and deletion.
Prior to Version 7.2, recovery unit (RU) journals were created
temporarily in the [SYSJNL] directory on the same volume as
the file that was being journaled. The file name for the
recovery unit journal had the form RMS$process_id (where
process_id is the hexadecimal representation of the process
ID) and a file type of RMS$JOURNAL.
The following changes are being introduced to RU journal file
creation in this remedial release of OpenVMS Version 7.1:
* The files are created in node-specific subdirectories of
the [SYSJNL] directory
* The file name for the recovery unit journal has been
shortened to the form: YYYYYYYY, where YYYYYYYY is the
hexadecimal representation of the process ID in reverse
order.
The following example shows both the previous and current
versions of journal file creation:
Previous versions: [SYSJNL]RMS$214003BC.RMS$JOURNAL;1
Current version: [SYSJNL.NODE1]CB300412.;1
If RMS does not find either the [SYSJNL] directory or the
node-specific directory, RMS creates them automatically.
This enhancement is included in OpenVMS Alpha V7.2.
Image(s) Affected:
- [SYS$LDR]RMS.EXE
o SDA's SHOW PROCESS/IMAGE and MAP commands provide confusing
data if a protected image has a separate change-mode vector
and another image appears between the protected image and
its change-mode vector. SHOW PROCESS/IMAGE may show multiple
images occupying the same address space, and MAP may identify
the wrong image. SHOW PROCESS/IMAGE now provides a completely
new display that avoids the overlap. MAP recognizes that an
apparent overlap is possible and identifies the correct image.
Image(s) Affected:
- [SYSLIB]SDA$SHARE.EXE
o If the SYSGEN parameter ERLBUFFERPAGES is raised above the old
(V7.1) maximum of 32 pagelets, SDA ($ ANALYZE/CRASH) will give
the error:
%SDA-W-ERLBUFTOOBIG, size of error log buffers exceeds
maximum for system parameter ERLBUFFERPAGES
Image(s) Affected:
- [SYSLIB]SDA$SHARE.EXE
o SET SECURITY/DEFAULT is not updating the modify date:
1. The modified (revised) date is not updated on a file when
the file object attributes are reset to default with the
following command:
$ SET SECURITY filex.xxx /DEFAULT
2. Errors occur when long (or UCS2) filenames are 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 TurboLaser error handling problems occur:
1. In the event of handling a correctable memory error, which
is non-fatal, the system experiences an INCONSTATE crash.
2. In the event of handling a TIOP 620 machine check error,
the system could experience an INVEXCEPTN crash.
Image(s) Affected:
- [SYS$LDR]SYS$CPU_ROUTINES_0C05.EXE
- [SYS$LDR]SYS$CPU_ROUTINES_0C08.EXE
o The Debugger's source view oscillates horizontally (steady
state) after upgrade to Motif V1.2-5.
Image(s) Affected:
- [SYSLIB]DEBUGSHR.EXE
- [SYSLIB]DEBUGUISHR.EXE
- [SYSLIB]VMSDEBUGUIL.UID
o Under certain stack environments, the routine LIB$CONVERT_DATE_STRING
will return incorrect values for the strings "YESTERDAY" and
"TOMORROW" (the date actually returned is "today"). This problem
is dependent on the on stack contents at the time of the call.
Image(s) Affected:
- [SYSLIB]LIBRTL.EXE
- [SYSLIB]LIBRTL_INSTRUMENTED.EXE
o LMF would return a LICENSE$_EXCEEDED OPCOM error if a valid
VOLSHAD-DISK license was in use. LMF has been changed to
simply check for the presence of valid licenses. LMF will
look for a VOLSHAD license only if the VOLSHAD-DISK check
returns a LICENSE$_NOLICENSE error.
Image(s) Affected:
- [SYS$STARTUP]LICENSE_CHECK.EXE
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 #####
Image(s) Affected:
- [SYSEXE]OPCOM.EXE
o An INVEXCEPTN bugcheck may occur due to ACCVIO or page fault
at high IPL.
Image(s) Affected:
- [SYS$LDR]SYS$FTDRIVER.EXE
o SORT32 sees a 24 byte memory loss across calls.
Image(s) Affected:
- [SYSLIB]SORTSHR.EXE
o SCSI-1 devices fail with MEDOFL using PKEDRIVER.
Image(s) Affected:
- [SYS$LDR]SYS$PKEDRIVER.EXE
- [SYS$LDR]SYS$PKTDRIVER.EXE
PROBLEMS ADDRESSED IN VMS712_GRAPHICS-V0100 KIT
o PowerStorm 4D10T text corruption fix
If the PowerStorm 4D10T card is used, text is corrupted when
bringing up a list box in the EVE DECwindows interface.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o SPLIPLHIGH crash
System crash with SPLIPLHIGH in INDRIVER during boot on some
AlphaServer 1000a systems.
Image(s) Affected:
- [SYS$LDR]SYS$INDRIVER.EXE
o Bell pitch and duration problems
Bell pitch and duration are not handled by the correct
sliders, or by xset. The bell volume can't be set on
AlphaStations. Previously, setting the volume on an
AlphaStation would affect the pitch and duration and setting
the pitch and duration would have no effect. With the change,
the pitch and duration can be controlled normally and setting
the volume has no effect.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DIX.EXE
- [SYS$LDR]SYS$INDRIVER.EXE
- [SYS$LDR]SYS$IKBDRIVER.EXE
o Screen 0 has no colors
Screen 0 has no colors in a multi-head PowerStorm 3D30
installation.
Image(s) Affected:
- [SYS$LDR]SYS$INDRIVER.EXE
o Autorepeat rate is too high
Autorepeat rate is too high when using the PowerStorm 3D30 and
4D20 on a DPWS (Digital Personal Workstation).
Image(s) Affected:
- [SYS$LDR]SYS$GYCDRIVER.EXE
o Console and ^F2 mode switching problems.
Console and ^F2 mode switching problems when using the
PowerStorm 3D30 and 4D20.
Image(s) Affected:
- [SYS$LDR]SYS$GYCDRIVER.EXE
o PowerStorm 4D20 does not correctly install private colormaps
The PowerStorm 4D20 does not correctly install private
colormaps in its 8-plane default mode.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GY.EXE
- [SYSLIB]DECW$SERVER_DDX_WMB_GY.EXE
o DMA on the PowerStorm 3D30/4D20 causes window corruption.
DMA on the PowerStorm 3D30/4D20 on small memory systems (less
than 1GB) causes window corruption.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GY.EXE
- [SYSLIB]DECW$SERVER_DDX_WMB_GY.EXE
o Turbolaser Galaxies with graphics cards on the EISA bus do not
boot.
Turbolaser Galaxies with graphics cards on the EISA bus do not
boot.
Image(s) Affected:
- [SYSLIB]DECW$ICBM.EXE
o DMA does not work correctly when Open3D has been installed.
DMA does not work correctly when Open3D has been installed.
Image(s) Affected:
- [SYSMGR]DECW$DEVICE_CONFIG_GY.COM
o ACCVIO when using TGA graphics cards
An ACCVIO occurs during a Print Screen when using TGA graphics
cards.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GY.EXE
- [SYSLIB]DECW$SERVER_DDX_WMB_GY.EXE
o Corruption problem with the PowerStorm 4D10T graphics card
Corruption problem with the PowerStorm 4D10T graphics card due
to the card's ability to only handle 10 bits of precision.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o Bold fonts do not work properly
Bold fonts do not work properly when using the PowerStorm
4D10T graphics card.
Image(s) Affected:
- [SYSLIB]DECW$SERVER_DDX_GZ.EXE
o Fix PCSI ACCVIO
When there are multiple patch kits that ship the same image or
file and the patch kits are installed out of order, POLYCENTER
Software Installation utility can ACCVIO when trying to
resolve file conflict.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
New Functionality Addressed in the VMS712_4D20T01 Kit:
o This kit provides OpenVMS V7.1-2 support for the Compaq PowerStorm
4D10T (ELSA/Gloria) graphics option. You should install this kit
after installing the Motif layered product. After installation,
graphics operation of the 4D10T option will automatically start
graphics after system boot.
The default graphics settings are 1024x768 @70Hz with 8-bit pixels.
Additional resolutions are available, depending on the monitor and
environment:
640 x 480 8/24-bit 60, 65, 70, 75, and 85Hz
800 x 600 8/24-bit 60, 65, 70, 75, and 85Hz
1024 x 768 8/24-bit 60, 65, 70, 75, and 85Hz
1152 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1280 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1600 x 1200 8-bit only 60, 65, 70, 75Hz
1600 x 1280 8-bit only 60, 65, 70Hz
1920 x 1200 8-bit only 60, 65, 70Hz
These settings are changed by renaming:
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
to
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
and following the directions in the file (for example):
$ define/exec/system/nolog decw$server_refresh_rate 75
$ define/exec/system/nolog decw$server_pixel_depth 24
$ decw$xsize_in_pixels == 1280
$ decw$ysize_in_pixels == 1024
Note that Compaq recommends that the refresh rate be 70Hz or above
to avoid screen flicker with room lighting. In addition, the
monitor determines the highest settings. For instance, many
monitors will not support greater than 1280x1024, or may only
support that resolution at lower (60Hz) refresh rates.
For multiple heads, there can be separate values for each monitor:
$ define/exec/system/nolog decw$server_refresh_rate 75, 60, 70
$ define/exec/system/nolog decw$server_pixel_depth 24, 8, 8
$ decw$xsize_in_pixels == "1280, 640, 1600"
$ decw$ysize_in_pixels == "1024, 480, 1280"
The 4D10T has been tested with up to 7 heads. Only 4D10T cards
should be used together. Combinations with non-4D10T cards have not
been tested, and may not work.
New Functionality Addressed in VMS712_4D20T01:
o Compaq PowerStorm 4D10T graphics option support
This kit provides OpenVMS V7.1-2 support for the Compaq
PowerStorm 4D10T graphics option. You should install this kit
after installing the Motif layered product. After
installation, graphics operation of the 4D10T option will
automatically start graphics after system boot.
The default graphics settings are 1024x768 @70Hz with 8-bit
pixels.
Additional resolutions are available, depending on the monitor
and environment:
640 x 480 8/24-bit 60, 65, 70, 75, and 85Hz
800 x 600 8/24-bit 60, 65, 70, 75, and 85Hz
1024 x 768 8/24-bit 60, 65, 70, 75, and 85Hz
1152 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1280 x 1024 8/24-bit 60, 65, 70, 75, and 85Hz
1600 x 1200 8-bit only 60, 65, 70, 75Hz
1600 x 1280 8-bit only 60, 65, 70Hz
1920 x 1200 8-bit only 60, 65, 70Hz
These settings are changed by renaming:
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE
to
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM.
and following the directions in the file (for example):
$ define/exec/system/nolog decw$server_refresh_rate 75
$ define/exec/system/nolog decw$server_pixel_depth 24
$ decw$xsize_in_pixels == 1280
$ decw$ysize_in_pixels == 1024
Note that Compaq recommends that the refresh rate be 70Hz or
above to avoid screen flicker with room lighting. In
addition, the monitor determines the highest settings. For
instance, many monitors will not support greater than
1280x1024, or may only support that resolution at lower (60Hz)
refresh rates.
For multiple heads, there can be seperate values for each
monitor:
$ define/exec/system/nolog decw$server_refresh_rate 75, 60, 70
$ define/exec/system/nolog decw$server_pixel_depth 24, 8, 8
$ decw$xsize_in_pixels == "1280, 640, 1600"
$ decw$ysize_in_pixels == "1024, 480, 1280"
The 4D10T has been tested with up to 7 heads. Only 4D10T
cards should be used together. Combinations with non-4D10T
cards have not been tested, and may not work.
Problems Addressed in VMS712_DRIVER-V0100:
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
2. INIT-W-NOBADDATA, bad block data not found on volume
Note that an INIT of the same devices succeeds on the server.
Image(s) affected: [SYS$LDR]SYS$DUDRIVER.EXE
New Functionality Included in the VMS712_HARDWARE-V0100 Kit:
o OpenVMS support is provided for the following new Alpha
systems and hardware options:
+ Compaq AlphaServer ES40
+ Compaq AlphaServer DS10
+ Compaq AlphaStation VS10
o This kit includes the latest DQDRIVER, X-18.027. Using this
driver with OpenVMS Alpha Version 7.1-2 provides DMA support
on IDE/ATA hard drives and IDE (ATAPI) CD-ROM drives for the
following systems:
+ Compaq AlphaServer DS10 and Compaq AlphaStation VS10 systems
+ Compaq AlphaServer DS20 systems
+ Compaq AlphaServer ES40 systems
+ Second-generation DPWS/433au, DPWS/500au, and DPWS/600au
workstations
Only second-generation DPWS/433au, DPWS/500au, and
DPWS/600au workstations that use the Cypress IDE bridge
are supported. First-generation DPWS/xxxau systems that
use the Intel+CMD IDE bridge are not supported.
o Runtime and boot support for Compaq's Fast Ethernet Network
Interface Card (NIC) based on the i82558 controller. The
DE602 is a dual port NIC based on the i82558 controller.
This NIC supports 10/100 Mbits/sec, full/half duplex, and
auto negotiation.
Known Restrictions with the VMS712_HARDWARE-V0100 Kit:
o IDE/ATA Hard Drives and the ATAPI CD-ROM as System Disks with
the AlphaServer ES40
+ The Compaq AlphaServer ES40 systems have only one IDE
bus and the supplied IDE bus cable can connect only one
drive. Therefore, you can only connect a maximum of one
drive per host and that drive must be the included ATAPI
CD-ROM drive. An IDE/ATA hard drive currently cannot be
connected to a Compaq AlphaServer ES40.
Therefore, at this time, use of an IDE/ATA hard drive as
a system or data disk on a Compaq AlphaServer ES40 system
is not supported.
+ The DEC-AXPVMS-VMS712_HARDWARE-V0100-4.PCSI Remedial Kit
must be installed before IDE/ATA hard drives are used as
system disks. Until this Hardware kit is applied, the
DQDRIVER will not use DMA and performance of IDE/ATA/ATAPI
disks will be less than optimal.
+ The Compaq AlphaServer ES40 system can never be booted from
a DQB0: or DQB1: device. The Secondary IDE bus does not
exist on these systems.
o After a Compaq AlphaServer ES40 system is shut down, an ">>>init"
command must be performed at the console before an attempt is made
to boot an IDE CD-ROM.
o To increase performance with IDE/ATA/ATAPI Disk Drives, segregate
the slow drives onto their own IDE bus. For example,put the
magnetic disk(s) on the primary bus and the CD-ROM drive(s) on
the secondary bus, or vice-versa.
o Timeout errors will be logged when a nonexisting drive(s) is
booted. The system will always configure four devices:
DQA0:, DQA1:, DQB0:, and DQB1:. The system may not contain
actual drives for each of these four devices.
To show the type of device the system is connected to,
enter the following command at the DCL prompt:
$ SHOW DEVICE /FULL
During system initialization and subsequently, if an attempt is
made to mount a nonexistent drive when the system is booted, a
timeout error will be logged. This error can be ignored.
o Memory must be fully initialized before booting. The console
parameter that provides this function is MEMORY_TEST. The
default setting for this parameter is FULL, so memory should
be fully initialized after power up.
From the console prompt, the following command will tell you
the current memory_test setting:
>>> SHOW MEMORY_TEST
If the setting is set to anything but FULL, enter the following
command to ensure that memory is completely initialized before
booting:
>>> SET MEMORY_TEST FULL
>>> INIT
o On a Compaq AlphaServer ES40, do not configure the KZPAC adapter
in PCI slots, 0, 1, 2, or 3 if an IDE CD-ROM is being used. The
system will crash with this configuration.
o The Direct Memory Access (DMA) operation is supported for both
IDE/ATA hard drives and ATAPI CD-ROM drives. The ATAPI version
of the Iomega Zip drive is also supported as a data drive only
and operating in Progammed-I/O mode; the Zip drive itself does
not support DMA.
o Forming a shadow set containing IDE/ATA/ATAPI disk drives is
unsupported at this time.
o Disks controlled by the DQDRIVER can be shared in an OpenVMS
Cluster. However, in a SCSI cluster, the disks may not have
unique names. For example, if two systems each contain a
CD-ROM drive configured as the Master Drive and connected to
the Primary IDE Bus, both systems might identify the two drives
as $1$DQA0:. This makes it more difficult to use these CD-ROM
drives in a SCSI cluster.
The following two workarounds exist:
1. To eliminate this problem, assign the CD-ROM drives to
different IDE busses or set the drives Master/Slave
jumpers differently. On ES40 systems, you can use the
following drive assignments:
+ DQA0-Primary IDE Bus, Master Drive
+ DQA1-Primary IDE Bus, Slave Drive
On all systems except for the Compaq AlphaServer ES40,
you can use any of the following four possible drive
assignments:
+ DQA0-Primary IDE Bus, Master Drive
+ DQA1-Primary IDE Bus, Slave Drive
+ DQB0-Secondary IDE Bus, Master Drive
+ DQB1-Secondary IDE Bus, Slave Drive
By correctly configuring the Master/Slave jumpers, you
may be able to connect up to four CD-ROM drives in the
SCSI cluster before you encounter naming conflicts.
2. If you have a naming conflict:
+ Mount only one volume at a time (among the
conflicting drives)
+ Mount the volume locally (mount it at the system to
which the drive is actually connected)
+ Do not use the /CLUSTER qualifier on the '$MOUNT'
command
o The Compaq AlphaServer ES40 is configured with two internal
Fast Ethernet Adapters and the DE500-BA PCI Fast Ethernet
adapter. To ensure proper network operation, the console
environment variable for each adapter must be set to an
operating mode that is compatible will the network device
it is attached to.
This console environment variable is EWx0_MODE, where x is the
adapter's controller letter. The valid settings and the
corresponding operating modes, are as follows:
________________________________________________________________
Table_1: Settings and Operating Modes for Adapters
Setting Operating_Mode
____________________ _______________________
Twisted-Pair 10BaseT Half Duplex
Full Duplex, Twisted- 10BaseT Full Duplex
Pair
Fast 100BaseTX Half Duplex
FastFD (Full Duplex) 100BaseTX Full Duplex
Auto-Negotiate Negotiates the highest common
operating mode possible
________________________________________________________________
Some network devices, mainly switches, will attempt to AutoSense
if Auto-Negotiation fails. Auto-Sense does not guarantee that
the correct duplex mode will be selected, and may result in lost
data. The adapter should be set to Auto-Negotiation if the device
it is connected to is also set to Auto-Negotiation. Conversely,
the adapter should not be set to Auto-Negotiation if the device
it is connected to is not set to Auto-Negotiation.
o On Compaq AlphaServer ES40 systems, following system routines
cannot be used to perform I/O tribyte reads and writes:
+ IOC$READ_PCI_CONFIG
+ IOC$WRITE_PCI_CONFIG
+ IOC$READ_IO
+ IOC$WRITE_IO
If a device driver calls any of these system routines with a
length of three, one of the following methods must be used
instead, depending on the I/O card's characteristics:
+ For IOC$READ_IO and IOC$READ_PCI_CONFIG:
1) Use a longword read, and mask out the byte.
2) Do a combination of word and byte reads and
append the data.
+ For IOC$WRITE_IO and IOC$WRITE_PCI_CONFIG:
1) Read a longword, modify the tribyte, and rewrite
the longword.
Note that AlphaServer 8200/8400 and GS60/140 systems with
Alpha 21264 CPUs support tribyte reads and writes.
o This note applies to Compaq AlphaServer ES40 systems.
When device drivers call the IOC$CRAM_CMD, IOC$READ_IO,
and IOC$WRITE_IO system routines with the IOC$K_WORD or
IOC$K_WORD_LANED parameters, the I/O address must be on
a natural, word-aligned boundary. (In other words, the
I/O address must be an even number). If the I/O address
is an odd number, these system routines return SS$_BADPARAM.
o The FRU configuration tree provided by the Compaq AlphaServer
ES40 console firmware is not copied to the errorlog file if the
SYSGEN parameter ERLBUFFERPAGES is not large enough. Use the
following command to run AUTOGEN with the FEEDBACK option to
automatically calculate the correct setting of ERLBUFFERPAGES
and resize the SYS$ERRORLOG.DMP file to allow for the config-
uration error log entry:
$ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK
Problems Addressed in the VMS712_HARDWARE-V0100 Kit:
o Unable to LAN boot over FDDI on EV6 based systems.
Image(s) Affected:
- [SYS$LDR]SYS$FWBTDRIVER.EXE
- [SYSEXE]APB.EXE
o INVEXCEPTN bugcheck because of an ACCVIO in kernel mode.
Image(s) Affected:
- [SYS$LDR]SYSTEM_PRIMITIVES.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES_MON.EXE
o The execution throttle limits the number of simultaneous I/O
commands sent to each device by the Qlogic chip. It should
have been, but was not, set to the quantities defined by the
EEROMCONFIG utility. The hardware default appears to have
been 3 rather than the more appropriate EEROMCONFIG default of
16. This fix provides approximately 50% improvement in the
number of I/O's /sec when 15 simultaneous streams read 2-block
transfers from a disk on an HSZ.
Image(s) Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
o When there are multiple patch kits that ship the same image or
file and the patch kits are installed out of order, POLYCENTER
Software Installation utility can ACCVIO when trying to
resolve file conflict.
Image(s) Affected:
- [SYSEXE]PCSI$MAIN.EXE
- [SYSLIB]PCSI$SHR.EXE
Problems Addressed in VMS712_MOUNT96-V0100:
o OpenVMS V7.2 provided a new check to determine if the disk
that is being MOUNTed was 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 (for example, 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
was detected, then a fatal MOUNT-F-FILESTRUCT error was
reported and the MOUNT was aborted.
It has been determined that a number of systems are running
with disks which are in this condition. While there may be
data that is 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 the following
warning message rather than a fatal error:
%MOUNT-W-INCONSIZE, inconsistent number of blocks reported,
some data may not be accessible
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.
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
- [SYSMSG]SYSMSG.EXE
o Previously, a fix was included to address a problem in which
SWL disks do not come out of mount verification properly.
The fix insured that the VCB$T_VOLOCKNAM matches the
SCB$_VOLOCKNAME of the volume, even for privately mounted
disks. However, 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 causes a variety of symptoms, including access conflicts
during BACKUPs of the former member and in at least one case,
an XQPERR, Error detected by file system XQP bugcheck at
F11BXQP_PRO+0BE48. In addition, reports of systems unable
to MOUNT multiple CDROMS have been attributed to this problem.
Due to the problems that it caused, the original fix has been
removed. As a result, the original problem may still occur.
If a disk is write-locked, it will not successfully complete
mount verification. The device will be marked as "wrong volume".
Compaq OpenVMS Engineering continues to research solutions to
this problem.
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
o MEDIA_FORMAT and /DENSITY qualifiers are not always handled
properly, resulting in tapes being written in different modes
than intended.
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
o The following switches and options have been added to the
MOUNT command:
+ /POLICY=REQUIRE_MEMBERS
This forces all specified members to be available
for MOUNT to occur. This switch is used in
disaster-tolerant configurations where another site
may have a more recent disk that is not available.
In effect, this will force more human decision making.
+ /POLICY=VERIFY_LABELS
All copy targets must have the label "SCRATCH_DISK" or
they will not be added to the set. The volume must be
ODS2 and have a valid file structure. This change starts
forcing users to use alternate volume labels. One of the
biggest causes of incorrect disks being added to shadow
set is mistyped commands. Less data will be lost if
only "scratch" disks can be added to shadow sets.
This is similar to the /CONFIRM switch, 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".
Images Affected:
- [SYSLIB]MOUNTSHR.EXE
- [SYSEXE]VMOUNT.EXE
- [SYSMSG]SYSMSG.EXE
- [SYSLIB]DCLTABLES.EXE
Problems Addressed in VMS712_SCSI-V0100:
o A potential synchronization problem has been identified in
I/O stress testing of SYS$PKQDRIVER. Simultaneous execution
of the register write code path in the driver interrupt service
routine on the primary CPU, and execution of the register write
code path in the driver send command routine on a secondary CPU
may have led to system crashes.
Image(s) Affected: [SYS$LDR]SYS$PKQDRIVER.EXE
INSTALLATION NOTES:
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 VMS712_UPDATE /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 POLYCENTER Software Installtion kits can
be found by typing HELP PRODUCT INSTALL at the system prompt.
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, 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.
All trademarks are the property of their respective owners.
SCSI 7.1-2 VMS712
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dec-axpvms-vms712_update-v0300--4.README
dec-axpvms-vms712_update-v0300--4.CHKSUM
dec-axpvms-vms712_update-v0300--4.pcsi-dcx_axpexe
vms712_update-v0300.CVRLET_TXT
|
