**************************** ECO SUMMARY INFORMATION **************************** Release Date: 5-JUN-2007 Kit Name: DEC-AXPVMS-VMS83A_UPDATE-V0300--4.PCSI$COMPRESSED;2 Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 34358 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS83A_UPDATE-V0200 Mandatory Kit Dependencies: None or later Optional Kit Dependencies: None Checksums: VMS83A_UPDATE-V0300.ZIPEXE Checksum: 2960709448 DEC-AXPVMS-VMS83A_UPDATE-V0300--4.PCSI$COMPRESSED;2 Checksum: 934741158 VMS83A_UPDATE-V0300.ZIPEXE MD5 Checksum: 9C99C97167F04E6D02ACC4DDED68F60D DEC-AXPVMS-VMS83A_UPDATE-V0300--4.PCSI$COMPRESSED;2 MD5 Checksum: 155D4260286D38361AA522568CEAD23A ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_UPDATE-V0300 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. 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: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. In addition to the reboot, some kits that have been included in the VMS83A_UPDATE-V0300 kit have specific steps that must be performed before or after the installation of the VMS83A_UPDATE-V0300 patch kit. Refer to section 7.5 "Special Installation Instructions" for any such requirements BEFORE attempting to install the VMS83A_UPDATE-V0300 patch kit. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V8.3 2.4 New functionality or new hardware support provided: Yes. See the following files for more information: o [SYSHLP]VMS83A_ACMELDAP-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_TZ-V0100.RELEASE_NOTES Page 2 3 KITS SUPERSEDED BY THIS KIT: - VMS83A_UPDATE-V0200 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - None 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 CONSOLIDATION OF PREVIOUSLY RELEASED PATCH KITS FOR OPENVMS ALPHA V8.3. The VMS83A_UPDATE-V0300 kit is a consolidation of previously released patch kits for OpenVMS Alpha V8.3. The kits included in the VMS83A_UPDATE-V0300 kit are: o VMS83A_ACMELDAP-V0200 o VMS83A_ACRTL-V0100 o VMS83A_ADDENDUM-V0200 o VMS83A_BACKUP-V0200 o VMS83A_ERRFMT-V0100 o VMS83A_LAN-V0100 o VMS83A_MQ-V0100 o VMS83A_RMS-V0200 o VMS83A_SECSRV-V0100 o VMS83A_TZ-V0100 o VMS83A_XFC-V0100 Note that OpenVMS Patch kits are cumulative and that they contain all changes that have been released in earlier versions of the kit. Page 3 The issues addressed by these kits can be found in the following Release Notes files after the kit is installed: o [SYSHLP]VMS83A_ACMELDAP-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_ACMELDAP-V0200.RELEASE_NOTES o [SYSHLP]VMS83A_ACRTL-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_ADDENDUM-V0200.RELEASE_NOTES o [SYSHLP]VMS83A_ADDENDUM-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_BACKUP-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_BACKUP-V0200.RELEASE_NOTES o [SYSHLP]VMS83A_ERRFMT-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_LAN-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_MQ-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_RMS-V0200.RELEASE_NOTES o [SYSHLP]VMS83A_RMS-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_SECSRV-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_TZ-V0100.RELEASE_NOTES o [SYSHLP]VMS83A_XFC-V0100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS83A_UPDATE/VERSION=3.0- /DESTINATION=destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS83A_UPDATE/VERSION=3.0 - /SELECT=file_name/DESTINATION=destination_directory 6 FILES PATCHED OR REPLACED: o [SYS$LDR]ACME.EXE (new image) Image Identification Information [SYSHLP] Page 4 image name: "ACME" image file identification: "X-5" image file build identification: "XBCA-0080070018" link date/time: 3-JAN-2007 09:47:58.43 linker identification: "A13-03" Overall Image Checksum: 2823333793 o [SYSEXE]ACME_SERVER.EXE (new image) Image Identification Information image name: "ACME_SERVER" image file identification: "X-42" image file build identification: "XBCA-0080070002" link date/time: 21-NOV-2006 10:12:58.09 linker identification: "A13-03" Overall Image Checksum: 480770781 o [SYSEXE]ANALYZRMS.EXE (new image) Image Identification Information image name: "ANALYZRMS" image file identification: "X-11" image file build identification: "XBCA-0080070000" link date/time: 11-SEP-2006 14:59:19.35 linker identification: "A13-03" Overall Image Checksum: 2791810061 o [SYSEXE]AUDIT_SERVER.EXE (new image) Image Identification Information image name: "AUDIT_SERVER" image file identification: "X-12" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:40.79 linker identification: "A13-03" Overall Image Checksum: 3194053560 o [SYSEXE]BACKUP.EXE (new image) Image Identification Information image name: "BACKUP" image file identification: "V8.3" image file build identification: "XBCA-0080070002" link date/time: 11-SEP-2006 14:59:19.68 linker identification: "A13-03" Overall Image Checksum: 4151286267 o [SYSLIB]BACKUPSHR.EXE (new image) Image Identification Information image name: "BACKUPSHR" image file identification: "V8.3" Page 5 image file build identification: "XBCA-0080070002" link date/time: 11-SEP-2006 14:58:36.17 linker identification: "A13-03" Overall Image Checksum: 3328667864 o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information image name: "DECC$SHR" image file identification: "V8.2-01" image file build identification: "XBCA-0080070002" link date/time: 1-NOV-2006 10:50:58.41 linker identification: "A13-03" Overall Image Checksum: 3078199418 o [SYSLIB]DECC$SHR_EV56.EXE (new image) Image Identification Information image name: "DECC$SHR_EV56" image file identification: "V8.2-01" image file build identification: "XBCA-0080070002" link date/time: 1-NOV-2006 10:51:06.18 linker identification: "A13-03" Overall Image Checksum: 80475638 o [SYSEXE]EDF.EXE (new image) Image Identification Information image name: "EDF" image file identification: "X-07" image file build identification: "XBCA-0080070000"" link date/time: 20-OCT-2006 11:55:49.64 linker identification: "A13-03" o [SYSEXE]ERRFMT.EXE (new image) Image Identification Information image name: "ERRFMT" image file identification: "X-19" image file build identification: "XBCA-0080070001" link date/time: 8-NOV-2006 16:12:38.80 linker identification: "A13-03" Overall Image Checksum: 3156178145 o [SYS$LDR]IO_ROUTINES.EXE (new image) Image Identification Information image name: "IO_ROUTINES" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:29.20 linker identification: "A13-03" Overall Image Checksum: 2222556394 Page 6 o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) Image Identification Information image name: "IO_ROUTINES_MON" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:31.30 linker identification: "A13-03" Overall Image Checksum: 2698973810 o [SYSLIB]LAN$SDA.EXE (new image) Image Identification Information image name: "LAN$SDA" image file identification: "X-44" image file build identification: " 0080070007" link date/time: 15-NOV-2006 13:59:04.01 linker identification: "A13-03" Overall Image Checksum: 3321472708 o [SYSEXE]LANACP.EXE (new image) Image Identification Information image name: "LANACP" image file identification: "X-52" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:58.20 linker identification: "A13-03" Overall Image Checksum: 1661583049 o [SYSEXE]LANCP.EXE (new image) Image Identification Information image name: "LANCP" image file identification: "X-83A1" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:57.97 linker identification: "A13-03" Overall Image Checksum: 1150978786 o [SYSLIB]LDAP$SHR.EXE (new image) Image Identification Information image name: "LDAP$SHR" image file identification: "LDAP V2.0-05000" image file build identification: "XBCA-0080070000" link date/time: 8-NOV-2006 16:12:06.42 linker identification: "A13-03" Overall Image Checksum: 951171002 Page 7 o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:47:41.59 linker identification: "A13-03" Overall Image Checksum: 1514753709 o [SYSEXE]MONITOR.EXE (new image) Image Identification Information image name: "MONITOR" image file identification: "X-26" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:57.62 linker identification: "A13-03" Overall Image Checksum: 3914726037 o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT" image file identification: "X-5" image file build identification: "XBCA-0080070024" link date/time: 13-FEB-2007 08:49:37.30 linker identification: "A13-03" Overall Image Checksum: 400481989 o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) Image Identification Information image name: "PROCESS_MANAGEMENT_MON" image file identification: "X-5" image file build identification: "XBCA-0080070024" link date/time: 13-FEB-2007 08:49:38.68 linker identification: "A13-03" Overall Image Checksum: 2514094830 o [SYS$LDR]RMS.EXE (new image) Image Identification Information image name: "RMS" image file identification: "X-47" image file build identification: "XBCA-0080070007" link date/time: 7-FEB-2007 13:33:46.67 linker identification: "A13-03" Overall Image Checksum: 1517205937 Page 8 o [SYSEXE]RMSREC$SERVER.EXE (new image) Image Identification Information image name: "RMSREC$SERVER" image file identification: "X-13" image file build identification: "XBCA-0080070000" link date/time: 21-FEB-2007 15:38:11.74 linker identification: "A13-03" o [SYSLIB]SDARMS$SHARE.EXE (new image) Image Identification Information image name: "SDARMS$SHARE" image file identification: "X-13" image file build identification: "XBCA-0080070007" link date/time: 7-FEB-2007 13:33:47.68 linker identification: "A13-03" Overall Image Checksum: 4015830445 o [SYSLIB]SECURESHRP.EXE (new image) Image Identification Information image name: "SECURESHRP" image file identification: "X-8" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:47:50.15 linker identification: "A13-03" Overall Image Checksum: 3299818619 o [SYSEXE]SECURITY_SERVER.EXE (new image) Image Identification Information image name: "SECURITY_SERVER" image file identification: "01" image file build identification: "XBCA-0080070000" link date/time: 11-SEP-2006 15:00:18.95 linker identification: "A13-03" Overall Image Checksum: 3290586404 o [SYSEXE]SETSHOSERVER.EXE (new image) Image Identification Information image name: "SETSHOSERVER" image file identification: "X-2" image file build identification: "XBCA-0080070005" link date/time: 12-DEC-2006 10:19:37.11 linker identification: "A13-03" Overall Image Checksum: 825224115 o [SYSLIB]SPISHR.EXE (new image) Image Identification Information Page 9 image name: "SPISHR" image file identification: "ALPHA XBCA-N2O" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:49.78 linker identification: "A13-03" Overall Image Checksum: 3881418943 o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-5" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:50:00.32 linker identification: "A13-03" Overall Image Checksum: 4197445520 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-5" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:50:02.12 linker identification: "A13-03" Overall Image Checksum: 3665832722 o [SYS$LDR]SYS$EI1000.EXE (new image) Image Identification Information image name: "SYS$EI1000" image file identification: "X-24" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:01.15 linker identification: "A13-03" Overall Image Checksum: 3602879448 o [SYS$LDR]SYS$EW1000A.EXE (new image) Image Identification Information image name: "SYS$EW1000A" image file identification: "X-64" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:59.80 linker identification: "A13-03" Overall Image Checksum: 2290813298 o [SYS$LDR]SYS$EW5700.EXE (new image) Image Identification Information image name: "SYS$EW5700" Page 10 image file identification: "X-61" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:00.52 linker identification: "A13-03" Overall Image Checksum: 4248753802 o [SYS$LDR]SYS$EWXFRAME.EXE (new image) Image Identification Information image name: "SYS$EWXFRAME" image file identification: "X-18" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:02.17 linker identification: "A13-03" Overall Image Checksum: 1533687700 o [SYS$LDR]SYS$LAN_CSMACD.EXE (new image) Image Identification Information image name: "SYS$LAN_CSMACD" image file identification: "X-9" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:58:38.75 linker identification: "A13-03" Overall Image Checksum: 575030692 o [SYS$LDR]SYS$LLDRIVER.EXE (new image) Image Identification Information image name: "SYS$LLDRIVER" image file identification: "X-23" image file build identification: "XBCA-0080070007" link date/time: 15-NOV-2006 13:59:02.69 linker identification: "A13-03" Overall Image Checksum: 842429645 o [SYS$LDR]SYS$PEDRIVER.EXE (new image) Image Identification Information image name: "SYS$PEDRIVER" image file identification: "X-4" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:49:54.68 linker identification: "A13-03" Overall Image Checksum: 2641392456 o [SYS$LDR]SYS$VLANDRIVER.EXE (new image) Image Identification Information image name: "SYS$VLANDRIVER" image file identification: "X-14" image file build identification: "XBCA-0080070007" Page 11 link date/time: 15-NOV-2006 13:58:55.82 linker identification: "A13-03" Overall Image Checksum: 64235250 o [SYSMSG]SYSMGTMSG.EXE (new image) Image Identification Information image name: "SYSMGTMSG" image file identification: "X-4" image file build identification: "XBCA-0080070008" link date/time: 18-SEP-2006 14:15:37.54 linker identification: "A13-03" Overall Image Checksum: 1376464696 o [SYS$LDR]SYS$VM.EXE (new image) Image Identification Information image name: "SYS$VM" image file identification: "X-5" image file build identification: "XBCA-0080070003" link date/time: 11-SEP-2006 14:59:30.87 linker identification: "A13-03" Overall Image Checksum: 4233182520 o [SYS$LDR]SYS$XFCACHE.EXE (new image) Image Identification Information image name: "SYS$XFCACHE" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:33.37 linker identification: "A13-03" Overall Image Checksum: 1640148127 o [SYS$LDR]SYS$XFCACHE_MON.EXE (new image) Image Identification Information image name: "SYS$XFCACHE_MON" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:35.59 linker identification: "A13-03" Overall Image Checksum: 947787436 o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:49.10 linker identification: "A13-03" Page 12 Overall Image Checksum: 85166119 o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) Image Identification Information image name: "SYSTEM_PRIMITIVES_MIN" image file identification: "X-5" image file build identification: "XBCA-0080070027" link date/time: 7-MAR-2007 14:58:50.16 linker identification: "A13-03" Overall Image Checksum: 396578336 o [SYSLIB]TRACE.EXE (new image) Image Identification Information image name: "TRACE" image file identification: "V8.3-002" image file build identification: "XBCA-0080070000" link date/time: 7-AUG-2006 17:48:41.56 linker identification: "A13-03" Overall Image Checksum: 612648440 o [SYSLIB]VMS$VMS_ACMESHR.EXE (new image) Image Identification Information image name: "VMS$VMS_ACMESHR" image file identification: "01" image file build identification: " 0080070002" link date/time: 27-SEP-2006 16:27:18.13 linker identification: "A13-03" Overall Image Checksum: 2256325941 o [SYSLIB]XFC$SDA.EXE (new image) Image Identification Information image name: "XFC$SDA" image file identification: "V1.0" image file build identification: "XBCA-0080070003" link date/time: 7-MAR-2007 14:58:36.60 linker identification: "A13-03" Overall Image Checksum: 3412882693 o [SYSLIB]XX$SDA.EXE (new image) Image Identification Information image name: "XX$SDA" image file identification: "X-3" image file build identification: " 0080070007" link date/time: 15-NOV-2006 13:59:03.85 linker identification: "A13-03" Overall Image Checksum: 1752586015 Page 13 o [SYSUPD]ACME_DEV_KITS.BCK (new file) o [SYSHLP]ACME_DEV_README.TXT (new file) o [SYSUPD]BACKUP.CLD (new file) o [SYSLIB]DECC$RTLDEF.TLB o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) o [SYSLIB]LIBRTL.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]RMSDEF.STB (new file) o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) o [SYS$LDR]SYS$PEDRIVER.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYS$XFCACHE.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) o [SYS$ZONEINFO.SYSTEM]YEARISTYPE.COM (new file) o All [SYS$ZONEINFO.SYSTEM] timezone files. 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: Page 14 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. 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI$COMPRESSED file, run the file with the following command: $ RUN VMS83A_UPDATE-V0300.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 VMS83A_UPDATE /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. 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 Page 15 o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT 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 o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=HP/BASE=AXPVMS/VER=V3.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS83A_UPDATE-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_UPDATE/PRODUCER=HP /BASE=AXPVMS- /VER=V3.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 7.5 Special Installation Instructions: The following kits that are included in this UPDATE kit require additional actions to be taken either before or after the installation of the VMS83A_UPDATE-V0300 patch kit: o VMS83A_ACMELDAP-V0100 - To complete the installation process and configure the LDAP external authentication agent, you must install the V83_ACMELOGIN and V83_ACMELDAP_STD kits found in the SYS$UPDATE:ACME_DEV_KITS.BCK saveset. Please refer to SYS$HELP:ACME_DEV_README.TXT for more details. - Due to a small memory leak in one of the API libraries used by the LDAP ACME agent, the ACME_SERVER process will slowly consume its page file quota. The ACME_SERVER will detect Page 16 when its page file quota reaches 20% and will automatically restart. This will occur after approximately 55,000 LDAP authentications. o VMS83A_TZ-V0100 - After kit installation completes you must execute one of the following commands in order to update the logical SYS$TIMEZONE_RULE: If you are using DTSS (Distributed Time Synchronization Service), execute the command: $ @NET$CONFIGURE.COM If you are not using DTSS, execute the command: $ @UTC$TIME_SETUP.COM - The following instructions apply to users who have set the time zone to GMT-* or GMTPLUS* : The definition of the timezone names has been changed in the time-zone public database (ftp://elsie.nci.nih.gov/pub/). The effect of this change is that, after installation of the VMS83A_TZ-V0100 kit, "GMT-" (minus) will now mean "ahead (east) of" Greenwich Mean Time (GMT) and "GMTPLUS" will now mean "behind (west) of" GMT. For example, GMT-1 will mean one hour ahead (east) of GMT and the Time Differential Factor (SYS$TIMEZONE_DIFFERENTIAL) will be set to "3600". GMTPLUS1 will mean one hour behind (west) of GMT and the SYS$TIMEZONE_DIFFERENTIAL will be set to "-3600". This is the opposite meaning of what you are used to. In order to correct for this, after installation of this kit, users must run the SYS$MANAGER:UTC$TIME_SETUP.COM command file and set the timezone to the opposite of what was originally set. For example, if you had previously set the timezone to GMTPLUS*, you must now set the timezone to GMT-* to account for the timezone definition changes. For usage of UTC$TIME_SETUP.COM, see the HP OpenVMS System Manager's Manual. 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Page 17 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.