SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
DCE-VMS VAXDCE02_014 DCE V1.4 for OpenVMS VAX ECO Summary

TITLE: DCE-VMS VAXDCE02_014 DCE V1.4 for OpenVMS VAX ECO Summary 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) Compaq Computer Corporation 1998. All rights reserved. PRODUCT: Distributed Computing Environment (DCE) For OpenVMS VAX OP/SYS: OpenVMS VAX SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VAXDCE02_014 ECO Kits Superseded by This ECO Kit: VAXDCE01_014 ECO Kit Approximate Size: 13415 Blocks Saveset A - 90 Blocks Saveset B - 13302 Blocks Cover Letter - 23 Blocks Kit Applies To: DCE V1.4 OpenVMS VAX V5.5-2, V5.5-2H4, V6.2 through V7.1 System/Cluster Reboot Necessary: No (See Installation Instructions) Installation Rating: 2 - To be installed on all systems running the listed versions of OpenVMS and using the following feature: This remedial kit contains many Year 2000 related fixes. Any customer running DCE must install this kit. ECO KIT SUMMARY: An ECO kit exists for DCE V1.4 on OpenVMS VAX V5.5-2, V5.5-2H4, V6.2 through V7.1. This kit addresses the following problems: PROBLEMS ADDRESSED IN VAXDCE02_014: o When a file required for an IDL compile was not located in the first location in a directory logical name search list, the IDL compile fails with: %IDL-E-OPENREAD, Unable to open idl_sources:[guy]test1.idl for read access %IDL-E-SYSERRMSG, System error message: no such file or directory %IDL-F-COMPABORT, Compilation aborted o User applications passing fixed arrays containing structures between Alpha VMSand other platforms encounter corruption in the array contents. o DCE Servers die with the following error messages: + Listening... (socket) rpc__socket_disp_select *** FATAL ERROR at SOCKDISPATCH.C;1\3668 ** %CMA-F-EXCCOP, exception raised; VMS condition code follows -SYSTEM-F-OPCCUS, opcode reserved to customer fault at PC=FFFFFFFF80538638,PS=000001B %SYSTEM-F-ABORT, abort o Configuring a OpenVMS DCE 1.4 client into a Gradient server running on NT4.0 results in the following error: Establishing security environment for principal "cell_admin" . . . **************************** ERROR **************************** *** An error occurred while setting up the security environment *** using principal name "cell_admin" Error: Cannot validate identity for principal "cell_admin" who are you failed (dce / rpc) 236094202 %SYSTEM-F-ABORT, abort PROBLEMS ADDRESSED IN VAXDCE01_014: o When the security server is not running, sec_login_refresh_identity() returns an undocumented status code, 336760967. The documentation states that the sec_rgy_server_unavailable status code should be returned. Example programs from OSF and other vendors show the refresh thread testing for the sec_rgy_server_unavailable status to determine if the refresh should be retried o Executing any RPCLM command results in a fault invalid bound message on Alpha systems. $RPCLM String Binding of Server:ncadg_ip_udp:16.32.80.42[2301] RPCLM> inq %CMA-F-EXCCOPLOS, exception raised; some information lost -DCERPC-E-FAULTINVALIDBOU, fault invalid bound (DCE / RPC) o In the directory DCE$SPECIFIC:[KRB5] there are hundreds of versions of KRB5KDC_RCACHE created in it by the DCE$SECD process. These files do get cleaned up during a CLEAN operation but, they are not cleaned up during a start or restart of DCE. o If you do not include prior to including the header will not compile because it uses the datatype FILE*. o Attempting a kinit on an OpenVMS system results in the error below: $ kinit cell_admin $5$dkb0:[sys0.syscommon.][sysexe]dce$kinit.exe;4: Malformed representation of principal when parsing name T@ o When an 'Illegal state transition' occurs, the correct state is not reported. The code clobbered the state before reporting it. A state of 255 is reported and is meaningless because it is the code for No State. o Print 4 digit years on output from DCE processes. Allow four digit data inputs from DCE administration functions. Fix leap year calculations for years after 2017. o It has been discovered that OSF/DCE has a potential problem in the security server that could allow for a denial of service attack. If a principal, group, or organization is greater than 1024 characters (including the cell name, so the actual name limit is less than 1024) when passed to security daemon (secd), it will cause secd core dump. The buffer is overrun causing memory corruption. In certain cases, the lookup attempt (or add or whatever) on the client will then rebind to another secd to make the request, eventually crashing all security daemons in the cell. o The new Pathway IP version can cause DCE setup to abort abruptly with error messages. Pathway changes the output of an image that returns the Pathway version. This causes output parsing routines to fail because they search for runtime on the line containing the version. INSTALLATION NOTES: Before installing the kit you must stop DCE by issuing the following command: @SYS$MANAGER:DCE$SETUP STOP NOCONF No reboot is necessary after successful installation of the kit. However, DCE must be re-started after the kit is installed to complete the installation of the new DCE images. DCE can be restarted with the comand @SYS$MANAGER:DCE$SETUP START



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

vaxdce02_014.README
vaxdce02_014.CHKSUM
vaxdce02_014.CVRLET_TXT
vaxdce02_014.a-dcx_vaxexe
vaxdce02_014.b-dcx_vaxexe

privacy and legal statement