l8HP DECprint Supervisor (DCPS) for OpenVMSG

HP DECprint Supervisor (DCPS) for OpenVMS
User's Guide

z d f

3.1.3 Using the Envelope Feeder

AYou must specify the paper size with the SHEET_SIZE or PAGE_SIZE Fparameter when you specify the ENVELOPE_FEEDER input tray. Otherwise, Ayour print job terminates and the following message is displayed:

"
D NO_SHEET_SIZE, Sheet_size must be specified for Envelope_Feeder

^

3.2 Selecting the Output Tray

4Some PostScript printers have multiple output trays.

EYou can list the output trays available with your type of printer by Hentering the HELP PRINT_PARAMETER OUTPUT_TRAY command and selecting the %subtopic that describes your printer.

AYou can select the output tray for print jobs destined for these >printers using the OUTPUT_TRAY parameter in the PRINT command.

"
\ $ PRINT /PARAMETERS=OUTPUT_TRAY=output-tray file-name

For example:

"
C $ PRINT /PARAMETERS=OUTPUT_TRAY=SIDE MYFILE.PS

GIf you select an unsupported output tray, the print job may be printed Eand sent to another output tray, and the following message displayed:

"
a TRAYSUBST, Output will be delivered to the output-tray tray on printer-name

BAlternatively, your print job may be terminated and the following message displayed:

"
V NOOUTTRAY, OUTPUT_TRAY, tray-name, not supported on printer-name

ESome printers have optional output trays. If you specify an optional Houtput tray that is not currently available on the printer, your output Awill be directed to a similar tray if one exists. If there is no Csimilar output tray, the job is terminated and the following error message is displayed:

"
N OUTTRAYNOTAVL, No tray-name is installed on printer-name

J

3.2.1 Manually Selecting Output Trays

DIf you manually select the output trays on your printer, you cannot Hchange trays with the OUTPUT_TRAY parameter. You must select the output Ctray by using the controls on the printer. Refer to the operator's Bguide to your printer for information about output tray selection.

FIf you specify the OUTPUT_TRAY parameter for this type of printer, be Gsure that the appropriate output tray is selected manually. Otherwise, Gthe print job is terminated and the following message may be displayed:

"
V OUTTRAYMISMATCH, Printer printer-name output tray setting does not match < requested output-tray on printer-name

Chapter 4
Printing PostScript Files

4.1 Printing Jobs with Multiple PostScript Files

FThe PostScript file created by your application modifies the state of Lthe PostScript interpreter in the printer. The DECprint Supervisor software Gresets the printer state for each new print job, but not for each file @in the print job. Therefore, files that are meant to be printed Ftogether, such as a data file with an application prologue or a font, Dwill print successfully. But in a print job with a set of unrelated Hfiles, the state of the printer after completing printing of a file may 2adversely affect the printing of subsequent files.

?This can cause PostScript errors and unexpected changes in the Cappearance of the printed documents. If you need to print multiple GPostScript files, or multiple copies of a PostScript file, submit them using separate print jobs.o

4.2 Printing Files that Contain Text and PostScript

NDECprint Supervisor software can detect PostScript data after the text at the Dbeginning of the file. This is useful for printing PostScript files Hsent to you by an electronic messaging system that places text in front of the PostScript file.

AFor example, if you receive a message in a software utility that Hcreates ANSI text, and that message includes a PostScript file, you can 0print the file without specifying the data type.†

4.3 Printing Files Created on Other Operating Systems

BWhen creating PostScript files on systems running other operating Fsystems for eventual printing through DECprint Supervisor for OpenVMS 7software, you should keep the following points in mind:

