| From: "OpenVMS.org Lists" <ovms-lists@openvms.org> | | Subject: VMS83I_LAN-V0700, ECO Kit Release | | Date: Tue, 04 Dec 2007 08:27:49 -0500 | | To: alerts@openvms.org |
|
 |
| The VMS83I_LAN-V0700 kit has been released. This kit should be
available on the following patch download site within 24
hours of receiving this announcement.
http://www.itrc.hp.com/service/patch/mainPage.do
ftp://ftp.itrc.hp.com/
Kit files are:
VMS83I_LAN-V0700.ZIPEXE
VMS83I_LAN-V0700.TXT
Following are the release notes for this kit.
****************************
ECO SUMMARY INFORMATION
****************************
Release Date: 4-DEC-2007
****************************
ECO SUMMARY INFORMATION
****************************
Release Date: 4-DEC-2007
=======================================================================
Hewlett-Packard OpenVMS ECO Cover Letter
=======================================================================
1 KIT NAME:
VMS83I_LAN-V0700
2 KIT DESCRIPTION:
2.1 Installation Rating:
INSTALL_2 : To be installed by all customers using the
following feature(s):
- LAN
2.2 Reboot Requirement:
Reboot Required.
HP strongly recommends that a reboot is performed immediately after
kit installation to avoid system instability. If you have other
nodes in your OpenVMS cluster, they must also be rebooted in order
to make use of the new image(s). If it is not possible or
convenient to reboot the entire cluster at this time, a rolling
re-boot may be performed.
2.3 Version(s) of OpenVMS to which this kit may be applied:
OpenVMS for Integrity Servers V8.3
2.4 New functionality or new hardware support provided:
Yes.
3 KITS SUPERSEDED BY THIS KIT:
- VMS83I_LAN-V0600
4 KIT DEPENDENCIES:
4.1 The following remedial kit(s), or later, must be installed
BEFORE installation of this, or any required kit:
- VMS83I_UPDATE-V0400
Page 2
4.2 In order to receive all the corrections listed in this kit,
the following remedial kits, or later, should also be
installed:
- None
5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83I_LAN-V0700
KIT
5.1 New functionality addressed in this kit
5.1.1 Add Shared Interrupt Support for BCM5715 Mezzanine Card
5.1.1.1 Functionality Description:
The 4-port BCM5715 mezzanine card requires the driver to
support shared interrupts for two of the ports. This kit
sets the bit that says the driver supports shared
interrupts.
Images Affected:
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
5.1.2 Additional Debug and Monitoring Support
5.1.2.1 Functionality Description:
Added support for additional debug and monitoring
functionality, via _MON versions of drivers. If the _MON
version of the driver is copied to the non _MON version,
or if the system is booted with system parameter
SYSTEM_CHECK set to 1, the debug and monitoring
functionality will be available.
Images Affected:
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
Page 3
5.1.3 Check for Non-standard Settings of the LAN_FLAGS System
Parameter
5.1.3.1 Functionality Description:
Check for non-standard settings of the LAN_FLAGS system
parameter. If reserved bits are set, a warning message
is displayed. If the settings could adversely affect
driver operation, the driver ignores the setting. In
both cases, an error log entry is made with the hex value
0xDAFF, indicating the LAN_FLAGS setting is non-standard.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
5.1.4 Receive Time Histogram Added
5.1.4.1 Functionality Description:
Driver internal counters have been modified to add a
receive time histogram which records the time that
applications took to process receive completion.
Images Affected:
- [SYSEXE]LANCP.EXE
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
Page 4
- [SYSLIB]LAN$SDA.EXE
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$EWDRIVER.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
5.1.5 Transmit and Fork Histogram Data Modified
5.1.5.1 Functionality Description:
The histogram data for transmit and fork has been
modified to be displayed all of the time, not just when
the /DEBUG qualifier is specified.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
Page 5
5.1.6 Mailbox size Increased
5.1.6.1 Functionality Description:
Mailbox size has been increased to account for a larger
volatile device database entry size to accommodate
cleared counters information. Note that this change
could require the BYTLM quota value to be increased for
the user account used to issue the LANCP counters
commands. If BYTLM is insufficient, a warning messages
will accompany the command output.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.1.7 CLEAR_COUNTERS and RESTORE_COUNTERS Qualifiers Added
5.1.7.1 Functionality Description:
Added support for CLEAR_COUNTERS and RESTORE_COUNTERS
qualifiers. The updated commands are:
LANCP> SHOW DEVICE/COUNTERS [/CLEAR_COUNTERS] -
[/RESTORE_COUNTERS]
LANCP> SHOW DEVICE/INTERNAL_COUNTERS [/CLEAR_COUNTERS] -
[/RESTORE_COUNTERS]
CLEAR_COUNTERS clears the counters (as seen by LANCP
only) after the counters are displayed.
RESTORE_COUNTERS restores the counters to the uncleared
state.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
Page 6
5.1.8 Retry Count and Timeout Values Increased
5.1.8.1 Functionality Description:
Retry count and timeout values increased for the LANCP
MOP CONNECT command to make connections more robust.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.1.9 Add New device IDs
5.1.9.1 Functionality Description:
Add the PCI device IDs for the AB385A, AD337A, AD338A,
AD339A, and NC364M LAN adapters.
Images Affected:
- [SYSEXE]SYS$CONFIG.DAT
5.2 Problems addressed in this kit
5.2.1 VMS83I_LAN-V0600 Patch Kit Might Not Install
LAN$SDA.EXE
5.2.1.1 Problem Description:
Due to an image generation issue the VMS83I_LAN-V0600
patch kit might not correctly install the LAN$SDA.EXE
image. This kit corrects that image generation issue and
correctly installs LAN$SDA.EXE.
Images Affected:
- [SYSLIB]LAN$SDA.EXE
5.2.1.2 CLDs, and QARs reporting this problem:
Page 7
5.2.1.2.1 CLD(s)
None.
5.2.1.2.2 QAR(s)
None.
5.2.1.3 Release Version of OpenVMS that will contain
this change:
Not applicable
5.2.1.4 Work-arounds:
None.
5.2.2 Intel Gigabit Transmit Timeout Error
5.2.2.1 Problem Description:
With certain packet sizes and under certain load
conditions, it is possible for the Intel gigabit chip to
lock up. This will result in a transmit timeout and
restart by the driver. In most cases, it is likely to
never happen or occur only rarely. In rare cases, it
might happen much more often, given application behavior
that uses the exact mix of packet sizes necessary to
induce the problem.
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.2.2.2 CLDs, and QARs reporting this problem:
5.2.2.2.1 CLD(s)
None.
5.2.2.2.2 QAR(s)
None.
Page 8
5.2.2.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.2.4 Work-arounds:
None.
5.2.3 Failover Sets Not Properly Read
5.2.3.1 Problem Description:
Failover sets that are defined in the LANCP permanent
database in prior versions of OpenVMS are not properly
read in V8.3. Executing a LANCP CONVERT DEVICE command
does not correct the problem.
Images Affected:
- [SYSEXE]LANCP.EXE
5.2.3.2 CLDs, and QARs reporting this problem:
5.2.3.2.1 CLD(s)
QXCM1000385682
5.2.3.2.2 QAR(s)
None.
5.2.3.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.3.4 Work-arounds:
None.
5.2.4 Network Applications Cannot be Started
Page 9
5.2.4.1 Problem Description:
In a standalone system (not clustered), network
applications cannot be started without first starting an
application in the physical device hosting the VLAN.
This leads to applications, such as DECnet and TCPIP
failing to start.
Images Affected:
- [SYS$LDR]SYS$VLANDRIVER.EXE
5.2.4.2 CLDs, and QARs reporting this problem:
5.2.4.2.1 CLD(s)
None.
5.2.4.2.2 QAR(s)
None.
5.2.4.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.4.4 Work-arounds:
None.
5.2.5 Unnecessary Error Log Entry
5.2.5.1 Problem Description:
When the system is booted and the link becomes available
for the first time, the driver posts an error log entry
even though this is not an error condition. With the
change in this kit, the driver will not post an error to
the device and will not make an error log entry. An
error log entry will still be made for each transition to
"link up" and "link down".
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
Page 10
- [SYS$LDR]SYS$EIDRIVER.EXE
- [SYS$LDR]SYS$EIDRIVER_MON.EXE
- [SYS$LDR]SYS$EW1000A.EXE
- [SYS$LDR]SYS$EW1000A_MON.EXE
- [SYS$LDR]SYS$EW5700.EXE
- [SYS$LDR]SYS$EW5700_MON.EXE
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
- [SYS$LDR]SYS$FWDRIVER.EXE
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.5.2 CLDs, and QARs reporting this problem:
5.2.5.2.1 CLD(s)
None.
5.2.5.2.2 QAR(s)
None.
5.2.5.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.5.4 Work-arounds:
None.
5.2.6 System Crash
5.2.6.1 Problem Description:
When an oversize packet is received, if the device has no
remaining buffers after receipt of the first buffer
segment, the driver does not discard the packet properly.
This results in a system crash shortly afterwards, when
subsequent receive processing continues. The changes
included in this kit will properly check for remaining
buffers, avoiding the crash.
Page 11
Images Affected:
- [SYS$LDR]SYS$EI1000.EXE
- [SYS$LDR]SYS$EI1000_MON.EXE
5.2.6.2 CLDs, and QARs reporting this problem:
5.2.6.2.1 CLD(s)
None.
5.2.6.2.2 QAR(s)
None.
5.2.6.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.6.4 Work-arounds:
None.
5.2.7 Corrupted Device Drivers
5.2.7.1 Problem Description:
The device counters displayed in the driver internal
counters get corrupted after a reset.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.7.2 CLDs, and QARs reporting this problem:
5.2.7.2.1 CLD(s)
None.
Page 12
5.2.7.2.2 QAR(s)
None.
5.2.7.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.7.4 Work-arounds:
None.
5.2.8 Transmit Timeout Problem
5.2.8.1 Problem Description:
A transmit could timeout if it was the last transmit and
there was no receive traffic.
Images Affected:
- [SYS$LDR]SYS$EWXFRAME.EXE
- [SYS$LDR]SYS$EWXFRAME_MON.EXE
5.2.8.2 CLDs, and QARs reporting this problem:
5.2.8.2.1 CLD(s)
None.
5.2.8.2.2 QAR(s)
None.
5.2.8.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.8.4 Work-arounds:
None.
Page 13
5.2.9 Duplicated "link up" Message.
5.2.9.1 Problem Description:
When auto-negotiation is in progress, the "link up"
message was displayed twice.
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.9.2 CLDs, and QARs reporting this problem:
5.2.9.2.1 CLD(s)
None.
5.2.9.2.2 QAR(s)
None.
5.2.9.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.9.4 Work-arounds:
None.
5.2.10 Incorrect Error Log Entry For "link down" Events.
5.2.10.1 Problem Description:
The error log entry code for "link down" events was 0xCA
"Connection Available" when it should have been 0xCD
"Connection Down".
Images Affected:
- [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE
5.2.10.2 CLDs, and QARs reporting this problem:
Page 14
5.2.10.2.1 CLD(s)
None.
5.2.10.2.2 QAR(s)
None.
5.2.10.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.10.4 Work-arounds:
None.
5.2.11 System Crash
5.2.11.1 Problem Description:
A system crash occurs when LANACP is run when no LAN
devices have been configured and DECnet-Plus has not been
initialized.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.2.11.2 CLDs, and QARs reporting this problem:
5.2.11.2.1 CLD(s)
None.
5.2.11.2.2 QAR(s)
None.
Page 15
5.2.11.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.11.4 Work-arounds:
None.
5.2.12 Only Last LL or VL Device Configured
5.2.12.1 Problem Description:
Only the last Logical LAN (LL) or VLAN (VL) device
present in the LAN permanent device database is
configured when LANACP is started. For example, if LLA,
LLB, VLA, VLB were defined in the LAN permanent device
database, only VLB would be configured on LANACP startup.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.2.12.2 CLDs, and QARs reporting this problem:
5.2.12.2.1 CLD(s)
None.
5.2.12.2.2 QAR(s)
None.
5.2.12.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.12.4 Work-arounds:
None.
Page 16
5.2.13 Unsupported FCARP Qualifier Removed
5.2.13.1 Problem Description:
The unsupported FCARP qualifier has been removed.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.2.13.2 CLDs, and QARs reporting this problem:
5.2.13.2.1 CLD(s)
None.
5.2.13.2.2 QAR(s)
None.
5.2.13.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.13.4 Work-arounds:
None.
5.2.14 LANCP SHOW Output Modified
5.2.14.1 Problem Description:
The output from a LANCP SHOW command has been modified to
show consistent header output that also includes the time
and node name in the header.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
Page 17
5.2.14.2 CLDs, and QARs reporting this problem:
5.2.14.2.1 CLD(s)
None.
5.2.14.2.2 QAR(s)
None.
5.2.14.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.14.4 Work-arounds:
None.
5.2.15 LANCP Hang Problem.
5.2.15.1 Problem Description:
It was possible for a LANCP PURGE DEVICE/ALL command to
hang scanning devices, requiring a Control-C or Control-Y
to terminate LANCP.
Images Affected:
- [SYSEXE]LANACP.EXE
- [SYSHLP]LANCP$HELP.HLB
- [SYSEXE]LANCP.EXE
5.2.15.2 CLDs, and QARs reporting this problem:
5.2.15.2.1 CLD(s)
None.
5.2.15.2.2 QAR(s)
None.
Page 18
5.2.15.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.15.4 Work-arounds:
None.
5.2.16 MCR NCL SHOW CSMA-CD Port * All induced System Crash
5.2.16.1 Problem Description:
An "MCR NCL SHOW CSMA-CD Port * All" command can result
cause a system crash.
Images Affected:
- [SYS$LDR]NET$CSMACD.EXE
5.2.16.2 CLDs, and QARs reporting this problem:
5.2.16.2.1 CLD(s)
QXCM1000435837
5.2.16.2.2 QAR(s)
None.
5.2.16.3 Release Version of OpenVMS that will contain
this change:
OpenVMS for Integrity Servers V8.3-1H1
5.2.16.4 Work-arounds:
None.
6 PROBLEMS ADDRESSED IN PREVIOUS KITS
Problems addressed by previously released VMS83I_LAN ECO kits can
be found in the following files:
o VMS83I_LAN-V100.RELEASE_NOTES
o VMS83I_LAN-V200.RELEASE_NOTES
Page 19
o VMS83I_LAN-V300.RELEASE_NOTES
o VMS83I_LAN-V400.RELEASE_NOTES
o VMS83I_LAN-V500.RELEASE_NOTES
o VMS83I_LAN-V600.RELEASE_NOTES
Before kit installation, these files can be extracted from the kit
via the following commands:
o To extract all release notes files at once use:
PRODUCT EXTRACT RELEASE_NOTES VMS83I_LAN /VERSION=7.0 -
[/file=destination_directory]
o To extract a single release notes file use:
PRODUCT EXTRACT FILE VMS83I_LAN /VERSION=7.0 -
/SELECT=[SYSUPD]release_note_name[/DESTINATION=destination_directory]
The names of individual RELEASE_NOTES files in the kit can be
found with:
PRODUCT LIST VMS83I_LAN /VERSION=7.0 /SELECT = *.RELEASE_NOTES
7 FILES PATCHED OR REPLACED:
o [SYSLIB]LAN$SDA.EXE (new image)
Image Identification Information
Image name: "LAN$SDA"
image file identification: "X-46A1"
image file build identification: "XBCA-00800700050"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:39.59
Overall Image Checksum: 229604356
o [SYSEXE]LANACP.EXE (new image)
Image Identification Information
Image name: "LANACP"
image file identification: "X-25"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:32.29
Overall Image Checksum: 3173101349
o [SYSEXE]LANCP.EXE (new image)
Image Identification Information
Page 20
Image name: "LANCP"
image file identification: "X-86"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:31.20
Overall Image Checksum: 1072676242
o [SYS$LDR]NET$CSMACD.EXE (new image)
Image Identification Information
Image name: "NET$CSMACD"
image file identification: "X-17"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:29.66
Overall Image Checksum: 750025201
o [SYS$LDR]SYS$EI1000.EXE (new image)
Image Identification Information
Image name: "SYS$EI1000"
image file identification: "X-35"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:36.08
Overall Image Checksum: 2867964795
o [SYS$LDR]SYS$EI1000_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EI1000_MON"
image file identification: "X-35"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:36.63
Overall Image Checksum: 2727003434
o [SYS$LDR]SYS$EIDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$EIDRIVER"
image file identification: "X-54"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:38.62
Overall Image Checksum: 3207276152
o [SYS$LDR]SYS$EIDRIVER_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EIDRIVER_MON"
Page 21
image file identification: "X-54"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:38.91
Overall Image Checksum: 2737869428
o [SYS$LDR]SYS$EW1000A.EXE (new image)
Image Identification Information
Image name: "SYS$EW1000A"
image file identification: "X-69"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:33.66
Overall Image Checksum: 1405754571
o [SYS$LDR]SYS$EW1000A_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EW1000A_MON"
image file identification: "X-69"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:34.09
Overall Image Checksum: 652592
o [SYS$LDR]SYS$EW5700.EXE (new image)
Image Identification Information
Image name: "SYS$EW5700"
image file identification: "X-76"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:34.93
Overall Image Checksum: 2369960489
o [SYS$LDR]SYS$EW5700_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EW5700_MON"
image file identification: "X-76"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:35.42
Overall Image Checksum: 26848870
o [SYS$LDR]SYS$EWDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$EWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-0080070021"
Page 22
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:20.39
Overall Image Checksum: 2388237354
o [SYS$LDR]SYS$EWDRIVER_DE500BA.EXE (new image)
Image Identification Information
Image name: "SYS$EWDRIVER_DE500BA"
image file identification: "X-5"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:24.49
Overall Image Checksum: 2424862029
o [SYS$LDR]SYS$EWXFRAME.EXE (new image)
Image Identification Information
Image name: "SYS$EWXFRAME"
image file identification: "X-26"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:37.45
Overall Image Checksum: 137115336
o [SYS$LDR]SYS$EWXFRAME_MON.EXE (new image)
Image Identification Information
Image name: "SYS$EWXFRAME_MON"
image file identification: "X-26"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:37.87
Overall Image Checksum: 3318132700
o [SYS$LDR]SYS$FWDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$FWDRIVER"
image file identification: "X-5"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:25.68
Overall Image Checksum: 517381042
o [SYS$LDR]SYS$VLANDRIVER.EXE (new image)
Image Identification Information
Image name: "SYS$VLANDRIVER"
image file identification: "X-16"
image file build identification: "XBCA-0080070021"
linker identification: "Linker T02-28"
Link Date/Time: 31-JUL-2007 11:31:27.56
Page 23
Overall Image Checksum: 1577394916
o [SYSHLP]LANCP$HELP.HLB (new file)
o [SYSEXE]SYS$CONFIG.DAT (new file)
8 INSTALLATION INSTRUCTIONS
8.1 Test/Debug Image Loss
In the course of debugging problems reported to OpenVMS
Engineering, customers may be given debug or point-fix images to
install. Typically, these images do not have the same image
generation flags contained in images released via the OpenVMS
remedial patch process. Because of this, any debug or point-fix
image that is in the SYS$COMMON area, will be replaced by any image
of the same name installed by this kit. If this occurs, you will
lose any functionality that is provided by the replaced image. If
you wish to retain these debug or point-fix images, you can take
the following steps:
o Prior to installing this kit, move the test/debug image(s) to
be saved to the SYS$SPECIFIC area.
o During kit installation, you will be asked if you wish to
delete the image(s) in SYS$SPECIFIC. You should answer NO for
each image that you want to keep.
o After installation completes, but before rebooting the system
(if required), move the image(s) from SYS$SPECIFIC back to
SYS$COMMON.
8.2 Compressed File
This kit is provided as a Self Extracting ZIPEXE kit. To expand
this file to the installable .PCSI file, run the file with the
following command:
$ RUN VMS83I_LAN-V0700.ZIPEXE
8.3 Installation Command
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 VMS83I_LAN[/SOURCE=location of Kit]
Note that this kit will install with the /SAVE_RECOVERY_DATA option
turned on. Using this qualifier will allow easy removal of the kit
from the system in the event of problems. If you wish to disable
Page 24
this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the
PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is
optional but highly recommended. Using this qualifier will allow
easy removal of the kit from the system in the event of problems.
The kit location may be a tape drive, CD, or a disk directory that
contains the kit. The /SOURCE qualifier is not needed if the
PRODUCT INSTALL command is executed from the same directory as the
kit location.
Additional help on installing PCSI kits can be found by typing HELP
PRODUCT INSTALL at the system prompt.
8.4 Scripting of Answers to Installation Questions
During installation, this kit will ask and require user response to
several questions. If you wish to automate the installation of
this kit and avoid having to provide responses to these questions,
you must create a DCL command procedure that includes the following
logical name definitions and commands:
o To avoid the BACKUP question, define the following:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
o To avoid the REBOOT question, define the following:
$ DEFINE/SYS NO_ASK$REBOOT TRUE
o To save replaced files as *.*_OLD define the following logical
name as YES. If you do not wish to save replaced files, define
the logical name as NO. Note that if you use the
/SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT
INSTALL command all replaced files will be saved as part of
that operation. There is no need to also save files as
*.*_OLD:
$ DEFINE/JOB ARCHIVE_OLD NO
o Add the following qualifiers to the PRODUCT INSTALL command and
add that command to the DCL procedure.
/PROD=HP/BASE=I64VMS/VER=V7.0 [/SOURCE=location of Kit]
o De-assign the logical names assigned
For example, a sample command file to install the VMS83I_LAN-V0700
kit would be:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ DEFINE/JOB ARCHIVE_OLD NO
$!
Page 25
$ PROD INSTALL VMS83I_LAN/PRODUCER=HP/BASE=I64VMS/VER=V7.0"
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
$!
9 COPYRIGHT AND DISCLAIMER:
(C) Copyright 2007 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or its
subsidiaries required for possession, use, or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer
Software, Computer Software Documentation, and Technical Data for
Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
Neither HP nor any of its subsidiaries shall be liable for
technical or editorial errors or omissions contained herein. The
information in this document is provided "as is" without warranty
of any kind and is subject to change without notice. The
warranties for HP products are set forth in the express limited
warranty statements accompanying such products. Nothing herein
should be construed as constituting an additional warranty.
DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY
THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL
EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR
PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE
FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH
MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.
|
|