OpenVMS VMS73_RPC-V0100 RPC ALPHA 7.3 ECO Summary
TITLE: OpenVMS VMS73_RPC-V0100 RPC ALPHA 7.3 ECO Summary
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.pcsi-dcx_axpexe or
kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe. The
resultant file will be the PCSI installation file which can be
used to install the ECO.
New Kit Date: 28-FEB-2003
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2003. All rights reserved.
OP/SYS: OpenVMS Alpha
SOURCE: Compaq Computer Corporation
ECO Kit Name: VMS73_RPC-V0100
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 7872 Blocks
Kit Applies To: OpenVMS Alpha 7.3
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Information NA
Installation Rating: INSTALL_2
2 - To be installed by all customers using the following
COM, DCE and RPC
The following remedial kit(s) must be installed BEFORE
installation of this kit:
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
ECO KIT SUMMARY:
An ECO kit exists for RPC on Alpha V7.3. This kit addresses the following
PROBLEMS ADDRESSED IN VMS73_RPC-V0100 KIT
o When a large number of ACMSxp Processing servers are stopped
and re-started several times in a loop, DCE goes into a hang
o On cancellation of an RPC-call, the BG devices (Sockets) that
were allocated are not released. Several such RPC call
cancellations can result in a pileup of BG devices leading to a
o A memory leak is encountered in DCE/RPC when DCOM is functional
in unauthenticated mode.
o Under load, the DCE$DCED process terminates with the following
*** FATAL ERROR at SOCKDISPATCH.C;1\3755 ***
%CMA-F-EXCCOP, exception raised; VMS condition code follows
SYSTEM-F-OPCCUS,opcode reserved to customer
fault at PC=00000000007043A8,
o The login context specific to application processes expires
immediately after starting ACMSxp TP system. The TP System
makes use of credentials obtained after a dce_login with
"acmsxp_svr" as the principal name.
Klist fails with the following error:
No DCE identity available: No currently established network
identity for which context exists (dce / sec)
o When a command procedure containing dce_login and ACMSxp
commands is executed in an infinite loop, the DCE$DCED process
aborts with a SYSTEM-F-ACCVIO error.
o DCE V3.0 RPC Only configuration fails on systems with TCPWARE
as the IP product. The configuration program terminates
o There was a case where a NULL pointer check was not being made
in RPC Runtime code. The new image takes care of this problem.
o When a call to rpc_binding_from_string_binding fails, the
subsequent calls to this function hang forever. The new RPC
Runtime library fixes the bug in
o When running DCOM applications between Windows 2000 and VMS
systems, several RPC_CN_CREATE_AUTH_INFO messages are logged
into the DCOM$RPCSS.OUT file leading to exhaustion of disk
space. This problem has now been resolved in the new image.
User will need to define a logical "DCE_DISABLE_LOGGING" to 1
either system or process wide for disabling the error messages.
$ DEFINE/SYSTEM/EXEC DCE_DISABLE_LOGGING 1
$ DEFINE DCE_DISABLE_LOGGING 1
o Failure to detect or ping an active Windows 2000 Client, while
running Authenticated DCOM between a Windows 2000 and OpenVMS
System, would cause the DCOM Server applications to timeout and
run down after a period of about 10 minutes.
Several "RPC_CN_AUTH_VFY_CLIENT_REQ" error messages appear in
DCOM$RPCSS.OUT file in intervals of 2 minutes.
2001-10-02-17:01:58.468-04:00I0.629 PID#330 ERROR rpc auth
CNSASSM.C;1 4654 0x01eb9740 RPC_CN_AUTH_VFY_CLIENT_REQ on
server failed: invalid handle (dce /rpc)
o The serviceability logging feature does not log the RPC
information into the log files, though it creates the file.
o RPC Fatal Exceptions are reported in DCOM$RPCSS.OUT when
running DCOM applications, from Windows 2000, after a new
DCOM$RPCSS process reports the following exception in the OUT
2002-04-18-15:04:17.604-04:00I0.113 PID#21370 FATAL rpc
(rpc_cn_network_receiver) Unexpected exception was raised
o DCE client example programs located in
[SYSHLP.EXAMPLES.DCE.RPC], generated using the IDL "-trace
log_manager" option, access violate. The access violation
occurs when the symbol RPC_LOG_FILE is defined.
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=000000000000 0000, PC=0000000000239F68, PS=0000001B
o According to the OSF documentation, when a user defined
authorization function returns false, the status value from the
user supplied function is to be returned to the client. The
RPC runtime always returns status "rpc_s_mgmt_op_disallowed"
when the user function returns false.
o Cannot configure and start an RPC only configuration on DCE
V3.0. Running uuidgen results in the error:
$ run sys$system:dce$uuidgen
%UUIDGEN-F-RPC_MESSAGE, Received Error Status: "no IEEE
802 hardware address"
o kdestroy does not delete the credential files at
o During startup, whenever a client application imports the
binding information from the name service database, using the
rpc call rpc_ns_binding_import_next( ), if there are less than
thirteen free event flags, the RPC call fails with the 'name
service unavailable' error.
No reboot is necessary after successful installation of the kit.
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
PRODUCT INSTALL VMS73_RPC /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 PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
All trademarks are the property of their respective owners.
Files on this server are as follows: