OpenVMS ALPPRTS02_070 Alpha V6.1-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] ALPPRTS02_070 Alpha V6.1-V7.0 Print Symbiont ECO Summary
Copyright (c) Digital Equipment Corporation 1995, 1996. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: Print Symbiont
PRTSMB.EXE
SMBSRVSHR.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPPRTS02_070
ECO Kits Superseded by This ECO Kit: ALPPRTS01_070
ALPPRTS01_062
AXPPRTS02_061 (AXPPRTS)
AXPJOBC01_061 (CSCPAT_2087 V1.2)
This kit was never released.
AXPQMAN01_061 (CSCPAT_2087 V1.1)
AXPPRTS01_061 (CSCPAT_2087 V1.0)
ECO Kit Approximate Size: 1426 Blocks
Saveset A - 198 Blocks
Saveset B - 414 Blocks
Saveset C - 396 Blocks
Saveset D - 396 Blocks
Cover Letter - 22 Blocks
Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2,
V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
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 the Print Symbiont on OpenVMS Alpha V6.1 through
V7.0. This kit addresses the following problems:
Problems Addressed in the 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, 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 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. However,
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 following error
but the input file is not closed:
Job X (queue COLA, entry 3) terminated with error status
%PSM-E-OPENIN, error opening !AS as input
Problems Addressed in ALPPRTS01_070 for OpenVMS Alpha V6.1,
V6.1-1H1, 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:
+ 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
NOTE: According to OpenVMS Engineering, the fixes discussed
below have been included in OpenVMS Alpha V7.0.
There are some fixes that have been included in previous
versions of OpenVMS and those versions are specified in
text following the problem descriptions.
Problems Addressed in the ALPPRTS01_062 Kit for OpenVMS Alpha 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.
Problems addressed in the AXPPRTS02_061 kit:
o The unreleased AXPJOBC01_061 kit contained both QMAN and
PRTSMB ECOs. It superseded both AXPQMAN01_061 and
AXPPRTS01_061. This kit, AXPPRTS02_061, only replaces the
the print symbiont and SMBSRVSHR fixes from that combined
kit. The QMAN fixes have been moved to the AXPQMAN03_061
ECO kit.
Problems addressed in the 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 The 'START/QUEUE/SEARCH="text_string"' DCL command does not start
the print job on the correct page. When a paused print queue is
restarted with the 'START/QUEUE/SEARCH="text_string"' command, the
print job is not restarted on the page that contains the search
text. Rather, the print job starts a few lines prior to the actual
page containing the text.
With the use of the 'START/QUEUE/BACKWARD=n' DCL command, the
print symbiont does not set the first record flag. This causes
an extra line feed to occur which offsets the page alignment
by one line.
o PRTSMB or a user-modified symbiont can fail with an ACCVIO with
the PC=1A45 in the Librarian routines. This causes the print job
to hang.
o In the following cases, the print symbiont prints an unwanted
form feed after a print job:
+ Output ends exactly at the end of the page
+ File printed with /PASSALL ends with a form feed
o When printing a file with the /FORM qualifier on a LAT printer,
it is possible for the LATSYM to crash with PSM-F-BADLOGIC,
internal logic error. 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,
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.
o After a 'START/QUEUE' command is issued and the printing of a
FORTRAN CC file is resumed, 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
Problems addressed in the AXPPRTS01_061 kit:
o When starting a LAT queue, the symbiont process may crash and
the queue will be left in a stopped state. A process
dump, SYS$SYSTEM:LATSYM.DMP, will be created.
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.
Files on this server are as follows:
alpprts02_070.README
alpprts02_070.CHKSUM
alpprts02_070.CVRLET_TXT
alpprts02_070.a-dcx_axpexe
alpprts02_070.b-dcx_axpexe
alpprts02_070.c-dcx_axpexe
alpprts02_070.d-dcx_axpexe
|
