ECO NUMBER: ALPPRTS02_070 ----------- PRODUCT: OpenVMS Alpha Operating System -------- UPDATED PRODUCT: OpenVMS Alpha Operating System 7.0 ---------------- APPRX BLCK SIZE: 1426 ---------------- COVER LETTER 1 KIT NAME: ALPPRTS02_070 2 KITS SUPERSEDED BY THIS KIT: ALPPRTS01_070 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, V7.0 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced for OpenVMS V6.1, V6.1-1H1, V6.1-1H2 o [SYSEXE]PRTSMB.EXE (new image) o [SYSLIB]SMBSRVSHR.EXE (new image) 3.4 Files patched or replaced for OpenVMS V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 o [SYSLIB]SMBSRVSHR.EXE (new image) 3.5 Files patched or replaced for OpenVMS V7.0 o [SYSLIB]SMBSRVSHR.EXE (new image) -- COVER LETTER -- Page 2 2 December 1996 4 PROBLEMS ADDRESSED IN ALPPRTS02_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3, V7.0 o A file which contains a form feed code at the end of the record, prints in unexpected format. The format of the following page is destroyed. o User modified symbionts using the LAT protocol and a user work area, terminate with %SYSTEM-F-ABORT when a print job is queued. o On OpenVMS Version 7.0 or higher, printing a VFC file on either PRTSYM or LATSYM, gives an invalid prefix control character, even though the prefix control character is a valid "C0" control character. On OpenVMS Version 6.2 or lower, when printing a VFC file on either PRTSYM or LATSYM, the process goes into 100% CPU utilization. 5 PROBLEMS ADDRESSED IN ALPPRTS01_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2 o Use of the /DISABLE_AUTOSTART option in the SYSMAN SHUTDOWN NODE command results in an infinite loop. o Users with READALL priv, who do not otherwise have read access to a file, cannot successfully print the file. They are able to copy or type the same file. o When a print request encounters a security violation on an input file at the time of printing, the symbiont does not close the file. The symbiont signals the error: Job X (queue COLA, entry 3) terminated with error status %PSM-E-OPENIN, error opening !AS as input but the input file does not get closed. 6 PROBLEMS ADDRESSED IN ALPPRTS01_070 KIT FOR OPENVMS ALPHA V6.1, V6.1-1H1, V6.1-1H2, V6.2, V6.2-1H1, V6.2-1H2, V7.0 o Symbiont processes may die with insufficient dynamic memory. The problem has been observed under the following scenarios: o Restarting a large print job to begin printing at a specific page. For example: $ PRINT/PAGE=(90000,90001) A_BIG_PRINTOUT.LIS -- COVER LETTER -- Page 3 2 December 1996 o UCX$TELNET symbiont process managing 16 queues with lots of print activity. o Batch/Print high speed test symbionts running with 16-32 queues. When the symbiont process dies the following message is broadcast to the operator console and written to the OPERATOR.LOG file. %%%%%%%%%%% OPCOM 22-FEB-1996 08:08:14.18 %%%%%%%%%%% $!Message from user QUEUE_MANAGE on QMUNGR $!%QMAN-E-SYMDEL, unexpected symbiont process termination *************** $!%%%%%%%%%%% OPCOM 22-FEB-1996 08:08:14.18 %%%%%%%%%%% $!Message from user QUEUE_MANAGE on QMUNGR $!-SYSTEM-F-INSFMEM, insufficient dynamic memory 7 PROBLEMS ADDRESSED IN ALPPRTS01_062 KIT FOR OPENVMS V6.1, V6.1-1H1, V6.1-1H2, V6.2 o LATSYM loops infinitely on queues with RESET modules that do form feeds. The common symptoms are: - Queue printing a file forever - Queue stuck in starting state - STOP/QUEUE fails to pause queue - LATSYM symbiont processes looping o Files printed to a LN03 device are corrupted, usually with the first page margins incorrect. 8 PROBLEMS ADDRESSED IN AXPPRTS02_061 KIT o The AXPJOBC01_061 kit contained both QMAN and PRTSMB ECOs. The AXPQMAN03_061 kit supersedes only the QMAN portion of the AXPJOBC01_061 kit. The PRTSMB ECOs have been separated into the AXPPRTS02_061 kit. The AXPPRTS02_061 supersedes the PRTSMB portion of the AXPJOBC01_061 kit. -- COVER LETTER -- Page 4 2 December 1996 9 PROBLEMS ADDRESSED IN AXPQMAN01_061 KIT o If a queue is set up with a form other than the default form, and a job is printed using PAGE_SETUP, the printer will continually spew out paper with only the output from the page setup module. This continues until the entry is deleted from the queue. o START/QUEUE/SEARCH="text_string" does not start the print job on the correct page. Also, when restarting a paused print queue with START/QUEUE/SEARCH="text_string", the print job is not restarted on the page that contains the search text. Rather, the print job starts with a couple of lines prior to the actual page containing the text. START/QUEUE/BACKWARD=X does not resume printing at top of form. For example, if a paper jam occurs and the queue is stopped and started with a /BACKWARD=5 with the paper sitting at top of form then the printout will start with the last line of a page and continue with the expected page. This misallignment will continue for the rest of the printout. o PRTSMB or a user modified symbiont can fail with an ACCVIO PC = 1A45c causing the print job to hang. o In the following cases, the print symbiont prints an unwanted form feed after a print job: 1. Output ends exactly at the end of the page 2. File printed with /PASSALL ends with a form feed o When printing a file with the /FORM qualifier on a LAT printer it's possible for the LATSYM to dump. This was shown with a file that contained an OSC escape sequence and had a WIDTH of 255. o When a paused or stopped queue, which was printing a FORTRAN carriage control file, is restarted with the /TOP_OF_FILE qualifier, extraneous formatting characters may be sent to the printer device. o When a modified print symbiont contains a combination of a user written input routine and a user written format routine, then memory leaks occur in the modified print symbiont. o A WPS formatted file may leave the symbiont in a state where printing a non-WPS file directly afterwards will cause the vertical margins on the first page to be incorrect. This only happens if a top margin is defined for the non-WPS file's form and no flag page is produced between jobs. -- COVER LETTER -- Page 5 2 December 1996 o After a START/QUEUE, when resuming the printing of a FORTRAN CC file, a symbiont may crash producing a .DMP file o With latest print symbiont, All-IN-1 users may experience a blank page between each job 10 PROBLEMS ADDRESSED IN AXPPRTS01_061 KIT o When starting a LAT queue, the symbiont process may crash, leaving the queue in a stopped state and causing a process dump (SYS$SYSTEM:LATSYM.DMP). 11 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 3 : To be installed by customers experiencing the problems corrected. 12 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPPRTS02_070 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). Copyright (c) Digital Equipment Corporation, 1996 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. -- COVER LETTER -- Page 6 2 December 1996 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 DIGITAL 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.