l8HP DECprint Supervisor (DCPS) for OpenVMSG

HP DECprint Supervisor (DCPS) for OpenVMS
System Manager's Guide

z d f

7.11 Device Control Library Cache Feature

FDCPS includes a device control library caching feature that optimizes Athe retrieval of certain commonly-used PostScript device control modules.

FThe caching feature causes modules with names beginning with LPS$$ to Hbe read only the first time they are requested. Those modules reside in Hthe symbiont's cache. Jobs that follow can quickly access those modules Guntil you reset the queue or restart the system. This minimizes access Dto the primary device control library, saves CPU time, reduces disk activity.

FThe device control library caching feature is disabled by default. To Henable the device control library caching feature for a specific queue, ;enter the following command before you start a print queue:

"
] $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_DEVCTL_CACHE 1

GCaching device control library modules can decrease the total CPU time Gconsumed by the symbiont by as much as 17 percent. I/O activity on the >part of the symbiont is also reduced by as much as 50 percent.

HYou can define the system logical DCPS$DEVCTL_CACHE (with no queue name Especified) to specify that device control library caching is enabled 3for all DCPS print execution queues on that system.j

7.12 Printing on Unrecognized Printers

HThe DCPS software automatically obtains a printer's product name before Fprinting jobs. It uses the product name to select and download device <control modules that are specific to the particular printer.

GIf you use the DCPS software with a printer whose product name it does Hnot recognize, the product name defaults to "HPGENERIC" if it Ais an HP printer, and "UNRECOGNIZED" if it is not. The Gsupervisor downloads device control modules associated with that name. HAlthough this configuration is unsupported, the modules associated with Gan "unrecognized" printer may be sufficient to permit simple @printing with that device. Printers identified as "generic FHP" use commands common to most HP printers and allow additional Dfeatures such as tray selection and use of the printer's native PCL interpreter.

FIf a printer is being treated as a "generic HP" printer, an 6OPCOM message similar to the following will be issued:

"
; %%%%%%%%%%% OPCOM 14-NOV-2002 16:25:43.37 %%%%%%%%%%% % Message from user SYSTEM on FUNYET M Queue MY_NEW_PRINTER: %DCPS-W-HPGENERIC, Product name hp LaserJet 9999 not # recognized; assuming HP Generic

FIf a printer is being treated as an "unrecognized" printer, 9an OPCOM message similar to the following will be issued:

"
; %%%%%%%%%%% OPCOM 20-MAY-2003 16:54:05.25 %%%%%%%%%%% % Message from user SYSTEM on FUNYET N Queue YOUR_NEW_PRINTER: %DCPS-W-UNRECOGNIZED, Product name Foo Bar 1234 not % recognized; assuming Unrecognized

BA system manager can also modify the corresponding device control Fmodules as needed without affecting the characteristics of any of the Csupported printers. By following the comments contained within the GLPS$$UNRECOGNIZED modules, along with some knowledge of PostScript and Hthe specifics of the printer, and examination of device control modules Ffor similarly programmed printers (if any), the system manager may be Bable to get tray and sheet size selection working for the printer.

Note

>Your use of an unrecognized printer with DCPS, and any use or Amodification of the LPS$$UNRECOGNIZED device control modules, is Hwithout support or assistance from Hewlett-Packard Company. Further, HP Emakes no commitment to maintain the same contents of or interface to 5these modules for different versions of DCPS.

CDevice control modules are located in the following device control library:

"
% SYS$COMMON:[SYSLIB]DCPS$DEVCTL.TLB

GThe device control modules associated with an unrecognized printer are:

"
! LPS$$UNRECOGNIZED_INITPSDEVICE LPS$$UNRECOGNIZED_SETCONTEXT ! LPS$$UNRECOGNIZED_SETINPUTTRAY " LPS$$UNRECOGNIZED_SETOUTPUTTRAY

EIf you modify these modules for a certain printer, you should always Eplace the modified modules in a site-specific device control library N(see Section 7.4).

Chapter 8
Creating and Maintaining Form Definitions

HYou can create form definitions, which users can include in their PRINT Bcommand to modify the appearance of a file. A form definition can Hspecify several attributes for a print job, including the type of paper Cstock on which it is to be printed; the width, length, and margins Gassociated with the paper; whether long text lines are to be truncated For wrapped onto another line; and setup modules to be implicitly sent to the printer.