Use of Printer-Specific Code
Windows and Macintosh printer I drivers often create PostScript code that is specific to a printer and I to the set of printer options for which you configured the driver (for I example, printer brand and model, trays available, whether the printer C can perform duplex printing, how much memory is available in the A printer, etc.). If you later attempt to print such a file on a J different type of printer or a printer with a different set of options, E the file may not print correctly.
Try to create a file that is I specific to the printer and printer options that you ultimately intend H to use. Alternatively, attempt to select a generic printer, optimized G for portability, with few options, to increase your chances of being G able to print the file on multiple printer configurations. (Also see A Section 4.5.)H
Use of Feature-Specific PostScript Code
Windows and Macintosh H applications and printer drivers often create PostScript code that is H specific to a set of printer features that you select when you create E the file (for example, which tray to use, the number of uncollated G copies, simplex or duplex, etc.). When your PostScript file contains I explicit requests for such features, the corresponding DCPS parameters H (for example, INPUT_TRAY, OUTPUT_TRAY, SHEET_COUNT, SIDES, etc.) have J no impact on your print job.
If your application and printer driver I allow you to default certain settings (for example, the input tray) to J the current printer setting, do so and then specify the desired setting G using a DCPS parameter. Otherwise, use your application or driver to @ specify the feature and omit the corresponding DCPS parameter.I
Assumptions about Printer-Specific Setup
The physical setup of J a printer can vary from printer to printer, and over time. For example, D you might create a PostScript file to print to the top input tray E because you know that the top tray on your printer contains yellow I paper and you want to print on yellow paper. However, if you then send G the file to another printer of the same brand and model, or even the F same printer at a later date, the top tray may contain other media. G
For printer features that DCPS does not allow you to specify and D that your application and printer driver also do not allow you to G specify (for example, media type), verify that the physical setup of I the target printer is as you desire before sending your file to it. If H not, you may have to recreate the file for the reasons given in items number 1 and 2 above.

4.4 Creating Printer-Specific PostScript Documents

GEach model of PostScript printer recognizes some unique operators that Aare not part of the standard PostScript language. The PostScript Gextensions for each PostScript printer may be described in the printer owner's manual.

FMany commercial applications, and printer drivers on PC and Macintosh >systems, allow you to specify printer features that depend on ˆprinter-specific extensions (see Section 4.3). For example, you can Hcreate a PostScript file that requires the use of the top input tray on Fa particular printer. If you try to print the file on another type of Gprinter, the file may print from a different tray, or may even fail to print.g

4.5 Creating Portable PostScript Documents

HTo create documents that are independent of printer type, make sure the Capplication that you use to create the PostScript file has printer Fsetup options that do not conflict with the PRINT parameters that you >specify with the DCPS software. Use option settings to ensure 9that your PostScript document is as portable as possible.

HTo ensure that your application creates documents that are printable on Ethe widest variety of printers, select "printer's default" Efor all printer-specific options such as input and output trays. Or, Dselect a generic printer or one without duplex printing or multiple Finput trays. Then, choose the feature in your application that allows you to print to a file.w

4.6 Resolving Unrecognized PostScript Operator Errors

@If you try to print a file that contains a PostScript extension Doperator that is not defined in your printer, you get the following error message:

"
U %DCPS-W-UNDEF, undefined: Name not known - offending command is operator

COperator is the PostScript extension operator that is not recognized by the printer.

?You may be able to resolve this problem by doing the following:

Re-create the PostScript file from the application. Examine the J print setup options and disable any options that are not generic to all Z PostScript printers (see Section 4.5).|
If you must print the PostScript file that fails, see Section 4.7 0 for information about modifying the print job.

4.7 Using Example Files to Suppress PostScript Operators

:The DCPS software provides example files that show how to ;suppress many commonly used PostScript extension operators.V

4.7.1 Suppressing PostScript Operators on Desktop Printers

EIf you are using a desktop printer, you can create a setup module to Hsuppress the failing PostScript operator. The following example file is #distributed with the DCPS software:

"
7 SYS$COMMON:[SYSHLP.EXAMPLES.DCPS]LPS$STATUSDICT.PS

DThis file is an assortment of PostScript routines. You can edit the Dfile and copy routines that solve problems with specific PostScript Doperators. The new file that you create can be specified as a setup -module and printed with the file that failed.

6See the DCPS System Manager's Guide for more information about setup modules.b

4.7.2 Suppressing PostScript Operators on PrintServer Printers

EThe PS_SUPPLEMENT file can be loaded into the PrintServer printer so Fthat many unrecognized PostScript extension operators are ignored. If Ayou have PrintServer Software Version 4.2 or later, this file is )automatically downloaded to your printer.

Chapter 5
Printing ANSI Files

DWhen you submit ANSI or ASCII text files for printing on PostScript Nprinters, they are translated to PostScript. The DECprint Supervisor software Erecognizes the full range of ANSI escape sequences for all levels of Šthe ANSI printing protocol. Refer to the Digital ANSI-Compliant Printing Protocol Level 3 Programming Reference Manual for more Ginformation about the DIGITAL ANSI-compliant printing protocol and the !functions of the ANSI translator.o

5.1 Printing Multiple ANSI Files in a Print Job

GANSI files are handled differently from other types of files. When you Fprint more than one ANSI file in a print job, the printer commands in Ethe first file are not passed on to the second file. You must use an DANSI setup module to pass printing attributes, or include the print attributes in each file.]

5.2 Emulating ANSI Printers

