======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_JOBCTL-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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. 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: 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-V0800 Page 2 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 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_JOBCTL-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Job Control process aborts having exhausted its P0 Space 5.2.1.1 Problem Description: The Job Controller process aborts after running out of P0 space trying to handle a flood of incoming messages to check for process deletion. This is a very rare condition and is now being handled better by the Job Control process. This problem has been fixed. Images Affected: - [SYSEXE]JBC$JOB_CONTROL.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001140129 5.2.1.2.2 PTR(S) None 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 3 5.2.1.4 Work-arounds: None 5.2.2 Unable to login to system as Job Controller aborted during boot. 5.2.2.1 Problem Description: Job controller aborts during system boot as license database was located on a disk which was not mounted and this prevents logging onto the system. This problem has been fixed. Images Affected: - [SYSEXE]JBC$JOB_CONTROL.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001164783 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 5.2.3 Fall time change TQE is missing. 5.2.3.1 Problem Description: When nodes in a cluster are rebooted, intermittently the TQE for the spring or fall time change are missing from the JOB_CONTROL process. This problem has been fixed. Page 4 Images Affected: - [SYSEXE]JBC$JOB_CONTROL.EXE 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001126382 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: Restart the JOB controller. $STOP/ID= $@SYS$SYSTEM:STARTUP JOBCTL 5.2.4 Unable to update the device control library if library has been accessed by the queue. 5.2.4.1 Problem Description: The Device Control libraries used while printing, are opened by the first printing job. These remain open even after the job is complete and no modifications can be made to these libraries. The libraries are closed only after the queue is stopped. $ SHOW QUEUE / FULL Printer queue PRINTER1, idle, on KU2S4::"PRINTER1", mounted form DEFAULT /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /LIBRARY=PCL Lowercase /OWNER=[SYSTEM] /PROCESSOR=TCPIP$TELNETSYM /PROTECTION=(S:M,O:D,G:R,W:S) $ $ PRINT/QUEUE=PRINTER1/SETUP=PCL_LANDSCAPE HELLO.TXT Job HELLO (queue PRINTER1, entry 1) started on PRINTER1 $ $ SHOW QUEUE Printer queue PRINTER1, idle, on KU2S4::"PRINTER1", mounted form DEFAULT $ Page 5 $ SHOW ENTRY %JBC-E-NOSUCHENT, no such entry $ $ PIPE SHOW DEVICE SYS$SYSDEVICE/FILE | SEARCH SYS$PIPE PCL TCPIP$TNS1 000006BE [VMS$COMMON.SYSLIB]PCL.TLB;2 $ $ LIBRARY /INSERT SYS$LIBRARY:PCL.TLB TEST.TXT KU2S4::SYSTEM 17:12:12 LIBRARIAN CPU=00:00:00.46 PF=2624 IO=3261 MEM=365 %LIBRAR-F-OPENIN, error opening SYS$COMMON:[SYSLIB]PCL.TLB;2 as input -RMS-E-FLK, file currently locked by another user This problem has been fixed. Images Affected: - [SYSLIB]SMBSRVSHR.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001203836 5.2.4.2.2 PTR(S) 75-74-385 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers V8.4 5.2.4.4 Work-arounds: None 5.2.5 Incomplete informational message reported by the command DELETE/ENTRY/LOG 5.2.5.1 Problem Description: The informational message is incompletely displayed for the command DELETE/ENTRY/LOG when the entry number is greater than 7 digits. This problem has been fixed. Images Affected: Page 6 - [SYSEXE]QUEMAN.EXE 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1000893449 5.2.5.2.2 PTR(S) None 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.5.4 Work-arounds: None 6 FILES PATCHED OR REPLACED: o [SYSEXE]JBC$JOB_CONTROL.EXE (new image) Image Identification Information Image name: "JBC$JOB_CONTROL" Image file identification: "X-35" Image build identification: "0100000082" linker identification: "Linker I02-37" Link Date/Time: 3-AUG-2012 13:49:47.73 Overall Image Checksum: 16861EF4 o [SYSEXE]QUEMAN.EXE (new image) Image Identification Information Image name: "QUEMAN" Image file identification: "X02-01" Image build identification: "0100000102" linker identification: "Linker I02-37" Link Date/Time: 12-MAR-2013 11:33:18.74 Overall Image Checksum: 39279152 o [SYSLIB]SMBSRVSHR.EXE (new image) Image Identification Information Image name: "SMBSRVSHR" Page 7 Image file identification: "X-6" Image build identification: "0100000102" linker identification: "Linker I02-37" Link Date/Time: 12-MAR-2013 11:31:21.86 Overall Image Checksum: 45E34BD3 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. 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_JOBCTL-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_JOBCTL[/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 Page 8 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 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=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_JOBCTL-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! Page 9 $ PROD INSTALL VMS84I_JOBCTL/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2013 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.