l8HP DECprint Supervisor (DCPS) for OpenVMSG

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

z d f

7.4 Creating Device Control Libraries

GTo make the setup module accessible to users, you must create a device Fcontrol library and put the module in the library. Create a different Blibrary for setup modules of each data type. Do not include setup Fmodules of different data types in the same library. You can create a 7library for ANSI, PCL, Proprinter, or PostScript files.

Note

ADo not put your custom setup modules in the standard DCPS$DEVCTL Dlibrary. Custom setup modules in DCPS$DEVCTL will be deleted if you -upgrade DECprint Supervisor software.

HTo create a library for setup modules, use the following command format:

"
U $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]library-name

GYou supply the library-name, the name you give to the library.

GThe following command creates a new PostScript device control library, 2PS1, for your customized PostScript setup modules:

"
C $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PS1

sFor more information, refer to the HP OpenVMS Command Definition, Librarian and Message Utilities Manual.P

7.4.1 Putting Setup Modules in Libraries

@To insert a setup module into a device control library, use the following command format:

"
c $ LIBRARY /INSERT /TEXT SYS$LIBRARY:library-name module-name

:In the command line, you supply the following information:
library-name The name of the library
module-name " The name of the setup module

8The following command puts the PostScript setup module, GCONFIDENTIAL.PS, into your PostScript device control library, PS1.TLB, (and names the setup module CONFIDENTIAL:

"
L $ LIBRARY /INSERT /TEXT SYS$LIBRARY:PS1 CONFIDENTIAL.PS

DThe following command puts the ANSI setup module, A4_PAGE.TXT, into Hyour ANSI device control library, ANSI1.TLB, and names the setup module A4_PAGE:

"
J $ LIBRARY /INSERT /TEXT SYS$LIBRARY:ANSI1 A4_PAGE.TXT

O

7.4.2 Specifying a Library Search List

CIf you have several device control libraries, you need to set up a Bsearch list of the libraries in SYS$STARTUP:DCPS$STARTUP.COM. The Hsearch list specifies which device control libraries to search, and the priority of the libraries.

pExample 7-1 shows a search list of device control libraries.

I
Example 7-1 Search List for Device Control Libraries

"
@ $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB -& _$ DCPS$DEVCTL, -6 _$ "PS1 /DATA_TYPE=POSTSCRIPT", -2 _$ "ANSI1 /DATA_TYPE=ANSI", - _$ PS2

dIn Example 7-1, the software does the following:

Looks in the standard device control library F DCPS$DEVCTL for required setup modules and for any > setup modules that have been specified with /SETUP or /FORM.C
Looks in the PostScript library PS1 for any C specified setup modules not found in the standard device control H library. (PostScript setup modules can be used with any type of file, E so the PostScript device control library is always included in the search for a setup module.)<
If the print job is ANSI, looks in the library called ANSI1.H
If the print job is a data type other than ANSI, skips the ANSI1 J library and looks for it in the PostScript library PS2.

ATo define your library logical name and search list, perform the following steps:

Edit DCPS$STARTUP.COM and replace the line:
"
: $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB DCPS$DEVCTL
with the lines:
"
O $ DEFINE /EXECUTIVE_MODE /SYSTEM logical-name search-list
C
In the command line, you supply the following information: L
logical-name: Use a logical name that expands to a J list of library names. Make sure the logical name also appears in the @ execution queue definition (parameter P3). F
search-list: Add the list of libraries to be @ searched. Use the following guidelines as you add libraries:
- Place the standard device control library, DCPS$DEVCTL, first in D the list for most efficient printing.
  If you do not include K DCPS$DEVCTL in the library search list, the symbiont stops and returns the following error message:
  "
  R REQMODNOTFOUND, Required device control module module-name not found
  ;
- Make sure all the library names are in SYS$LIBRARY.F
- Make sure all the library names have the file extenstion .TLB.I
- For each library that includes the /DATA_TYPE qualifier, enclose I the library name and the qualifier in quotation marks. If you do not I use the /DATA_TYPE qualifier, you do not need to enclose the library D name in quotation marks. The default data type for a library is PostScript.L
- If an ANSI module and a PostScript module perform the same function L and have the same name, determine which one you want as the default for I ANSI jobs.
  If you want ANSI jobs to default to PostScript, place J the PostScript device control library before the ANSI library. If you J want ANSI jobs to default to ANSI, place the ANSI library in front of the PostScript library.
H
Stop and restart the execution queue to include your new library. H (If you add a setup module to an existing library, you do not have to reinitialize the queue.)

DFor example, to add PostScript libraries called PS1 and PS2, and an !ANSI library called ANSI1, enter:

"
= $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB DCPS$DEVCTL, - & "PS1 /DATA_TYPE=POSTSCRIPT", - " "ANSI1 /DATA_TYPE=ANSI", - PS2

j

7.4.3 Device Control Libraries Must Exist for Queue to Start

FAll device control libraries specified for a queue must exist for the Fqueue to start. For example, if a queue is defined with the following 4logical, the libraries SYS$LIBRARY:DCPS$DEVCTL.TLB, CSYS$LIBRARY:ANSI.TLB and SYS$LIBRARY:PS.TLB must all exist as text libraries:

"
@ $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS_LIB -& _$ DCPS$DEVCTL, -1 _$ "ANSI /DATA_TYPE=ANSI", -2 _$ "PS /DATA_TYPE=POSTSCRIPT"

^

7.4.4 Preserving Custom Setup Modules During Upgrades

KWhen you install DECprint Supervisor software, it creates a new version of Ethe standard device control library (DCPS$DEVCTL.TLB). If you purged Gold files during the software installation, early copies of the device }control library are deleted. (Refer to the Software Installation GuideSoftware Installation Guide for more information.)

