**************************** ECO SUMMARY INFORMATION **************************** Kit Name: DEC-AXPVMS-VMS732_RPC-V0400--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 9472 blocks Installation Rating: INSTALL_2 Required Features: COM, RPC, DCE All DCE Version 3.2-SSB Customers will need to install this kit Reboot Required: No Superseded Kits: VMS732_RPC-V0300 Mandatory Kit Dependencies: VMS732_UPDATE-V0300 VMS732_PCSI-V0100 Optional Kit Dependencies: None VMS732_RPC-V0400.PCSI-DCX_AXPEXE Checksum: 1301989980 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_RPC-V0400 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - COM, RPC, DCE - All DCE Version 3.2-SSB Customers will need to install this kit to receive all the updates made to RPC Runtime. This installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) 2.2 Reboot Requirement: No reboot is necessary after installation of this kit. See section 8.4 Special Installation Instructions for additional installation requirements. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.3-2 2.4 New functionality or new hardware support provided: Yes. 3 KITS SUPERSEDED BY THIS KIT: - VMS732_RPC-V0300 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0100 - VMS732_UPDATE-V0300 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 FILES PATCHED OR REPLACED: o [SYSEXE]DCE$ADD_ID.EXE (new image) Image Identification Information image name: "DCE$ADD_ID" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:10:01.45 linker identification: "A11-50" Overall Image Checksum: 639471769 o [SYSEXE]DCE$DCED.EXE (new image) Image Identification Information image name: "DCE$DCED" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:16:25.29 linker identification:"A11-50" Overall Image Checksum: 3696745781 o [SYSHLP.EXAMPLES.DCE.TOOLS]DCE$ETDEL.EXE (new image) Image Identification Information image name: "DCE$ETDEL" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:36.56 linker identification:"A11-50" Overall Image Checksum: 2671629274 Page 3 o [SYSHLP.EXAMPLES.DCE.TOOLS]DCE$ETDMP.EXE (new image) Image Identification Information image name: "DCE$ETDMP" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:37.25 linker identification: "A11-50" Overall Image Checksum: 1915298525 o [SYSHLP.EXAMPLES.DCE.TOOLS]DCE$ETFMT.EXE (new image) Image Identification Information image name: "DCE$ETFMT" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:37.91 linker identification:"A11-50" Overall Image Checksum: 2689759640 o [SYSHLP.EXAMPLES.DCE.TOOLS]DCE$ETGET.EXE (new image) Image Identification Information image name: "DCE$ETGET" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:38.57 linker identification: "A11-50" Overall Image Checksum: 85010364 o [SYSLIB]DCE$KERNEL.EXE (new image) Image Identification Information image name: "DCE$KERNEL" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:09:57.34 linker identification: "A11-50" Overall Image Checksum: 2691358144 o [SYSLIB]DCE$LIB_SHR.EXE (new image) Image Identification Information image name: "DCE$LIB_SHR" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:12:48.78 linker identification: "A11-50" Overall Image Checksum: 914630046 Page 4 o [SYSEXE]DCE$RPCCP.EXE (new image) Image Identification Information image name: "DCE$RPCCP" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:18:12.21 linker identification: "A11-50" Overall Image Checksum: 2608777926 o [SYSEXE]DCE$RPCPERF_CLIENT.EXE (new image) Image Identification Information image name: "DCE$RPCPERF_CLIENT" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:19:35.65 linker identification:"A11-50" Overall Image Checksum: 3644887574 o [SYSEXE]DCE$RPCPERF_SERVER.EXE (new image) Image Identification Information image name: "DCE$RPCPERF_SERVER" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:20:05.31 linker identification: "A11-50" Overall Image Checksum: 741535968 o [SYSMSG]DCE$RPC_MSG.EXE (new image) Image Identification Information image name: "DCE$RPC_MSG" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:09:56.96 linker identification: "A11-50" Overall Image Checksum: 2732761787 o [SYSLIB]DCE$SOCKSHR_DNET_IV.EXE (new image) Image Identification Information image name: "DCE$SOCKSHR_DNET_IV" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:29.63 linker identification: "A11-50" Overall Image Checksum: 853409841 Page 5 o [SYSLIB]DCE$SOCKSHR_DNET_OSI.EXE (new image) Image Identification Information image name: "DCE$SOCKSHR_DNET_OSI" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:18:46.36 linker identification: "A11-50" Overall Image Checksum: 4072192273 o [SYSLIB]DCE$SOCKSHR_IP.EXE (new image) Image Identification Information image name: "DCE$SOCKSHR_IP" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:32.33 linker identification: "A11-50" Overall Image Checksum: 2175749709 o [SYSLIB]DCE$SOCKSHR_TPS.EXE (new image) Image Identification Information image name: "DCE$SOCKSHR_TPS" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 18-SEP-2004 01:11:34.56 linker identification: "A11-50" Overall Image Checksum: 2319564122 o [SYSLIB]DTSS$SHR.EXE (new image) Image Identification Information image name: "DTSS$SHR" image file identification: "DCE V3.2-040917" image file build identification: "0060110012" link date/time: 29-OCT-2004 22:49:06.74 linker identification: "A11-50" Overall Image Checksum: 3771801815 o [SYSEXE]NTA$LOGON.EXE (new image) Image Identification Information image name: "NTA$LOGON" image file identification: "V1.0" image file build identification: "0060110011" link date/time: 27-APR-2004 06:30:23.10 linker identification: "A11-50" Overall Image Checksum: 708120495 Page 6 o [SYSMGR]DCE$RPC_SHUTDOWN.COM (new image) o [SYSMFR]DCE$RPC_STARTUP.COM (new image) o [SYSMGR]JPI.COM (new image) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_RPC-V0400 6.1 New functionality addressed in this kit 6.1.1 Support for IEEE_FLOAT Floating Point Type 6.1.1.1 Functionality Description: DCE RPC for OpenVMS now supports THE IEEE floating point type on Alpha platforms. The default floating-point type on Alpha platforms remains G_FLOAT. DCE RPC Application developers would need to use an rpc_set_local_float_drep call in their application to use the non-default floating point type. Please refer the release notes document of DCE V3.2 for more information on the usage of the call. Images Affected: - [SYSLIB]DCE$LIB_SHR.EXE 6.1.2 Support for tuning the buffer size of RPC Sockets 6.1.2.1 Functionality Description: The RPC runtime created sockets do not depend on the system specified socket buffer size values while setting the buffer quotas. They depend on the internally defined macros that set the buffer size to a default value of 4K bytes. RPC Runtime now provides support for tuning the socket buffer size by means of a logical RPC_USE_DEFAULT_SOCKET_BUFFER_SIZE. Setting the logical RPC_USE_DEFAULT_SOCKET_BUFFER_SIZE will allow RPC Runtime to make use of the system default socket buffer size values. The logical can be defined system wide as follows: $ DEFINE /SYSTEM RPC_USE_DEFAULT_SOCKET_BUFFER_SIZE 1 To restore the original RPC Runtime behavior the logical will need to be deassigned. Images Affected: - [SYSLIB]DCE$LIB_SHR.EXE Page 7 6.2 Problems addressed in this kit 6.2.1 UTC_VMSLOCALTIME does not return the correct time for AUS/WEST timezone 6.2.1.1 Problem Description: The DCE DTSS programming interface UTC_VMSLOCALTIME does not return the correct time for the Australia/West timezone. Images Affected: - [SYSLIB]DTSS$SHR.EXE 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) 70-10-1206 6.2.1.2.2 QAR(s) 75-15-1103 6.2.1.3 Problem Analysis: DCE DTSS was not able to set the time to standard time for those timezones without zone rule offsets. 6.2.1.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.1.5 Work-arounds: None. 6.2.2 DCE startup fails on systems with FAILSafe IP enabled 6.2.2.1 Problem Description: DCE startup fails while starting up DCED on OpenVMS systems where FAILSafe IP is enabled. An error similar to the following gets reported in the DCE$DCED.OUT. 2004-06-19-04:46:56.436+08:00I-- dced FATAL dhd general Page 8 MAIN.C;1 1502 0x7bbe4a78 Initialization (get bindings) failed, status=0x0e12815a Images Affected: - [SYSLIB]DCE$LIB_SHR.EXE 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-15-1095 6.2.2.3 Problem Analysis: On FAILsafe IP configured systems, the cause for the failure is DCE RPC's inability to recognize a network interface which does not have an IP address assigned to it. Whenever such a network interface is encountered, the "invalid network address" error is reported. This change allows DCE RPC to support FAILsafe IP environments. 6.2.2.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.2.5 Work-arounds: The logical RPC_UNSUPPORTED_NETIFS can be used to restrict DCE RPC's usage of interfaces that do not have assigned IP addresses in FAILsafe environments. 6.2.3 NTA$LOGON.DAT corruption when updating password 6.2.3.1 Problem Description: When a password change is requested via NTA$LOGON.EXE, the NTA$LOGON.DAT gets corrupted. Images Affected: Page 9 - [SYSEXE]NTA$LOGON.EXE 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) 70-73-35 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: When a password change is requested, the NTA$LOGON code pads 000's in between user records and at the end of file. This padding was being done incorrectly. It was creating a bad record, corrupting the file and keeping NTA from being able to read it. 6.2.3.4 Release Version of OpenVMS that will contain this change: V8.2 6.2.3.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS The VMS732_RPC-V0400 ECO kit includes all changes shipped in previous V7.3-2 RPC ECO kits. Issues addressed by these kits can be found in the following Release Notes files: o [SYSHLP]VMS732_RPC-V0100.RELEASE_NOTES o [SYSHLP]VMS732_RPC-V0200.RELEASE_NOTES o [SYSHLP]VMS732_RPC-V0300.RELEASE_NOTES 8 INSTALLATION INSTRUCTIONS Page 10 8.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_RPC-V0400.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 8.2 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 VMS732_RPC /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] 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. Page 11 8.3 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 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/SYS ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V4.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS732_RPC-V0400 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_RPC/PRODUCER=DEC/BASE=AXPVMS- /VER=V4.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit 8.4 Special Installation Instructions: A system re-boot is not necessary in order to use the new images supplied by this kit. However, the following steps must be taken after the installation completes: o Stop all applications that use DCE/RPC Page 12 o Shut down DCE/RPC via one of the following commands: - If you are running "RPC" only: $ @SYS$MANAGER:DCE$RPC_SHUTDOWN - If you are running DCE services: $ @SYS$MANAGER:DCE$SETUP CLEAN o Re-start DCE/RPC via one of the following commands: - If you were running "RPC" only: $ @SYS$MANAGER:DCE$RPC_STARTUP - If you were running DCE services: $ @SYS$MANAGER:DCE$SETUP START 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2005 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.