l8HP DECprint Supervisor (DCPS) for OpenVMSG

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



 z d f  
PreviousContentsIndex




U

Chapter 14
Controlling File Separation Pages




EThe printing system can produce both job separation pages (job burst Hpages, job flag pages and job trailer pages) and file separation pages. HThe system manager can define the job separation pages and default file Gseparation pages for the queue. Users cannot affect the job separation >pages, but can control whether to print file separation pages.

)Files in a print job can be separated by:



EYou can control the inclusion of file flag pages using the following PRINT command qualifiers:

x

14.1 Controlling File Separation Pages for All Files



HYou can specify the default file separation behavior for all files in a @print job by placing the /[NO]BURST, /[NO]FLAG and /[NO]TRAILER Fqualifiers between the PRINT command and the first file specification.

GFor example, the following command will print a file burst page before each file:

 

"
9    $ PRINT /BURST FIRST.TXT, SECOND.TXT




FIf you do not specify the behavior for a type of file separation page A(for example, the above command does not specify flag or trailer Epages), the default behavior is as specified by the queue's /DEFAULT Hqualifier. If /DEFAULT does not specify a particular type of separation page, then none is generated.

@The negated qualifiers (for example, /NOTRAILER), are useful in Goverriding a queue's default qualifier (for example, /DEFAULT=TRAILER).ˆ

14.2 Controlling File Separation Pages for Individual Files



GYou can alter the default file separation page behavior for individual =files within a print job by placing the qualifiers after the "corresponding file specifications.

EFor example, you can use the following command to override a queue's G/DEFAULT=BURST qualifier and instead print file flag pages for all but the second file in a job:

 

"
L    $ PRINT /NOBURST /FLAG FIRST.TXT, SECOND /NOFLAG, THIRD


ˆ

14.3 Displaying the Default Separation Pages for a Queue



ETo see the default separation pages for a queue, enter the following command:

 

"
0    $ SHOW QUEUE /FULL PS20$A14




 

"
D    Printer queue PS20$A14, on STAR::LPS, mounted form DCPS$DEFAULT     (stock=DEFAULT) K        /BASE_PRIORITY=4 /DEFAULT=(FLAG,FORM=DCPS$DEFAULT (stock=DEFAULT)) J        /NOENABLE_GENERIC /LIBRARY=DCPS_LIB Lowercase /OWNER=[SYS,SYSTEM] 9        /PROCESSOR=DCPS$SMB /PROTECTION=(S:E,O:RD,G,W:W)         /SCHEDULE=(NOSIZE) "        /SEPARATE=(BURST,TRAILER) 




FThis display shows that the job burst pages and job trailer pages are Gprinted for print jobs sent to this queue (/SEPARATE=(BURST,TRAILER)). GFile flag pages are printed by default, as indicated by /DEFAULT=FLAG, 2but can be overridden by PRINT command qualifiers.‡

14.4 Job Log and Trailer Pages Sent to Default Tray On Error



HThe job log and job trailer pages, if any, are normally directed to the Foutput tray you specified with the OUTPUT_TRAY parameter. However, if GDCPS reports a NOOUTTRAY, OUTTRAYNOTAVL, or OUTTRAYMISMATCH error when Finitially attempting to select the specified output tray, the job log Gand trailer pages are instead directed to the printer's default output 2tray so that you get an indication of the problem.


S

Chapter 15
Selecting Finishing Options




GSome printers have a finisher, often sold as an option, that can punch Bor staple your output. This chapter describes how to select these printer features from DCPS.K

15.1 Punching



@DCPS can punch your job if the printer has a puncher installed. :Punching with DCPS is supported on the following printers:

 GENICOM Intelliprint mL450
GENICOM LN45
HP 9085 MFP
HP LaserJet 9055 MFP
HP LaserJet 9065 MFP
Lexmark W820
B

15.1.1 PUNCH DCL Syntax



5Punching is specified with the PRINT parameter PUNCH.   

"
>$ PRINT /PARAMETERS=(..., [ PUNCH | NOPUNCH ] ,...) file_name 





HThere are no values to the PUNCH parameter. The position of the punched Hholes is determined by the orientation of the paper in the printer, and Cthe number and spacing of holes is determined by the printer. When FNOPUNCH is specified, the job is printed without punching, overriding $the printer's default punch setting.K

15.2 Stapling



