Previous | Contents | Index |
These setup modules allow you to manipulate the resolution of PostScript Level 2 printers.
Setup Module | Description |
---|---|
RES_300X300 | 300 dpi horizontal and vertical |
RES_600X300 | 600 dpi horizontal and 300 dpi vertical |
RES_600X600 | 600 dpi horizontal and vertical - default |
RES_1200X600 | 1200 dpi horizontal and 600 dpi vertical |
RES_1200X1200 | 1200 dpi horizontal and vertical |
Not all resolutions are supported by all printers. To have the printer notify you if it cannot print at a specified resolution, add the /NOTIFY switch to the PRINT command. If the printer cannot print at the requested resolution, it prints at a lower resolution. |
There following setup modules invoke DECimage or modify the DECimage parameters. They are grouped into the following categories:
Enabling and Disabling DECimage
These setup modules leave all current parameters intact, and turn DECimage on or off. It is not necessary to use these modules if you use other DECimage setup modules. The DECimage setup modules automatically invoke DECimage for the current print job.
Setup Module | Description |
---|---|
DI_ON | Turns DECimage ON |
DI_OFF | Turns DECimage OFF |
These setup modules adjust two DECimage parameters simultaneously.
Setup Module | Description |
---|---|
DI_HICONTRAST | Punch0 = 0.2, Punch1 = 0.8 |
DI_LOCONTRAST | Punch0 = -.1, Punch1 = 1.1 |
DI_BRIGHTER | Punch0 = -.2, Punch1 = 0.8 |
DI_DARKER | Punch0 = 0.2, Punch1 = 1.2 |
DI_NORMAL | Punch0 = 0, Punch1 = 1 |
When you specify one of these setup modules, all other parameters remain at the default value or the value most recently modified by another setup module. The setup modules have no order dependency, so they may appear in any order on the print command line.
Setup Module | Description |
---|---|
DI_PUNCH0_0 | Punch0 = 0 |
DI_PUNCH0_0P1 | Punch0 = 0.1 |
DI_PUNCH0_0P2 | Punch0 = 0.2 |
DI_PUNCH0_M0P1 | Punch0 = -.1 |
DI_PUNCH0_M0P2 | Punch0 = -.2 |
DI_PUNCH1_1 | Punch1 = 1 |
DI_PUNCH1_0P8 | Punch1 = 0.8 |
DI_PUNCH1_0P9 | Punch1 = 0.9 |
DI_PUNCH1_1P1 | Punch1 = 1.1 |
DI_PUNCH1_1P2 | Punch1 = 1.2 |
DI_SHARP_0P5 | Sharpness = 0.5 |
DI_SHARP_1 | Sharpness = 1.0 |
DI_SHARP_1P5 | Sharpness = 1.5 |
DI_SHARP_2 | Sharpness = 2.0 |
DI_SHARP_2P5 | Sharpness = 2.5 |
The following example adds sharpening and shifts the gray levels:
$ PRINT/NOTIFY/QUEUE=queue/SETUP=(DI_SHARP_2,DI_DARKER) file |
The DCPS software can emulate physical font cartridges. Use the FONTS_USED parameter with the PRINT command to specify one or more soft font modules from the device control library SYS$LIBRARY:CPS$ANSI_FONTS.TLB.
This feature, which is available for ANSI files only, supports documents that require font cartridges to print on DIGITAL ANSI printers. Just as with these printers, the document must contain escape sequences that select the desired fonts.
DCPS software does not include any soft font modules. SoftFont kits have been retired and are no longer available from HP. |
You can associate one or more default soft font modules with a print queue, so that users do not have to specify this parameter on the PRINT command line. For example, to establish CGTRIUM24_ISO1 as the default soft font module for the queue, include the following line in DCPS$STARTUP.COM:
FONTS_USED=CGTRIUM24_ISO1 |
(Add the line to p4 in the execution queue definition or as p3 in the generic queue definition.)
You can combine soft font modules for user convenience, at the expense of disk space and loading time. For example, if users need to load all three DEC Multinational CG Times soft font modules together, create a new module using the following sequence of commands:
$ LIBRARY SYS$LIBRARY:CPS$ANSI_FONTS.TLB/EXTRACT=CGTIMES8-10-12_MCS $ LIBRARY SYS$LIBRARY:CPS$ANSI_FONTS.TLB/EXTRACT=CGTIMES14-18_MCS $ LIBRARY SYS$LIBRARY:CPS$ANSI_FONTS.TLB/EXTRACT=CGTIMES24_MCS $ COPY CGTIMES8-10-12_MCS.TXT,CGTIMES14-18_MCS.TXT,- CGTIMES24_MCS.TXT ALLCGTIMES_MCS.TXT $ LIBRARY/INSERT SYS$LIBRARY:CPS$ANSI_FONTS.TLB ALLCGTIMES_MCS.TXT |
Users can specify the new module with the print parameter
FONTS_USED=ALLCGTIMES_MCS.
7.11 Device Control Library Cache Feature
DCPS includes a device control library caching feature that optimizes the retrieval of certain commonly-used PostScript device control modules.
The caching feature causes modules with names beginning with LPS$$ to be read only the first time they are requested. Those modules reside in the symbiont's cache. Jobs that follow can quickly access those modules until you reset the queue or restart the system. This minimizes access to the primary device control library, saves CPU time, reduces disk activity.
The device control library caching feature is disabled by default. To enable the device control library caching feature for a specific queue, enter the following command before you start a print queue:
$ DEFINE/SYSTEM/EXECUTIVE DCPS$queuename_DEVCTL_CACHE 1 |
Caching device control library modules can decrease the total CPU time consumed 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.
You can define the system logical DCPS$DEVCTL_CACHE (with no queue name
specified) to specify that device control library caching is enabled
for all DCPS print execution queues on that system.
7.12 Printing on Unrecognized Printers
The DCPS software automatically obtains a printer's product name before printing jobs. It uses the product name to select and download device control modules that are specific to the particular printer.
If you use the DCPS software with a printer whose product name it does not recognize, the product name defaults to "HPGENERIC" if it is an HP printer, and "UNRECOGNIZED" if it is not. The supervisor downloads device control modules associated with that name. Although this configuration is unsupported, the modules associated with an "unrecognized" printer may be sufficient to permit simple printing with that device. Printers identified as "generic HP" use commands common to most HP printers and allow additional features such as tray selection and use of the printer's native PCL interpreter.
A system manager can also modify the corresponding device control modules as needed without affecting the characteristics of any of the supported printers. By following the comments contained within the LPS$$UNRECOGNIZED modules, along with some knowledge of PostScript and the specifics of the printer, and examination of device control modules for similarly programmed printers (if any), the system manager may be able to get tray and sheet size selection working for the printer.
Your use of an unrecognized printer with DCPS, and any use or modification of the LPS$$UNRECOGNIZED device control modules, is without support or assistance from Hewlett-Packard Company. Further, HP makes no commitment to maintain the same contents of or interface to these modules for different versions of DCPS. |
Device control modules are located in the following device control library:
SYS$COMMON:[SYSLIB]DCPS$DEVCTL.TLB |
The device control modules associated with an unrecognized printer are:
LPS$$UNRECOGNIZED_INITPSDEVICE LPS$$UNRECOGNIZED_SETCONTEXT LPS$$UNRECOGNIZED_SETINPUTTRAY LPS$$UNRECOGNIZED_SETOUTPUTTRAY |
If you modify these modules for a certain printer, you should always place the modified modules in a site-specific device control library (see Section 7.4).
You can create form definitions, which users can include in their PRINT command to modify the appearance of a file. A form definition can specify several attributes for a print job, including the type of paper stock on which it is to be printed; the width, length, and margins associated with the paper; whether long text lines are to be truncated or 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, DECprint Supervisor informs them immediately. In contrast, if they specify an unknown setup module in their PRINT command, DECprint Supervisor does not inform them of the problem until it starts printing the job and needs to access the setup module.
The commands for creating, maintaining, and deleting forms require that
you have operator privileges.
8.1 Associating Setup Modules with Forms
To associate a setup module with a form, use the DEFINE/FORM command with the /SETUP qualifier.
Example 8-1 defines a form called CONFIDENTIAL that uses a setup module called PRIVATE.
Example 8-1 Sample Form Definition, CONFIDENTIAL |
---|
$ DEFINE/FORM CONFIDENTIAL 101- /DESCRIPTION="prints the word CONFIDENTIAL on each page"- /STOCK=DEFAULT- /SETUP=PRIVATE |
When you define a form, you supply the following qualifiers and information:
The existence of the setup module(s) is not checked until the form is used. |
If users invoke a setup module frequently, you can associate the setup module with a form, then associate the form with a queue. This method ensures that print jobs submitted to the queue automatically use the setup module. Use the following procedure to associate a form with a queue:
$ @SYS$STARTUP:EXECUTION_QUEUE.COM - XLR8- !P1 - Execution queue name "DECNET/XLR8" - !P2 - Device name DCPS_LIB - !P3 - Logical name for /LIBRARY "" - !P4 - Not used "/FORM_MOUNTED=CONFIDENTIAL/DEFAULT=(FORM=CONFIDENTIAL,NOFEED)" !P5 - Queue default qualifiers |
When you define forms for ANSI files, you can use various qualifiers that affect the page layout. For example, the following command defines the form CENTER to have a top margin of 6 and a left margin of 10:
$ DEFINE/FORM /MARGIN=(TOP=6,LEFT=10) CENTER 3 |
You can use the qualifiers in Table 8-1 with form defintions for ANSI files only:
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:
To supply more than one margin keyword, enclose the list in
parentheses, as in:
|
/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 | Wraps lines wider than the page to the next line. |
Notes:
You 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 --------- ------ ----------- A4_12 (stock=PLAIN_PAPER) 1129 A4 12-Pitch with margins A4_LPT_GRAY (stock=PLAIN_PAPER) 1118 A4 DP line printer with gray bars A4_LPT_PLAIN (stock=PLAIN_PAPER) 1119 A4 Plain DP line printer format BOOT_CHART (stock=DEFAULT) 37 BOOT_CHART BSS$LANDSCAPE (stock=DEFAULT) 3301 BSS Specific Landscape BSS$PORTRAIT (stock=DEFAULT) 3302 BSS Specific Portrait |
You can display the attributes of a form using the SHOW QUEUE/FORM/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 /LENGTH=66 /STOCK=DEFAULT /TRUNCATE /WIDTH=80 |
Use the DELETE/FORM command to delete a form definition from the system's form table. The format of this command is as follows:
$ DELETE/FORM form-name |
In the command line, you supply form-name, which is the name assigned to the form you are using.
Before you use the DELETE/FORM command, execute the SHOW QUEUE/FULL/ALL command. References to a form can exist as an attribute of an active print queue or as a qualifier to a print request. If you try to delete a form that has outstanding references, you are notified of the condition, and the form is not deleted. (Refer to Appendix A.)
8.6 Using the Default ANSI Form Definition
If users omit a form definition in their PRINT command, but supply one
of the following qualifiers, DCPS links the default form
definition DCPS$DEFAULT with the ANSI file.
/HEADER
/SPACE
/PARAMETERS=[NO]TAB
Previous | Next | Contents | Index |