@When users specify an unknown form name in their PRINT command, NDECprint Supervisor informs them immediately. In contrast, if they specify an Junknown setup module in their PRINT command, DECprint Supervisor does not Finform them of the problem until it starts printing the job and needs to access the setup module.

HThe commands for creating, maintaining, and deleting forms require that you have operator privileges.r

8.1 Associating Setup Modules with Forms

FTo associate a setup module with a form, use the DEFINE /FORM command with the /SETUP qualifier.

yExample 8-1 defines a form called CONFIDENTIAL that uses a setup module called PRIVATE.

B
Example 8-1 Sample Form Definition, CONFIDENTIAL

"
6 $ DEFINE /FORM CONFIDENTIAL 101 -R _$ /DESCRIPTION="prints the word CONFIDENTIAL on each page" -( _$ /STOCK=DEFAULT -& _$ /SETUP=PRIVATE

@When you define a form, you supply the following qualifiers and information:

Form Name: You select the name for the form you E are defining. The name can consist of up to 31 characters and must , contain at least one alphabetic character.J
Form Number: You specify a number for the form you are defining.?
/DESCRIPTION: You can optionally add a F description to the form to help users understand what the different forms do.E
/STOCK: You supply the name of the media that F needs to be in the printer when this form is invoked. The media you I specify must match the media in the printer. If they do not match, the J job is held in the queue until users load the specified media or modify J the form definition. Use the DEFAULT parameter to use whatever media is in the printer.E
/SETUP: You must supply the name of the setup . module(s) you want associated with the form.

Note

FThe existence of the setup module(s) is not checked until the form is used.

8.2 Associating a Form with a Print Queue

GIf users invoke a setup module frequently, you can associate the setup Fmodule with a form, then associate the form with a queue. This method Eensures that print jobs submitted to the queue automatically use the Esetup module. Use the following procedure to associate a form with a queue:

Associate the setup module with the form, as described in M Section 8.1.J

Associate the form with the execution queue, by editing parameter 5 7 (P5) in DCPS$STARTUP.COM as follows:

With the /FORM_MOUNTED qualifier, specify the name of the form you want tied to the queue.I
Specify the /DEFAULT=FORM=form-name qualifier to ensure I that every job prints with the form, even if the user does specify a form.

K
The following example associates the form called CONFIDENTIAL with # an execution queue called XLR8:

"
) $ @SYS$STARTUP:EXECUTION_QUEUE.COM - : XLR8- !P1 - Execution queue name 1 "DECNET/XLR8" - !P2 - Device name ? DCPS_LIB - !P3 - Logical name for /LIBRARY . "" - !P4 - Not used F "/FORM_MOUNTED=CONFIDENTIAL/DEFAULT=(FORM=CONFIDENTIAL,NOFEED)" > !P5 - Queue default qualifiers

8.3 Creating Form Definitions for ANSI Files

EWhen you define forms for ANSI files, you can use various qualifiers Hthat affect the page layout. For example, the following command defines Bthe form CENTER to have a top margin of 6 and a left margin of 10:

"
D $ DEFINE /FORM /MARGIN=(TOP=6,LEFT=10) CENTER 3

jYou can use the qualifiers in Table 8-1 with form defintions for ANSI files only:

h - 1
Table 8-1 DEFINE / FORM Qualifiers for ANSI Files
This Qualifier ... Does the Following ...
/LENGTH= n - Sets the length of each page, in lines.
/MARGIN= keyword= n Sets the margins.;
You supply one or more of the following keywords:

TOP= n
BOTTOM= m
RIGHT= y
LEFT= z
O
To supply more than one margin keyword, enclose the list in " parentheses, as in:
/MARGIN=(TOP=n,BOTTOM=m)

/PAGE_SETUP= module : Applies a page setup module to each page in the job.
/[NO]TRUNCATE = Truncates long lines that do not fit in the page width.
/WIDTH= n : Sets the width of the page in columns or characters.
/[NO]WRAP 7 Wraps lines wider than the page to the next line.