ADCPS can staple your job if the printer has a stapler installed. :Stapling with DCPS is supported on the following printers:

 Compaq Laser Printer LN32
Compaq Laser Printer LNM40
GENICOM Intelliprint mL450
GENICOM LN45
GENICOM LNM40
GENICOM microLaser 320
GENICOM microLaser 401
HP 9085 MFP
HP Color LaserJet 9500
HP Color LaserJet 9500 MFP
HP LaserJet 4200
HP LaserJet 4250
HP LaserJet 4300
HP LaserJet 4345 MFP
HP LaserJet 4350
HP LaserJet 8000
HP LaserJet 8100
HP LaserJet 8150
HP LaserJet 9000
HP LaserJet 9000 MFP
HP LaserJet 9050
HP LaserJet 9050 MFP
HP LaserJet 9055 MFP
HP LaserJet 9065 MFP
Lexmark W820
Xerox DocuPrint N24
Xerox DocuPrint N32
Xerox DocuPrint N40
Xerox Phaser 7750
C

15.2.1 STAPLE DCL Syntax



6Stapling is specified with the PRINT parameter STAPLE.   

"
3$ PRINT /PARAMETERS=(..., STAPLE = [ LEFT_CENTER | 7                                         TOP_CENTER  | 7                                         TOP_LEFT    | 7                                         TOP_RIGHT   | 0                                         NONE ] 9                                         ,...) file_name 





DThese values specify the position of the staple with respect to the Gorientation of the image on the paper. When NONE is specified, the job Eis printed without stapling, overriding the printer's default staple setting.G

15.2.2 Stapling Positions



ESome of the values for the STAPLE parameter are not always possible, Adepending on the direction in which the paper is fed through the „printer. See Table 15-1 for possible stapling positions depending on Gyour job's page orientation and the printer's paper feed direction. In Gthe table, "Port" and "Land" refer to portrait and Dlandscape page orientation, and "LEF" and "SEF" Frefer to long-edge-feed and short-edge-feed direction of paper in the printer.

ƒ  J   - / . 0   "                                                                 
Table 15-1 Stapling Positions and Paper Feed Direction
 Staple Position and Image Orientation
 TOP_LEFT TOP_CENTER TOP_RIGHT LEFT_CENTER
Printer Port Land Port Land Port Land Port Land
% Compaq, GENICOM, Lexmark, Xerox  LEF, SEF  LEF, SEF SEF LEF SEF LEF LEF SEF
 HP Color LaserJet 9500  LEF, SEF      LEF, SEF   LEF LEF SEF