HWhen you add custom setup modules, create a new library and refer to it Ein the library search list. This preserves your custom setup modules when you upgrade your software.

|Upgrading from DECprint Printing Services or PrintServer Client Software

DDECprint Printing Services software and PrintServer Client software <have their own device control libraries (CPS$DEVCTL.TLB and LLPS$DEVCTL.TLB). When you upgrade to DECprint Supervisor, the CPS$ and LPS$ Fdevice control libraries are no longer used. If you have custom setup Cmodules in either of those libaries, insert the modules into a new Elibrary and specify the library in the device control library search list.h

7.5 Including Setup Modules in Print Job

FYou can specify setup modules using the /SETUP qualifier in the PRINT command.

@To include an ANSI setup module in a print job using the /SETUP ,qualifier, use the following command format:

"
k $ PRINT /QUEUE=queue-name /SETUP=module-name print-file.TXT

DIf you enter the command wrong, the error is not detected until the Efile prints. To enable the software to detect the error immediately, oyou can include the setup module in a form. See Chapter 8 for instructions.

GIf users access a setup module frequently, you can associate the setup Hmodule with a queue, so that all print jobs submitted to that queue are pprinted with the setup module automatically. See Chapter 8 for instructions.d

7.6 Persistently Loading PostScript Resources

Note

HThis feature applies only to desktop printers; PrintServer printers are Hloaded with persistent resources using the PrintServer software.

FDownloading PostScript code with every print job can adversely affect Eprinting performance. To resolve this problem, you can load a module (that permanently resides in the printer.

BThe module LPS$PERSISTENT_RESOURCES loads persistently to desktop Gprinters. To create a persistent PostScript module, follow these steps:

Create a new device control library for site-specific PostScript - setup modules, using the following command:
"
L $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]library-name
D
Edit the SYS$STARTUP:DCPS$STARTUP.COM file to include the new J device control library in the search list. Use the following command in the DCPS startup file:
"
g $ DEFINE /SYSTEM /EXECUTIVE /NOLOG DCPS_LIB DCPS$DEVCTL, "library-name /DATA=POST"
G
In the execution queue definition for each PostScript printer to H which you want to load the setup module, ensure that the logical name G DCPS_LIB is entered in parameter 3 as the device control search list logical name.%
Save the DCPS$STARTUP.COM file.I
Stop the queues for the printers affected by the change, using the , STOP /QUEUE /RESET command for each queue.,
Execute the new DCPS$STARTUP.COM file.J
Test each print queue by sending two print jobs to the printer. The G setup module is loaded with the first print job sent to the printer. D The setting should be effective for the second print job, as well.

