======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_ACMELDAP-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: No reboot is necessary after installation of this kit. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Integrity V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0600 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None Page 2 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_ACMELDAP-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Wrong error message "acmekcv$cb_allocate_wqe_vm() failed" in ACME$SERVER.LOG file for ACME LDAP users 5.2.1.1 Problem Description: When a ACME LDAP user tries to login to a system with blank password, an error message is displayed on his terminal: "Operation failure; if logging is enabled, see details in the ACME$SERVER log file". The ACME$SERVER.LOG has the below entry: ACME_-I-TRACE, MESSAGE FROM THE MESSAGE FILE: acmekcv$cb_allocate_wqe_vm() failed. The behavior is changed to provide an authentication failure message on the user terminal instead of logging the message "acmekcv$cb_allocate_wqe_vm() failed" in acme$server.log. Images Affected: - [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001182768, QXCM1001191113 QXCM1001206178, QXCM1001205941 5.2.1.2.2 PTR(s) None. Page 3 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.1.4 Work-arounds: None. 5.2.2 Documentation changes 5.2.2.1 Problem Description: Documentation changes have been done to reflect the changes in steps of setting up of the ACME login framework. Images Affected: - [SYSHLP]ACME_DEV_README.TXT - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT - [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases None. 5.2.2.2.2 PTR(s) None. 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.2.4 Work-arounds: None. Page 4 5.2.3 ACME_SERVER process crashes sometimes when Multinet stack is used and Virtual terminals (VTA) are enabled 5.2.3.1 Problem Description: ACME_SERVER process crashes sometimes when Multinet stack is used and virtual terminals (VTA) are enabled on the system. The terminal device will not have the TT_PHYDEVNAM information which is accessed by VMS ACME agent, thus resulting in the crash. With the fix, the VMS ACME agent uses the virtual terminal name if the TT_PHYDEVNAM is not available. Customer will also see the below error, when TT_PHYDEVNAM information is not available: - Could not get Physical terminal name - GETDVI on DVI_TT_PHYDEVNAM - The virtual terminal name gets printed in second set of logs Images Affected: - [SYSLIB]VMS$VMS_ACMESHR.EXE 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001206178 5.2.3.2.2 PTR(s) None. 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.3.4 Work-arounds: None. 5.2.4 ACME logins hang Page 5 5.2.4.1 Problem Description: In an ACME (SYS$ACM enabled) login environment,the logins were not going through and timeout errors were received by users.Also,the ACME_SERVER process seemed to be hung. The below error were logged in the ACME$SERVER.LOG file 1.) -LOGIN-S-PROCSTEP, Processing Step was FINISH_PROCESSING_CALL_UAI_MODIFY -LOGIN-S-SUBPROGRAM, subprogram SYSUAISRV.MODIFY returned the error: -UAF-I-NOMODS, no modifications made to system authorization file 2.) -LOGIN-S-PROCSTEP, Processing Step was READ_UAI_CALLED_UAI_READ -LOGIN-S-SUBPROGRAM, subprogram SYSUAISRV.READ_RESULTS for user data supporting FINISH_PROCESSING_READ_UAI returned the error: -RMS-W-TMO, timeout period expired This problem has been fixed. Images Affected: - [SYSLIB]VMS$VMS_ACMESHR.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001216860 5.2.4.2.2 PTR(s) None. 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.4.4 Work-arounds: None. Page 6 6 FILES PATCHED OR REPLACED: o [SYSLIB]VMS$VMS_ACMESHR.EXE (new image) Image Identification Information image name: "VMS$VMS_ACMESHR" image file identification: "V1.0" image file build identification: "0100000084" link date/time: 4-SEP-2012 13:57:51.01 linker identification: "Linker I02-38" Overall Image Checksum: 8FD682C0 o [SYSLIB]LDAPACME$LDAP-STD_ACMESHR.EXE (new image) Image Identification Information Image name: "LDAPACME$LDAP-STD_ACMESHR" Image file identification: "LDAP-STD V01.05" Image file build identification: "0100000076" linker identification: "Linker I02-37" Link Date/Time: 11-JUN-2012 18:06:06.96 Overall Image Checksum: AD1BBD12 o [SYSHLP]ACME_DEV_README.TXT (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.TXT (new file) o [SYSHLP]ACMELDAP_STD_CONFIG_INSTALL.PDF (new file) 7 INSTALLATION INSTRUCTIONS 7.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. Page 7 o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.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 VMS84I_ACMELDAP-V0100.ZIPEXE 7.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 VMS84I_ACMELDAP[/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 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. 7.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 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 Page 8 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=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_ACMELDAP-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_ACMELDAP/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2012 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, Page 9 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.