( HP LaserJet 4200, 4250, 4300, 4350 SEF         SEF    
. HP LaserJet 8000, 8100, 8150, 9000, 9050  LEF, SEF   SEF LEF   LEF LEF SEF
. HP 9085 MFP, LaserJet 9055 MFP, 9065 MFP  LEF, SEF SEF SEF LEF  LEF, SEF   LEF SEF


EIf you specify an unsupported staple position, DCPS issues the error /message STPPOSNOSUP and does not print the job.;

15.2.3 Output Trays



EStapled output can only be delivered to the output trays attached to |the finisher. Table 15-2 lists the supported output trays for each printer.

u  ( '                  
Table 15-2 Output Trays Supported for Stapling
Printer Brand Output Trays
 Compaq, GENICOM, Xerox  STACKER / BIN_1
  BIN_2
  BIN_3
 HP, Lexmark  STACKER / BIN_2


FIf you specify a tray not supported for stapling, or do not specify a @tray but the printer's default output tray is not supported for Fstapling, DCPS issues the error message STPOUTTRAY and does not print the job.9

15.2.4 Paper Sizes



>Printers do not support stapling on every paper size and feed Edirection. In general, envelope sizes are not supported for stapling.

DIf you specify a size that cannot be stapled, DCPS issues the error 0message STPSIZENOSUP and does not print the job.C

15.2.5 Stapling Details



@Please note the following details when using stapling with DCPS:




R

Chapter 16
Using the Error Handler to Debug




CThe device control library includes an error handler to help debug GPostScript programs. The error handler prints the last partial page of :output, as well as information to help identify the error.n

16.1 Including the Error Handler in a Print Job



GThe error handler is not automatically included each time a job prints F(unless your system manager has changed this default). Therefore, you &must explicitly invoke it, as follows:

 

"
G    $ PRINT /SETUP=LPS$ERRORHANDLER file-name




BThe error handler returns PostScript messages. You can send these @messages to a file or printer by using the /PARAMETERS=MESSAGES fqualifier as described in Chapter 17. For example:

 

"
N    $ PRINT /QUEUE=PS40$A10 /PARAMETERS=MESSAGES=KEEP FILE.PS




FIf you are developing PostScript applications, you can make the error Ahandler easier to access by defining a form to include the error chandling setup module, as described in Chapter 12.{

16.2 How the Error Handler Affects the PostScript Environment



;The error handler references operators from the dictionary Dsystemdict, rather than using definitions that may 'have been modified by the user program.

GIn some cases, a program can behave differently when the error handler Eis loaded. For example, executing the exit operator Goutside a looping context causes an invalidexit error Eif the error handler is not loaded. However, if the error handler is 6loaded, the program exits without generating an error.Y

16.3 Error Handler Example



€The sample log file in Example 16-1 is for the following PostScript program:

 

"
D    [/1st-level [/2nd-level [/3rd-level [/4th-level 56 ] ] ] (end)] ,    /myproc { [ 8 8 ] 0 0 div setdash } def     100 200 moveto     myproc 




GThe following command includes the error handler and causes a log file to be generated:

 

"
a    $ PRINT /PARAMETERS=MESSAGES=KEEP /SETUP=LPS$ERRORHANDLER file-name




Example 16-1 shows the error handler output that is appended to the #log file when the program executes.$

 D  
Example 16-1 Sample Error Handler Log File
 

"
M    ERROR: undefinedresult (1)M    OFFENDING COMMAND: div (2) F    OPERAND STACK:  (3)     0     0     [ 8 8 ] =    [/1st-level [/2nd-level [/3rd-level  -array- ] ] (end) ]  H    EXECUTION STACK:  (4)     { setdash }  G    GRAPHICS STATE:  (5)<    Current Matrix: [ 4.16667 0.0 0.0 -4.16667 0.0 3298.0 ]     Color: 0.0 +    Current position: x = 100.0, y = 200.0     Line width: 1.0     Line cap: 0     Line join: 0     Flatness: 1.0     Miter limit: 10.0     Dash pattern: [ ] 0.0 




EThe array defined at the start of the example file is expanded three Flevels deep. The innermost version of the array is represented simply as --array--._

16.4 Reading Error Handler Output



3When an error occurs, the error handler executes a Dshowpage command to print the last partial page of output (see Example 16-1). It also gives the following information:

    2
  1. The name of the errorJ
  2. The PostScript operator that encountered the  errorG
  3. The contents of the operand stack
    The E error handler displays the value of each object on the stack, with J numbers in decimal. All elements of arrays and procedures are displayed F recursively to a maximum depth of three levels. Indicators describe G other objects, for example, --savelevel-- for a save object.
    The = first item displayed is the object on the top of the stack.I
  4. The contents of the execution stack
    The G execution stack contains partial procedures that are being executed. I The top object is a procedure that contains the operators and operands H still to be executed. The second object is the unexecuted part of the  calling procedure.B
  5. Information about the graphics state:
    ! Current transformation matrix4
    Color (a currentgray value)
    Current position
    Line width
    Line cap
    Line join
    Flatness
    Miter limit
    Dash pattern
    


EWhen you find an error in the PostScript code, you should modify the ?application that produced the file, or inform the applications programmer of the problem.e

16.5 PostScript Data Output Format



DPostScript data is easily identifiable, usually in the way the data Bappears in a PostScript source file. The error handler represents PostScript data as follows:



DThe PostScript language may be extended to include new data formats Bthat are unknown to the error handler. Data in unknown formats is Frepresented as two question marks followed by the name of the unknown data format.f

16.6 Determining Where the Error Occurred



BIt may be impossible to determine exactly where in the PostScript Hstream the error occurred, because the execution stack may not uniquely Hidentify the context. In this case, you can add diagnostics information Hto the PostScript file. For example, if the error appears to be related Gto a showpage definition, modify your PostScript code as follows:

 

"
    /myshowpage 	       { 1       (At the top of my showpage\n) print flush        % some PostScript code 6       (Just before real showpage call\n) print flush        showpage 
       } def 







 z a d f  
PreviousNextContentsIndex