SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS VAXPRTS02_070 VAX V5.5-2 - V7.0 Print Symbiont ECO Summary

NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. *OpenVMS] VAXPRTS02_070 VAX V5.5-2 - V7.0 Print Symbiont ECO Summary Copyright (c) Digital Equipment Corporation 1995, 1996. All rights reserved. PRODUCT: OpenVMS VAX COMPONENT: Print Symbiont PRTSMB.EXE SMBSRVSHR.EXE SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: VAXPRTS02_070 ECO Kits Superseded by This ECO Kit: VAXPRTS01_070 VAXPRTS01_062 VAXPRTS01_061 VAXQMAN02_061 (VAXQMAN) VAXQMAN01_061 (CSCPAT_1176) VAXQMAN02_060 VAXQMAN01_060 (CSCPAT_1175) VAXQMAN8_U2055 VAXQMAN07_U2055 (CSCPAT_1165) VAXQMAN06_U2055 VAXQMAN05_U2055 VAXQMAN04_U2055 VAXQMAN03_U2055 QMAN$02_U2055 QMAN$01_U2055 ECO Kit Approximate Size: 791 Blocks Saveset A - 90 Blocks Saveset B - 108 Blocks Saveset C - 108 Blocks Saveset D - 162 Blocks Saveset E - 144 Blocks Saveset F - 144 Blocks Cover Letter - 35 Blocks Kit Applies To: OpenVMS VAX V5.5-2, V5.5-2H4, V5.5-2HF, V6.0, V6.1, V6.2, V7.0 System/Cluster Reboot Necessary: Yes Installation Rating: 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. NOTE: In order to receive the full fixes listed in this kit, the following remedial kits also need to be installed: None ECO KIT SUMMARY: An ECO kit exists for PRTSMB and SMBSRVSHR on OpenVMS VAX V5.5-2 - V7.0. This kit addresses the following problems: Problems Addressed in the VAXPRTS02_070 Kit for OpenVMS VAX V6.1, V6.2 and 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. Problems Addressed in the VAXPRTS01_070 Kit for OpenVMS VAX V6.1, V6.2: 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. Problems Addressed in the VAXPRTS01_070 Kit for OpenVMS VAX V6.1, V6.2, V7.0: o Symbiont processes may die with "SYSTEM-F-INSFMEM, insufficient dynamic memory". The problem has been observed under the following scenarios: - Restarting a large print job to begin printing at a specific page. For example: $ PRINT/PAGE=(90000,90001) A_BIG_PRINTOUT.LIS - UCX$TELNET symbiont process managing 16 queues with lots of print activity. - 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 Problems Addressed in the VAXPRTS01_062 Kit for OpenVMS VAX V5.5-2, V5.5-2H4, V6.0, V6.1, 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 Problems Addressed in the VAXPRTS01_061 Kit for OpenVMS VAX V5.5-2, V5.5-2H4, V6.0 and V6.1: o The superseded VAXQMAN kits contained both QMAN and PRTSMB ECOs. This VAXPRTS01_061 ECO kit supersedes only the PRTSMB portion of those previous kits. The QMAN ECOs have been separated into the VAXQMAN03_061 kit which only supersedes the QMAN portion of the superseded VAXQMAN kits. Problems Addressed in the VAXQMAN02_061 Kit for OpenVMS VAX V6.1, the VAXQMAN02_060 Kit for OpenVMS VAX V6.0 and in the VAXQMAN8_U2055 Kit for OpenVMS VAX V5.5-2: 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; or 2. A file printed with /PASSALL ends with a form feed. o PRTSMB or a user-modified symbiont may fail with an ACCVIO at PC=1A45c. This will cause the print job to hang. The hang occurs because the librarian routines (LBR$) are called from the AST level. o Page alignment may be lost in the following cases: 1. When the DCL Command 'START/QUEUE/SEARCH="text_string"' is used, the print job does not begin printing on the correct page. 2. If the DCL Command 'START/QUEUE/SEARCH="text_string"' is used to restart a paused queue, the print job is not re-started on the page that contains the search text. 3. The DCL Command 'START/QUEUE/BACKWARD=X' does not inherently resume the print job at the top-of-form. For example, if a paper jam occurs and the queue is stopped, then the queue is restarted with the 'START/QUEUE/BACKWARD=5' DCL command and the paper is at the top-of-form, the printout might begin with the last line of one page and continue with the next page on the same sheet of paper. o Zero length records in FORTRAN Carriage Control files are special cased by the symbiont. The special case logic does not emulate the behavior of the symbiont if the explicit carriage control character code for CR/LF was in the first record and causes an extra line feed to be printed at the top of the file. 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. Problems Addressed in the VAXQMAN01_061 Kit for OpenVMS VAX V6.1, the VAXQMAN01_060 Kit for OpenVMS VAX V6.0 and the VAXQMAN07_U2055 Kit for OpenVMS VAX V5.5-2: o When the printing of a FORTRAN CC file is resumed after a 'START/QUEUE' command is issued, the symbiont may crash and produce a .DMP file. o A WPS-formatted file may leave the symbiont in a state where printing a non-WPS file immediately afterwards will cause the vertical margins on the first page of the non-WPS file 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. o When a modified print symbiont contains a combination of a user-written input routine and a user-written format routine, memory leaks occur in the modified print symbiont. 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. This causes an extra form feed to appear. Problems Addressed in the VAXQMAN01_061 Kit for OpenVMS VAX V6.1 and in the VAXQMAN07_U2055 Kit for OpenVMS VAX V5.5-2: o If a file that contains an OSC escape sequence is printed on a LAT printer and the '/FORM' qualifier is used with the DCL 'PRINT' command, LATSYM may crash and cause the print job to hang. Problems Addressed in the VAXQMAN01_060 Kit for OpenVMS VAX V6.0 and in the VAXQMAN07_U2055 Kit for OpenVMS VAX V5.5-2: o If the first character of a file to be processed is a CR/FF (carriage return/form feed) combination, the output of the printer file may contain many pages of garbage before the expected output appears. Problems Addressed in the VAXQMAN01_060 Kit for OpenVMS VAX V6.0: o Attempts to print a file from a DFS-served disk results in a NOSUCHOBJECT error. Problems Addressed in the VAXQMAN06_U2055 Kit for OpenVMS VAX V5.5-2: o If a user-written or user-modified symbiont calls SMB$INITIALIZE or PSM$PRINT and uses an invalid maximum stream number, the Queue Manager may crash. INSTALLATION NOTES: In order for the corrections in this kit to take effect, the system must be rebooted. If the system is a member of a VMScluster, the entire cluster should be rebooted.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

vaxprts02_070.README
vaxprts02_070.CHKSUM
vaxprts02_070.CVRLET_TXT
vaxprts02_070.a-dcx_vaxexe
vaxprts02_070.b-dcx_vaxexe
vaxprts02_070.c-dcx_vaxexe
vaxprts02_070.d-dcx_vaxexe
vaxprts02_070.e-dcx_vaxexe
vaxprts02_070.f-dcx_vaxexe

privacy and legal statement