|
|
 |
HP Services Software Patches - rsmsrveco2030
|
Copyright (c) Digital Equipment Corporation 1994, 1995. All rights reserved.
PRODUCT: POLYCENTER Software Distribution (RSM)
OP/SYS: OpenVMS VAX
OpenVMS Alpha
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: RSMSRVECO2030
ECO Kits Superseded by This ECO Kit: RSMSRVECO1030
ECO Kit Approximate Size: 9900 blocks
Kit Applies To: POLYCENTER Software Distribution V3.0
OpenVMS VAX V5.4-3 or later
OpenVMS Alpha V1.5 or later
System Reboot Necessary: No - unless you are running the LAST
protocol on a LAN adapter without
the DECnet protocol.
ECO KIT SUMMARY:
An ECO kit exists for POLYCENTER Software Distribution V3.0 on OpenVMS
VAX V5.4-3 or higher and OpenVMS Alpha V1.5 or higher. This kit
addresses the following problems:
o The RSM client kit is missing one image of the CAS sub-system. This
caused INSTALL RMS to OpenVMS Alpha clients to fail.
o ISL dies on certain processors with NVR$_NOTSUPPORTED due to the
STS$M_SEVERITY code being too high.
o ISL does not wait long enough for RSM$CLIENT_SYSTEM_DISK:.
o SDS> STOP PENDING * deletes too many files from RSM$PROCEDURES:.
o SDS> STOP PENDING during ISL of virgin client deletes client.
o ISL dies on certain processors with NVR$_NOTSUPPORTED due to the
STS$M_SEVERITY code being too high.
o ISL does not wait long enough for RSM$CLIENT_SYSTEM_DISK:.
o INIT$SHR is missing from VMSIMAGES.DAT.
NOTE: This is a problem with OpenVMS VAX V5.5-2.
o LAD container files on read-only media, such as CDROM, can not be
served.
o FETCH and/or INSTALL OPERA fails when /NAME= is long.
o SS$_DEVNOTMNT message in ISL after RSM$_DISPOSE informational.
o Client record does not get updated after successful ISL to virgin
client.
o SDS operations requiring RSM$CEA access terminate with status
00000000.
o The operating-system version field is corrupted by INSTALL RSM.
o BRS operations abort with SS$_EXQUOTA.
o Certain SDS update operations caused the list of applications
installed on a client to be cleared.
o Client APPLICATION information is not displayed if no RSM client is
present.
o BACKUP entries for OSname=AVMS is rejected.
o Unable to change /TARGET on existing BRS entry.
o LAD service names are wrong in RSM$CLUSTER_WIDE configuration.
o Can not MODIFY APPLICATION /NOREQUIRES without another
change-producing qualifier.
o The file SYS$LIBRARY:SDS_STRUCT.H was left out of the RSM V3.0
server kit.
NOTE: This file is only needed for developers of modular ISL code.
o Permit individual clients to control BKP quotas to prevent
SS$_EXQUOTA.
o Can not MODIFY SET /NOREQUIRES without another change-producing
qualifier.
o Wrong LAD service names are being broadcast when the RSM Server
is the cluster alias.
o After the installation of RSMSRVECO1030, the error SS$_IVBUFLEN
was returned in MOM.LOG for legacy ISL operations. This problem
was only visible when performing ISL operations to clients using
operating-systems FETCHed under V2.4 (or earlier) of RSM/PSD.
o Early termination of CEA work-process during SDS operations.
o During an INSTALL APPLICATION, the RSM$SDS_INSTALL_AP_POST.COM
command file runs as the last step before SDS_RECEIVE_STATUS. This
command file deletes the .DES file for the kit. However, the
next step calls the command file RSM$SDS_SET_STARTUP.COM to add
the startup file mentioned in the deleted .DES file. To workaround
this problem, the delete of the .DES file has been moved to
RSM$SDS_SET_STARTUP.COM.
o When the server uses the NI physical address 08-00-2B-..., failures
may occur for OpenVMS Alpha clients booting into ISLs.
o A loop may occur while scanning PRODUCTS array in client record.
o Due to an improper call to MEMSET, adding a member to group can
return the error SS$_ACCVIO.
o Premature deletion of .DES file occurred during the execution of
the command file RSM$TRIAL_INSTALL.COM.
o When the OpenVMS CHECKSUM program is used by RSM to check the
contents of the library .LDB files, CHECKSUM enters an infinite
loop if an error such as a network problem occurs. This resulted
in the filling up of all available space on the RSM$C_LOG: disk.
o ISL can hang when non-default execlets such as the POSIX kernel
image are loaded.
o An SS$_ACCVIO error is signaled in the MOM.EXE process during the
download of clients booting into ISL.
o During the final phases of an ISL to an Alpha system, it is possible
to observe the error "file not opened by DCL" in the NETSERVER.LOG
file on the RSM server and the automatic reboot fails.
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed
unless you are running the LAST protocol on a LAN adapter without the
DECnet protocol, such that LAST uses the 08-00-2B-... NI address instead
of the DECnet NI address AA-00-04-...
NOTE: You may verify this by executing the ESS$LADCP command
SHOW SERVICES from some other system than your RSM server. If
the 08-00-2B-... address appears in the display for your RSM
server system, you will need to reboot it after installing this kit.
Once the kit is installed, you will need to re-install the client
software on all RSM client systems using the following command:
DISTRIBUTE> install RSM [client name]
Also all OPERATING_SYSTEM images exhibiting the following problems:
o ISL dies on certain processors with NVR$_NOTSUPPORTED
o ISL does not wait long enough for RSM$CLIENT_SYSTEM_DISK:
o INIT$SHR is missing from VMSIMAGES.DAT on OpenVMS VAX V5.5-2.
o ISL can hang when non-default execlets such as the POSIX kernel
image are loaded.
will need to be re-FETCHed, using the following command:
|
Files on this server are as follows:
|
»rsmsrveco2030.README
»rsmsrveco2030.CHKSUM
»rsmsrveco2030.CVRLET_TXT
»rsmsrveco2030.a-dcx_axpexe
»rsmsrveco2030.a-dcx_vaxexe
|
