Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPDUP01_062 Alpha V6.2 - V6.2-1H3 FYDRIVER ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: FYDRIVER.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPDUP01_062
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 252 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: Yes
Installation Rating: 3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for FYDRIVER on OpenVMS Alpha V6.2, V6.2-1H1,
V6.2-1H2, V6.2-1H3. This kit addresses the following problems:
o ALPHA systems that use multiple accesses to HSC/HSJ disk
controllers (such as using Polycenter System Census Agent) will
see crashes intermittently. The crashes showed RSPID (sysgen
parameter SYSRESPCNT) to be exhausted. Previous workaround was
to increase sysgen parameter and customer would not have
anymore crashes.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'ALPDUP01_062' or 'ALPDUP'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system must
be rebooted. If the system is a member of a VMScluster, the entire
cluster should be rebooted.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| SYS$FYDRIVER.EXE | 17C7D465 | X-3 | 5-JUN-1997 |
| | | 11:25:11.49 |
+----------------------------+----------+-----------------+--------------+
|