CIf your site has changed the printing system from ANSI printers to GPostScript printers, you can take advantage of the DECprint Supervisor Dsoftware to print ANSI files that were created for ANSI printers on your new PostScript printers.

OThe DECprint Supervisor software automatically handles ANSI file printing in a Gway that emulates printing on ANSI printers. If you need to modify the >way that ANSI files are printed, use any of the qualifiers in WTable 5-1 to enhance your printed document.

Y 4 1 1
Table 5-1 ANSI Print Qualifiers
To modify this aspect ... Use this qualifier ... To get this effect ...
K Form feeds, which are usually inserted into the ANSI document at the bottom of each page /NOFEED - Suppress automatic form feed insertion.
Header lines on each page /HEADER ¹ M Print the file name, page number, and file creation date at the top of each page.
( Margin, header, and tab processing /PASSALL G Preserve the state of the file through printing without imposing A margins, headers, or tab emulation on the printed document.
Single-spaced documents /SPACE ¹ H Insert a blank line after each text line, providing double-spaced output.
) Expansion of tabs during processing /PARAMETERS=[NO]TAB ¹ l Control how tabs are processed (see Section 5.3).
" Fonts available for printing /PARAMETERS=FONTS_USED M Specify one or more SoftFont modules that include software fonts that e emulate font cartridges (see Section 5.4).
D Formatting of text by the default form specified for the queue /FORM < Specify the form definition assumed for the print job.

**Table 5-1 ANSI Print Qualifiers**
To modify this aspect ...	Use this qualifier ...	To get this effect ...
K Form feeds, which are usually inserted into the ANSI document at the bottom of each page	/NOFEED	- Suppress automatic form feed insertion.
Header lines on each page	/HEADER ¹	M Print the file name, page number, and file creation date at the top of each page.
( Margin, header, and tab processing	/PASSALL	G Preserve the state of the file through printing without imposing A margins, headers, or tab emulation on the printed document.
Single-spaced documents	/SPACE ¹	H Insert a blank line after each text line, providing double-spaced output.
) Expansion of tabs during processing	/PARAMETERS=[NO]TAB ¹	l Control how tabs are processed (see Section 5.3).
" Fonts available for printing	/PARAMETERS=FONTS_USED	M Specify one or more SoftFont modules that include software fonts that e emulate font cartridges (see Section 5.4).
D Formatting of text by the default form specified for the queue	/FORM	< Specify the form definition assumed for the print job.

F¹When you include this qualifier, the default form for the lqueue is applied to the print job. See Chapter 12 for more information.

5.3 Processing Tabs in ANSI Files

GThe [NO]TAB parameter allows you to emulate the ways in which the ANSI Fprinter handles tab characters. When you include the TAB parameter in Gyour print job, the action is equivalent to using the SET TERMINAL/TAB command on the ANSI printer.

HThe [NO]TAB parameter is useful when you are not printing 10 characters Dper inch, or when ANSI tabs are defined in inches, not by character Dposition. If you change the character size, tab sizes do not change Hwhen you specify PARAMETERS=TAB. If you expect tabs to change size when 2characters change size, specify /PARAMETERS=NOTAB.

AWhen you specify [NO]TAB, the software invokes the default form, uDCPS$DEFAULT for your job. Refer to Chapter 12 for more information "about the default form definition.

NBy default, the DECprint Supervisor software processes tab characters so that 5tab stops are set at every eight character positions (/PARAMETERS=NOTAB).

HThe system manager can change this operation as a queue default so that Cyou do not have to specify it on the PRINT command line. Different Dsettings of this parameter may be established as queue defaults for Hdifferent generic queues driving the same printer. In this way, you can Faccess either method of tab expansion when you submit print jobs from Fapplication programs that allow you to specify the queue name but not the print parameters.d

5.4 Emulating Printer Font Cartridges

DYour document may require font cartridges in order to print on ANSI Eprinters. If you want to print the document on a PostScript printer, Fyou can use the FONTS_USED parameter to emulate the ANSI printer font Hcartridges. The files must contain escape sequences that call the fonts.

Note

FThese font modules are not a standard part of the DECprint Supervisor Fsoftware. Your system manager can obtain SoftFont kits separately and Dthen install them in the font library. (The SoftFont kits have been Gretired and are no longer available from HP.) To list the font modules Cthat have been installed on your system, use the following command:

"
E $ LIBRARY /LIST /TEXT SYS$LIBRARY:CPS$ANSI_FONTS

BIf this file does not exist, no font modules have been installed.