**Table 8-1 DEFINE / FORM Qualifiers for ANSI Files**
This Qualifier ...	Does the Following ...
/LENGTH= n	- Sets the length of each page, in lines.
/MARGIN= keyword= n	Sets the margins.; You supply one or more of the following keywords: TOP= n BOTTOM= m RIGHT= y LEFT= z O To supply more than one margin keyword, enclose the list in " parentheses, as in: /MARGIN=(TOP=n,BOTTOM=m)
/PAGE_SETUP= module	: Applies a page setup module to each page in the job.
/[NO]TRUNCATE	= Truncates long lines that do not fit in the page width.
/WIDTH= n	: Sets the width of the page in columns or characters.
/[NO]WRAP	7 Wraps lines wider than the page to the next line.

Notes:

These form definitions are useful only with ANSI files, because C other types of files have internal controls for these attributes.E
You can prevent the software from wrapping or truncating long I lines by including both /NOWRAP and /NOTRUNCATE in the form definition.

8.4 Displaying Forms and Their Attributes

EYou can display the forms that already exist on your system with the following command:

"
' $ SHOW QUEUE /FORM

(The form definitions display as follows:

"
> Form name Number Description > --------- ------ ----------- K A4_12 (stock=PLAIN_PAPER) 1129 A4 12-Pitch with margins T A4_LPT_GRAY (stock=PLAIN_PAPER) 1118 A4 DP line printer with gray bars % A4_LPT_PLAIN (stock=PLAIN_PAPER) R 1119 A4 Plain DP line printer format = BOOT_CHART (stock=DEFAULT) 37 BOOT_CHART I BSS$LANDSCAPE (stock=DEFAULT) 3301 BSS Specific Landscape H BSS$PORTRAIT (stock=DEFAULT) 3302 BSS Specific Portrait

DYou can display the attributes of a form using the SHOW QUEUE /FORM D/FULL command. For example, this command displays the attributes of DCPS$DEFAULT:

"
: $ SHOW QUEUE /FORM /FULL DCPS$DEFAULT

"
> Form name Number Description > --------- ------ ----------- ? DCPS$DEFAULT (stock=DEFAULT) 1115 DCPS default 6 /LENGTH=66 /STOCK=DEFAULT /TRUNCATE /WIDTH=80

T

8.5 Deleting a Form

BUse the DELETE /FORM command to delete a form definition from the >system's form table. The format of this command is as follows:

"
6 $ DELETE /FORM form-name

FIn the command line, you supply form-name, which is the name #assigned to the form you are using.

FBefore you use the DELETE /FORM command, execute the SHOW QUEUE /FULL C/ALL command. References to a form can exist as an attribute of an Gactive print queue or as a qualifier to a print request. If you try to Gdelete a form that has outstanding references, you are notified of the qcondition, and the form is not deleted. (Refer to Appendix A.)

8.6 Using the Default ANSI Form Definition

GIf users omit a form definition in their PRINT command, but supply one 9of the following qualifiers, DCPS links the default form +definition DCPS$DEFAULT with the ANSI file.

/HEADER
/SPACE
/PARAMETERS=[NO]TAB

Chapter 9
Charging Users for Printer Resources

FThis chapter describes the accounting information that is supplied to 2the OpenVMS accounting files by the DCPS software.

BThe OpenVMS Accounting Utility reads information about the use of Dsystem resources from the file SYS$MANAGER:ACCOUNTING.DAT. The DCPS Csoftware records information in this file about printer usage. For |information about the OpenVMS Accounting Utility, see the HP OpenVMS System Management Utilities Reference Manual.v

9.1 Accounting Information Supplied by the DCPS Software

HThe print symbiont supplies the following information in the accounting file for each print job:

Pages printed
This is the actual number of sheets printed. When E you are using the NUMBER_UP parameter to print multiple pages on a G sheet, this field records the number of sheets of paper printed, not D the number of logical pages printed. The number of sheets printed E includes the separation (flag, trailer, and burst) pages. When the H print job is deleted by the user or system operator, this information F reflects the number of pages printed before the job was terminated. J
The value shown in the accounting file and on the DCPS trailer page v will not be correct for all printers. See Section 9.3 for more information.F
Gets from source
This is the number of RMS "gets" 1 from all files in the print job (records read).G
QIO puts
This is the number of QIO "writes" to the printer per job.

F When a print job has been completed successfully, the print symbiont I sends a request to the job controller to insert certain accounting data C fields into the accounting log file. For successful jobs and jobs C terminated by the DELETE /ENTRY command, the accounting file also includes the following message:

"
.%SYSTEM-S-NORMAL, normal successful completion

BIf the print job terminates abnormally, the information the print Esymbiont supplies in the accounting log may be incomplete. To filter ?out such jobs, count only the jobs that receive the successful Ecompletion status message. Any of the following may cause the job to terminate abnormally:

STOP /QUEUE /RESET command
Symbiont crash
Printer crash
Network connection lost

9.2 Accounting Information Supplied by the Job Controller

HThe job controller supplies the following information in the accounting file for print jobs:

Username
User name of the user who submitted the print job.G
Account
Account name of the user who submitted the print job.G
UIC (user identification code)
UIC of the user who submitted the print job.H
Process ID
Process ID of the user who submitted the print job.J
Start Time
The time the print job reached the top of the device G queue (not necessarily the time that the print job actually began to print).9
Finish Time
The time the job finished printing.H
Elapsed Time
The wall-clock time it took for the job to print ! (finish time minus start time).3
Priority
Queue priority of the print job.J
Final Status Code
Exit status of the print job. The status code for success is 00040001.H

Queue Entry
Queue entry number. This is the print job number. ) In this example, 222 is the job number:

"
>$ PRINT /QUEUE=LN03R$SCRIPT4 /NOTIFY TEST.MEMD Job TEST (queue LN03R$SCRIPT4, entry 222) started on queue SCRIPT4

4

Queue Name
Name of the print device queue.D
Queue Job
Print job name, as printed on the job flag page.F
Final Status Text = F$MESSAGE
The text for the Final Status 3 code. The text for completion of a normal job is:
"
,%JBC-S-NORMAL, Normal successful completion

]

9.2.1 Accounting Fields Left Blank by the Job Controller

AThe job controller fills the following fields with blanks in the accounting file for print jobs:

Owner ID
Terminal Name
Remote Node Name
Remote ID

9.2.2 Accounting Fields Filled with Zeros by the Job Controller

@The job controller fills the following fields with zeros in the accounting file for print jobs:

Privilege <31--00>
Privilege <63--32>

9.3 Accuracy of DCPS Page Counts

GThe page count reported by DCPS in the accounting file and on the DCPS Atrailer page relies on information returned by the printer. Some Fprinters do not report accurate information, due to different methods for:

Counting pages vs. sides
Some printers count physical sheets 8 of paper, while others count images, or sides printed.H
When pages are counted
Some printers count pages interpreted = by the printer, while others count pages physically output.

DFor the page count reported by DCPS to be correct, the printer must Fcount physical sheets interpreted by the printer. All Compaq, DIGITAL Eand GENICOM printers supported by DCPS, except the following models, Cadhere to this requirement and send the proper information to DCPS.

Compaq Laser Printer LN20
Compaq Laser Printer LN40
Compaq Laser Printer LNC02!
DIGITAL Laser Printer LNC02

CNo other printers, including HP printers, are guaranteed to supply correct accounting information.r

9.4 Compatibility with Mechanical Page Counters

7The PrintServer printers have mechanical page counters.

EThe mechanical page counter is different from the counter accessible ;through the PostScript pagecount operator.

The mechanical page counter counts all the sheets printed since the print engine was built.I
The PostScript page counter counts the number of sheets printed by the controller.

DUnder normal use, the totals of both counters increase at a similar Drate, but there can be a significant difference between them. Print Fengine test pages, initiated with the test button on the printer, are Frecorded on the mechanical counter but not on the PostScript counter. AAlso, replacing components can affect the counters. For example, >replacing the nonvolatile memory of the controller resets the BPostScript counter, but it does not affect the mechanical counter.

FBecause the counters record different events, they should be used for different purposes:

Use the PostScript counter to determine the number of sheets & printed within a PostScript program.;
Use the mechanical counter to track print engine use.

z a d f

Contents

Index

HP DECprint Supervisor (DCPS) for OpenVMSSystem Manager's Guide