CAUTION

DProblems can occur from the misuse of the persistent setup feature. 3Keep the following in mind when using this feature:

Only PostScript setup modules can be persistently loaded. Other + data types cannot be persistently loaded.H
A setup module can exceed the printer's virtual memory. Different E models of printers have different capacities. For example, a setup 5 module can overwhelm a printer with too many fonts.E
A shared network printer can be used from several nodes in the H network. Make sure the same setup module is loaded from all the nodes E that access the printer to ensure consistent print results. If you I required different setup modules load the setup module with each print 2 job, using either the /SETUP or /FORM qualifier.H
Improper PostScript coding in a persistently loaded setup module D can cause unexpected results that are difficult to analyze. Also, F because the code remains in the printer until the printer is turned B off, users from different systems may have print jobs fail with J unexpected results, but would not be able to determine the cause of the problem.

–

7.7 Changing the Default Character Set for PCL and Proprinter Print Jobs

@The default character set for PCL files is Roman-8. The default Fcharacter set for Proprinter files is code page 437, character set 1. ATo change the default character set, use the following procedure:

Create one device control library for PCL setup modules, one for J Proprinter modules, and another library for PostScript modules. Use the following commands:

"
G $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PCL_LIB G $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PRO_LIB F $ LIBRARY /CREATE /TEXT SYS$COMMON:[SYSLIB]PS_LIB

D

Edit DCPS$STARTUP.COM to include these libraries, as follows:
"
D $ DEFINE /EXECUTIVE_MODE /SYSTEM /NOLOG DCPS_LIB DCPS$DEVCTL, - "PCL_LIB /DATA=PCL", - "PRO_LIB /DATA=PRO", - PS_LIB
K
The PostScript device control library (PS_LIB) must be last in the search list.)
Create the following setup modules:
- The DEF_CHAR_SET.PCL file selects the PC-8 Danish/Norwegian character set:
  "
  6 <ESC>!`1P<ESC>(11U<ESC>!`0P
  F
  Replace <ESC> with the escape character (decimal 27).8
