Technical data

15.2.7 Looping When Handling Messages with ’]’ in Job: field
DCPS now properly handles PostScript printer messages with a ’]’ character in
the job name. Parsing such a message in previous versions would result in an
infinite loop. This was most likely to be noticed when printing to a printer on an
AppleTalk network.
15.2.8 Handling of Long Device Names in DCPS$STARTUP.COM
DCPS V1.1A did not properly account for the SCSNODE name when
determining the value for the /ON qualifier from the P2 value supplied to
DCPS$EXECUTION_QUEUE.COM by DCPS$STARTUP.COM. If the node’s
SCSNODE name was less then 6 characters, an error could occur when the queue
was started. This has been fixed.
15.2.9 Form Setup Modules and Multiple File Jobs
A setup module specified by the /SETUP qualifier of a form is sent to the printer
just once at the beginning of a print job if the setup module is PostScript. If the
job included multiple files or copies of a file, the PostScript context established
by this setup module could be lost and the rest of the files would not print as
expected. This happened because, when needed, DCPS sends the PostScript
’newsheet’ operator between files to ensure new files start on new sheets. The
PostScript context is now saved before executing ’newsheet’, and restored after
executing ’newsheet’.
15.2.10 Interrupting Busy Printers When a Job Starts
Previous versions of DCPS, when used with serially-connected printers, used an
aggressive synchronization sequence to gain control of the printer’s PostScript
interpreter. This is no longer the case, as it occasionally caused problems when a
printer was used in a shared multi-host environment.
However, if you rely on DCPS’s previous ability to abort errant PostScript
jobs on one queue by starting a job on another queue, you can define a DCPS
logical name to restore the previous functionality, as described in the DECprint
Supervisor for OpenVMS System Manager’s Guide.
15.2.11 Suppressing PostScript Synchronization When a Job Starts
Defining the logical name DCPS$queuename_NO_SYNC causes the DCPS
symbiont to avoid using its usual synchronization sequence on printers other
than PrintServer printers. This includes printers that use LAT or raw TCP/IP
connections on built-in Network Interface Cards (NICs). It has no effect when
using printers connected via other interconnects. This logical name is supported
by Versions 1.2 and later of DCPS to help avoid problems that have been reported
in past versions.
15.2.12 DDIF Files with Invalid Parameter Values
The DDIF translators have been modified to handle files with invalid values
for some parameters. Specifically, if the value for either the ‘‘PixelPath’’ or
‘‘LineProgression’’ parameter is invalid, then the default value for that parameter
is assumed.
DCPS Version 1.2 Information 15–3