|
|
 |
HP Services Software Patches - alpmscp02_062
|
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) Digital Equipment Corporation 1997, 1998. All rights reserved.
OP/SYS: DIGITAL OpenVMS Alpha
COMPONENT: TMSCP.EXE
MSCP.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPMSCP02_062
ECO Kits Superseded by This ECO Kit: ALPMSCP01_062
ALPMSCP01_070 (For OpenVMS
Alpha V6.2
*ONLY*)
ECO Kit Approximate Size: 360 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: Yes
Rolling Reboot Supported: Yes
Installation Rating: 2 - To be installed on all systems running
the listed version(s) of OpenVMS and
using the following feature(s):
Systems that MSCP serve tapes and disks.
NOTE: The following remedial kit(s) must be installed BEFORE
installation of this kit:
ALPCLUSIO01_062
ECO KIT SUMMARY:
An ECO kit exists for TMSCP and MSCP on OpenVMS Alpha V6.2 through
V6.2-1H3. This kit addresses the following problems:
Problems addressed in ALPMSCP02_062:
o The ALPMSCP01_062 remedial kit required that the ALPCLUSIO01_062
kit be installed. If the user tried to install the ALPMSCP01_062
kit on a system that had both the ALPCLUSIO01_062 and OpenVMS
Alpha Y2K remedial kits installed, the ALPMSCP01_062 kit did not
recognize that the ALPCLUSIO01_062 kit had been installed. This
caused the ALPMSCP01_062 installation to fail.
There are no new ECO problem corrections in this kit. If you
have installed the ALPMSCP01_062 remedial kit, you do not need
to install the ALPMSCP02_062 remedial kit.
Problems addressed in ALPMSCP01_062:
o Unexpected end messages are logged on client nodes for GUS and
AVAILABLE commands. A Cache Data Lost error is detected in the
tape subsystem due to a hardware-related problem. A GUS end
message is returned to the client with an end message status of
08 (data error). This status is set up in the SEND_END routine
in TMSCP. Since this is not a valid status for a GUS, the client
TUDRIVER rejects the invalid status, logs an error and then calls
TU$RE_SYNCH which breaks the connection.
For the same Cache Data Lost error, if an AVAILABLE command is
issued, the controller should return CDL until the host clears
the condition in the controller. TUDRIVER in the server, upon
receipt of an end message for AVAILABLE which indicates CDL,
will then issue another AVAILABLE with the clear cache data
lost modifier set in the packet. The only status that is
checked on the receipt of this end message is for PRESE which
will return SS$_DATALOST. Anything else returns SS$_DATALOST.
o An INVEXCEPTN system crash may occur when TMSCP does not get a
message buffer during configuration when a connection to
MSCP$TAPE is broken.
o An inconsistent transfer count occurs when a forced error is
encountered on a drive. A drive directly attached (or HSx
served) reports a different transfer count from the same drive
served via the MSCP server.
Code that attempts to determine the LBN of a forced error
block by looking at the byte count in the IOST/IOSB will
arrive at different values on the same drive when directly
accessed or MSCP served.
Problems addressed in ALPMSCP01_070:
o The problem occurs when ERASE commands with history logging
are issued on MSCP clients for large numbers of blocks to MSCP
devices served by an OpenVMS MSCP server. On an Alpha server,
an "Illegal Command" entry will be posted in the system error
log and the command will be aborted. Typically, if the affected
device is part of a shadow set, the set will enter mount verifi-
cation and the I/O request will eventually fail with a "Fatal
Controller Error". On a VAX server, no immediate problem is
noticed but the possibility of corrupting a shadow set exists should
there be a failure during the execution of the ERASE command and
a mini-merge is performed when the set becomes available.
o A satellite node will not boot after a preferpath/forcepath
command is issued on the server.
o Word instructions are used to reference a byte field.
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted.
If there are other nodes in the OpenVMS cluster, they must also be
rebooted in order to make use of the new image(s). If it is not
possible or convenient to reboot the entire cluster at this time, a
|