- The DEF_CHAR_SET.PRO file selects code page 850:
  "
  A <ESC>`<ETX><NUL><CR>R<ETX>
  - Replace <ESC> with the escape character (decimal 27).A
  - Replace <ETX> with the etx character (decimal 3).B
  - Replace <NUL> with the null character (decimal 0).M
  - Replace <CR> with the carriage return character (decimal 13).
  H
- The DEF_CHAR_SET.PS PostScript file is used for printing files ( that are neither PCL nor Proprinter.
F

Put these modules in the appropriate device control libraries, > using the LIBRARY command as shown in the following example:

"
X $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PCL_LIB DEF_CHAR_SET.PCL X $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PRO_LIB DEF_CHAR_SET.PRO V $ LIBRARY /INSERT /TEXT SYS$COMMON:[SYSLIB]PS_LIB DEF_CHAR_SET.PS

G

Create a form definition that includes DEF_CHAR_SET as the setup H module. You can associate this form with your printer execution queue as follows:
"
h $ DEFINE /FORM DEF_CHAR_SET form-number /SETUP=DEF_CHAR_SET /STOCK=DEFAULT
I
To make this change to the queue permanent, specify this form in @ the execution queue definition in the DCPS$STARTUP.COM file.

7.8 Specifying Printer Resolution with Setup Module

>These setup modules allow you to manipulate the resolution of PostScript Level 2 printers.

d ' &
Table 7-1 Printer Resolution Setup Modules
Setup Module Description
RES_300X300 & 300 dpi horizontal and vertical
RES_600X300 . 600 dpi horizontal and 300 dpi vertical
RES_600X600 0 600 dpi horizontal and vertical - default
RES_1200X600 / 1200 dpi horizontal and 600 dpi vertical
RES_1200X1200 ' 1200 dpi horizontal and vertical

**Table 7-1 Printer Resolution Setup Modules**
Setup Module	Description
RES_300X300	& 300 dpi horizontal and vertical
RES_600X300	. 600 dpi horizontal and 300 dpi vertical
RES_600X600	0 600 dpi horizontal and vertical - default
RES_1200X600	/ 1200 dpi horizontal and 600 dpi vertical
RES_1200X1200	' 1200 dpi horizontal and vertical

Note

GNot all resolutions are supported by all printers. To have the printer Anotify you if it cannot print at a specified resolution, add the H/NOTIFY switch to the PRINT command. If the printer cannot print at the >requested resolution, it prints at a lower resolution.

7.9 Modifying DECimage Parameters with Setup Modules

EThere following setup modules invoke DECimage or modify the DECimage ;parameters. They are grouped into the following categories:

@Enabling and Disabling DECimage

BThese setup modules leave all current parameters intact, and turn HDECimage on or off. It is not necessary to use these modules if you use Gother DECimage setup modules. The DECimage setup modules automatically .invoke DECimage for the current print job.

d ' &
Table 7-2 Enabling and Disabling DECimage
Setup Module Description
DI_ON Turns DECimage ON
DI_OFF Turns DECimage OFF

**Table 7-2 Enabling and Disabling DECimage**
Setup Module	Description
DI_ON	Turns DECimage ON
DI_OFF	Turns DECimage OFF

4Combined Parameters

FThese setup modules adjust two DECimage parameters simultaneously.

q ' &
Table 7-3 DECimage Setup Modules---Combined Parameters
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

**Table 7-3 DECimage Setup Modules---Combined Parameters**
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

7Individual Parameters

BWhen you specify one of these setup modules, all other parameters Cremain at the default value or the value most recently modified by Eanother setup module. The setup modules have no order dependency, so ;they may appear in any order on the print command line.

t ' &
Table 7-4 DECimage Setup Modules---Individual Parameters
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

**Table 7-4 DECimage Setup Modules---Individual Parameters**
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

HDECimage Setup Module Example

AThe following example adds sharpening and shifts the gray levels:

"
p $ PRINT /NOTIFY /QUEUE=queue-name /SETUP=(DI_SHARP_2,DI_DARKER) file-name

r

7.10 Providing Access to Font Cartridge Emulation

@The DCPS software can emulate physical font cartridges. Use the HFONTS_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 Hprinters. Just as with these printers, the document must contain escape (sequences that select the desired fonts.

Note

DDCPS software does not include any soft font modules. SoftFont kits >have been retired and are no longer available from HP.

EYou can associate one or more default soft font modules with a print Hqueue, so that users do not have to specify this parameter on the PRINT Fcommand 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

G(Add the line to P4 in the execution queue definition ;or as P3 in the generic queue definition.)

GYou can combine soft font modules for user convenience, at the expense Gof disk space and loading time. For example, if users need to load all Fthree DEC Multinational CG Times soft font modules together, create a 4new module using the following sequence of commands:

"
[ $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES8-10-12_MCS Y $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES14-18_MCS V $ LIBRARY /TEXT SYS$LIBRARY:CPS$ANSI_FONTS /EXTRACT=CGTIMES24_MCS ] $ COPY CGTIMES8-10-12_MCS.TXT, CGTIMES14-18_MCS.TXT, CGTIMES24_MCS.TXT -* _$ ALLCGTIMES_MCS.TXT Z $ LIBRARY /INSERT /TEXT SYS$LIBRARY:CPS$ANSI_FONTS ALLCGTIMES_MCS.TXT

:Users can specify the new module with the print parameter FONTS_USED=ALLCGTIMES_MCS.

z a d f

Contents

Index

library-name	The name of the library
module-name	" The name of the setup module

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

7.4 Creating Device Control Libraries

7.4.1 Putting Setup Modules in Libraries

7.4.2 Specifying a Library Search List

7.4.3 Device Control Libraries Must Exist for Queue to Start

7.4.4 Preserving Custom Setup Modules During Upgrades

7.5 Including Setup Modules in Print Job

7.6 Persistently Loading PostScript Resources

7.7 Changing the Default Character Set for PCL and Proprinter Print Jobs

7.8 Specifying Printer Resolution with Setup Module

7.9 Modifying DECimage Parameters with Setup Modules

7.10 Providing Access to Font Cartridge Emulation

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