?To include one or more font modules in your print job, use the G/PARAMETERS=FONTS_USED qualifier in the PRINT command. For example, if Eyou used to print your file on an ANSI printer with the ITC Souvenir Bcartridge installed, enter the following command to print it on a 9PostScript printer with the DECprint Supervisor software:

"
U $ PRINT /PARAMETERS=(FONTS_USED=ITC_SOUV_MCS) file-name

Note

GIf you include two or more cartridge names, be sure to place quotation marks around them. For example:

"
_ $ PRINT /PARAMETERS="FONTS_USED=(ITC_SOUV_MCS,BARCODE)" file-name

iSee Appendix D for a list of the available SoftFont kits.q

5.5 Using PostScript Operators to Change Trays

GWith the DCPS software, you can print ANSI documents that were created 1for printing on media from a specific input tray.

HThe DCPS software recognizes escape sequences in ANSI files that select Dthe printer input tray. If you print an ANSI file that is set up to Hselect an input tray that does not exist on your printer, the print job 2fails and you receive the following error message:

"
; %DCPS-W-RANGECHK, rangecheck: Argument out of bounds - ( offending command is setpapertray.

DIf this happens, you can create a PostScript setup module to submit Gwith the print job, and redefine the input tray settings. For example, ?you could create a PostScript setup module using the following PostScript operators:

"
: /settoptray {statusdict begin 2 setpapertray end} def = /setbottomtray {statusdict begin 1 setpapertray end} def

9This example selects the printer tray 2 for the top tray >(settoptray), and tray 1 for the bottom tray E(setbottomtray). When you create a PostScript setup umodule, use the operator listed in Table 5-2 that corresponds to Bthe input tray specified in the ANSI file. Select a value for the Dsetpapertray argument that corresponds to an input tray onFyour printer. Refer to your printer owner's manual for the input tray "numbers supported by your printer.

@Submit the setup module with your ANSI document using the PRINT Fcommand. For example, to use the setup module TRAYDEF.PS to print the /file OVERHEAD.TXT, enter the following command:

"
@ $ PRINT /NOTIFY /SETUP=TRAYDEF OVERHEAD.TXT

EThe ANSI input tray selection sequences and the PostScript operators nassociated with each of them are listed in Table 5-2. The Ftranslator uses the default setpapertray value if no Dother value has been defined. A setup module with a different value overrides the default value.

n ( 1 5
Table 5-2 Operators for Changing Input Trays
ANSI Sequence User-Defined Operators Default setpapertray Value
CSI ! v [none] [none]
CSI 0 ! v [none] [none]
CSI 1 ! v settoptray 1
CSI 2 ! v setbottomtray 2
CSI 3 ! v setlcittray 3
CSI 4 ! v setmanualfeedtray 0
CSI 99 ! v setmanualfeedtray 0
i

**Table 5-2 Operators for Changing Input Trays**
ANSI Sequence	User-Defined Operators	Default setpapertray Value
CSI ! v	[none]	[none]
CSI 0 ! v	[none]	[none]
CSI 1 ! v	settoptray	1
CSI 2 ! v	setbottomtray	2
CSI 3 ! v	setlcittray	3
CSI 4 ! v	setmanualfeedtray	0
CSI 99 ! v	setmanualfeedtray	0

5.6 Using ANSI Sequences to Print Duplex or Simplex

DTo specify one- or two-sided printing, add ANSI escape sequences to uyour file. The ANSI duplex sequences are listed in Table 5-3. HReplace the sp value in the table with a blank character space in your ANSI file.

| ( +
Table 5-3 ANSI Sequences for Printing Simplex or Duplex
ANSI Sequence Duplex Operation
CSI 0 sp x true simplex normal
CSI 1 sp x true simplex normal
CSI 2 sp x true simplex tumbled
CSI 3 sp x true duplex normal
CSI 4 sp x true duplex tumbled
CSI 5 sp x duplex master normal
CSI 6 sp x duplex master tumbled
CSI 7 sp x simplex compressed normal
CSI 8 sp x compressed tumbled

**Table 5-3 ANSI Sequences for Printing Simplex or Duplex**
ANSI Sequence	Duplex Operation
CSI 0 sp x	true simplex normal
CSI 1 sp x	true simplex normal
CSI 2 sp x	true simplex tumbled
CSI 3 sp x	true duplex normal
CSI 4 sp x	true duplex tumbled
CSI 5 sp x	duplex master normal
CSI 6 sp x	duplex master tumbled
CSI 7 sp x	simplex compressed normal
CSI 8 sp x	compressed tumbled

z a d f

Contents

Index

HP DECprint Supervisor (DCPS) for OpenVMSUser's Guide