======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_SORT32-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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: Yes. 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-V0500 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_SORT32-V0100 KIT 5.1 New functionality addressed in this kit 5.1.1 Convert/sort command on Huge files (>10GB) terminates with INSVIRMEM errors. 5.1.1.1 Problem Description: When huge files are involved in sort operation, there might be scenarios where the memory gets exhausted. To resolve this, the upper bound on the maximum possible value that SORT can utilize was doubled. This new upper bound will only be used in cases where the previous value would have been exceeded (i.e. on very large sorts). In few scenarios, the INSVIRMEM errors could be avoided by increasing the value of PGFLQUOTA(PQL_DPGFLQUOTA, PQL_MPGFLQUOTA) using SYSGEN such that the ratio between PGFLQUOTA and WSEXTENT is maintained as 3:1. If the user still notices fatal INSVIRMEM error messages, it is because of SORT having inherent limitation of not utilizing the P2 space for its operation. When using SORT command, this can be worked around by splitting the files and sorting them thereby generating a reordered output file. Images Affected: - [SYSLIB]SORTSHR.EXE 5.1.1.2 Quix and PTR cases reporting this problem: 5.1.1.2.1 Quix Cases QXCM1001157779 5.1.1.2.2 PTR(s) 75-126-225 5.1.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 3 5.1.1.4 Work-arounds: None. 5.2 Problems addressed in this kit 5.2.1 While converting large database files using convert/sort command, the convert operation is terminating with INSVIRMEM errors generated from SORT utility. 5.2.1.1 Problem Description: SORT has not been designed to utilize P2 space for its operation. Thereby when huge files are involved in sort operation, there are very good chances that memory gets exhausted. For a performance fix, an upper bound was set on the maximum number of pages that are made SORT has not been designed to utilize P2 space for its operation. Thereby when huge files are involved in sort operation, there are very good chances that memory gets exhausted. For a performance fix, an upper bound was set on the maximum number of pages that are made available for sort operation. In the current case, the upper bound value was insufficient to complete the SORT operation. Hence the SORT generated INSVIRMEM errors. By increasing the upper bound value, the convert/sort operation completed successfully even with some intermediate INSVIRMEM warnings. Images Affected: - [SYSLIB]SORTSHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001157779 5.2.1.2.2 PTR(s) 75-126-225 Page 4 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. 6 FILES PATCHED OR REPLACED: o [SYSLIB]SORTSHR.EXE (new image) Image Identification Information Image name: "SORTSHR" Image file identification: "V08-013" Image build identification: "0100000077" linker identification: "Linker I02-37" Link Date/Time: 18-JUN-2012 13:58:52.15 Overall Image Checksum: 2260F754 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. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. Page 5 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_SORT32-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_SORT32[/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 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 Page 6 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_SORT32-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_SORT32/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, 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.