l8HP DECprint Supervisor (DCPS) for OpenVMSG

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

z d f

3.5.8 Suppressing Unsolicited PJL Messages

DPrinters sometimes send out unsolicited PJL messages that DCPS then Ddisplays on the screen as user data. This can be caused by previous <print jobs from other operating systems that change printer Hcharacteristics so that all future jobs send back these messages. While Ethese messages are often harmless, sometimes they can interfere with #DCPS communications to the printer.

GSometimes, the PJL messages can interfere with DCPS and cause the DCPS Bjob to stall and never print. For this reason, you can define two Hlogical names to suppress PJL messages from being sent from the printer.

"
i $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_SUPPRESS_PJL_MESSAGES TRUEU $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$SUPPRESS_PJL_MESSAGES TRUE

EThe recommended method for suppressing PJL messages is to define the Elogical name DCPS$queue-name_SUPPRESS_PJL_MESSAGES for each Equeue having the problem. For example, to suppress PJL messages on a queue called HP4200:

"
\ $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$HP4200_SUPPRESS_PJL_MESSAGES TRUE

GYou can suppress PJL messages on all DCPS queues with the logical name FDCPS$SUPPRESS_PJL_MESSAGES, but you should use this logical name with Hcaution. Defining the logical name causes DCPS to send the PJL commands Dto the printer to suppress PJL messages. Since some printers do not Esupport PJL commands, defining the logical name for such queues will Ecause the printer to hang and the job to stall. If you are unsure if Dall your printers support PJL commands, define the logical name for individual queues.

AYou do not need to stop and restart the queue after defining the logical name.

Note

BThese new logical names replace the unsupported command procedure CUNSOLICITED-PJL-FIX.COM and provide improved functionality.

3.5.9 Suppressing the OPCOM Message USERNOTFOUND

EIf DCPS is running on an OpenVMS cluster that has more than one User EAuthorization file (UAF), it is possible the user submitting a print Ejob does not have a UAF record on the system running the DCPS queue. ?DCPS prints the job but issues a USERNOTFOUND operator message:

"
= %%%%%%%%%%% OPCOM 1-JUN-2005 18:43:55.87 %%%%%%%%%%% ' Message from user SYSTEM on LITERA V Queue SHARIE: %DCPS-W-USERNOTFOUND, user name FOO not found, no log files created ! -RMS-E-RNF, record not found

=Because the username cannot be found, DCPS cannot perform theMESSAGES=KEEP orMESSAGES=PRINT parameter request.

BTo prevent this OPCOM message from being displayed for every job, Ddefine one of the following logical names, depending on whether you >want the message suppressed for one print queue or all queues:

"
g $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_IGNORE_UNKNOWN_USER TRUES $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$IGNORE_UNKNOWN_USER TRUE

l

3.5.10 Using Old ANSI Translator Page Size for A4 Landscape

G All versions of the ANSI translator prior to DCPS V1.1A had a problem B printing 66 lines of text in landscape mode on A4 paper. Certain G printers have slightly smaller than average print areas when using A4 I paper, which resulted in the 66th line being lost or clipped when using print parameters of0PAGE_SIZE=A4,PAGE_ORIENTATION=LANDSCAPE.

H The ANSI translator now correctly prints 66 lines of text in landscape I mode on A4 paper. The fix involved changing the vertical spacing of the E font used (SGR 15) and correcting the maximum printable area for A4 paper.

@If you use preprinted forms that depend on the old translator's Ebehavior, you can retain the old behavior by defining a DCPS logical name:

"
g $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queue-name_OLD_ANSI_PAGE_SIZES TRUE

`

3.6 Setting Up Generic Queues

HGeneric queues are not associated with a specific printer; rather, they Epoint to the execution queues. Generic queues can be associated with Bmore than one execution queue and can distribute print jobs among Fqueues, or they can be used to associate specific DECprint Supervisor }functions with a print job. Generic queues are optional. Table 3-5 Cdescribes the parameters that can be used to define a generic DCPS queue.

u $
Table 3-5 Parameter Values for Generic Queues
Parameter Value
$ P1 (required) Name of the generic queue.P
In Example 3-4,K DRAFT_DOCS is the generic queue to which users will send print jobs.
$ P2 (required) I Name of the execution queue(s) to which the generic queue can send G jobs. You must supply at least one execution queue name for each generic queue definition.
In Example 3-4, the generic queue will send print jobs to two execution queues:% LN03R_TTB4 and" LN03R_TTB7.
$ P3 (optional) Default PRINT parameters.O
In Example 3-4,F LAYUP=LPS$SINGLEHOLES provides a default layup , definition file for the generic queue.
$ P4 (optional) - Explicit INITIALIZE /QUEUE qualifiers.
$ P5 (optional) E Setting of the SET VERIFY command. The default is SET NOVERIFY.

**Table 3-5 Parameter Values for Generic Queues**
Parameter	Value
$ P1 (required)	Name of the generic queue.P In Example 3-4,K DRAFT_DOCS is the generic queue to which users will send print jobs.
$ P2 (required)	I Name of the execution queue(s) to which the generic queue can send G jobs. You must supply at least one execution queue name for each generic queue definition. In Example 3-4, the generic queue will send print jobs to two execution queues:% LN03R_TTB4 and" LN03R_TTB7.
$ P3 (optional)	Default PRINT parameters.O In Example 3-4,F LAYUP=LPS$SINGLEHOLES provides a default layup , definition file for the generic queue.
$ P4 (optional)	- Explicit INITIALIZE /QUEUE qualifiers.
$ P5 (optional)	E Setting of the SET VERIFY command. The default is SET NOVERIFY.

{Example 3-4 shows how to set up a generic queue for printing with a Hlayup definition file. This generic queue feeds print jobs to either of #two ScriptPrinter execution queues.

I
Example 3-4 Setting Up a Generic Queue

"
$$ @SYS$STARTUP:DCPS$GENERIC_QUEUE - K DRAFT_DOCS - ! P1 - Generic queue name P "LN03R_TTB4,LN03R_TTB7" - ! P2 - Execution queue name(s) Q "LAYUP=LPS$SINGLEHOLES" ! P3 - Default queue parameters

p

3.7 Activating Changes to the Queue Definitions

GWhen you create or modify the DCPS$STARTUP.COM file, you must activate Nthe changes for the DECprint Supervisor to use the new queue definitions. You Gcan wait until you stop and restart the system, or you can execute the "DCPS$STARTUP.COM file, as follows:

Stop the print queues that you modified. If any of the modified H queues are running on a multistreamed symbiont, stop all other queues ~ that are using that same symbiont (see Section 3.5.1.2). To stop the ; queues, enter the following command for each print queue:
"
< $ STOP /QUEUE /NEXT queue-name
A
Edit the system startup file SYS$MANAGER:SYSTARTUP_VMS.COMEto include a command that invokes DCPS$STARTUP.COM.
Look for the -following command in the system startup file:
"
$ @SYS$STARTUP:DCPS$STARTUP
I
If this command is not in the system startup file, add it to the ' file. Use the following guidelines:
- If you are using a printer with TCP/IP, add the new line after TCP/IP is started.K
- If you are using a printer with LAT, add the new line after LAT is started.J
- If you are using a printer with AppleTalk, add the new line after AppleTalk is started.H
- If you are using a PrintServer printer with DECnet, add the new H line after the command to invoke STARTNET.COM. PrintServer Software H must be running on the PrintServer host system before you start the queues.>
- If the system startup file includes a command to start
  GLPS$STARTUP.COM, replace it with the command to start DCPS$STARTUP.COM.L
- If you are upgrading from DECprint Printing Services (CPS), delete F the command to start CPS$STARTUP.COM from the system startup file.
/
Execute the printer startup command file:
"
0 $ @SYS$STARTUP:DCPS$STARTUP

GIf the queues are on an OpenVMS Cluster system, you should execute the ,command above from all nodes in the cluster.

FThe print queues are started by the printer startup command file. See wSection 3.8 for information on testing your new queue definitions._

3.8 Testing the Printing System

Note

Execution of the IVP (@SYS$TEST:DCPS$IVP+) does not cause anything to print.

@You can test the printing system by printing the IVP files from FSYS$COMMON:[SYSTEST.DCPS]. The IVP files represent the different data wtypes that DCPS supports. The IVP files are listed in Table 3-6.

n $ $
Table 3-6 IVP Files with Different Data Types
File Name File Type
DCPS$IVP_ANSI.DAT ASCII files
DCPS$IVP_LIST.DAT Simple ASCII
DCPS$IVP_PCL.DAT PCL Level 4 files
DCPS$IVP_POST.DAT PostScript files
DCPS$IVP_PROPRINTER.DAT Proprinter files
DCPS$IVP_REGIS.DAT ReGIS files
DCPS$IVP_TEK4014.DAT Tektronix 4010/4014 files

**Table 3-6 IVP Files with Different Data Types**
File Name	File Type
DCPS$IVP_ANSI.DAT	ASCII files
DCPS$IVP_LIST.DAT	Simple ASCII
DCPS$IVP_PCL.DAT	PCL Level 4 files
DCPS$IVP_POST.DAT	PostScript files
DCPS$IVP_PROPRINTER.DAT	Proprinter files
DCPS$IVP_REGIS.DAT	ReGIS files
DCPS$IVP_TEK4014.DAT	Tektronix 4010/4014 files

GDCPS can automatically detect the file's data type. You do not have to Fspecify the data type on the command line. For example, you can enter the following PRINT command:

"
] $ PRINT/QUEUE=queue-name/NOTIFY DCPS$IVP_data-type.DAT

AIf the print queue is linked to a specific data type, or you are >testing the LIST data type, specify the data type of the file.

AFor example, to print DCPS$IVP_POST.DAT, use the following PRINT command:

"
9 $ PRINT /QUEUE=queue-name -B _$ /PARAMETERS=DATA_TYPE=POSTSCRIPT /NOTIFY -B _$ SYS$COMMON:[SYSTEST.DCPS]DCPS$IVP_POST.DAT

Chapter 4
Providing Automatic Data Type Detection

KDECprint Supervisor software can determine the data type of the file to be Cprinted. This chapter explains how you can customize your printing <system to print the types of files that users need to print.o

4.1 How DCPS Automatically Detects Data Type

DIf a user does not specify the data type and the print queue has no Bdefault data type, DCPS examines each file in the print job. DCPS Eattempts to determine the data type of the file from instructions in *the file, or from the file name extension.

NIf DECprint Supervisor software cannot determine the file data type by any of Bthese methods, the file is printed as a text file. Text files are Fhandled as ANSI files unless another default text file data type (PCL Gor Proprinter) has been defined by the system manager for the queue or for the system.

JWhen files are treated as text files in this way, the DECprint Supervisor Csoftware can detect PostScript data after the text, so a file that <starts with text followed by PostScript is printed properly.

HThe process of determining the file data type is repeated for each file Ein a print job, so a single print job can contain different types of files.u

4.2 Specifying Automatic Data Type Detection

NYou can control how the DECprint Supervisor software determines the data type &of files as they are printed. You can:

Link file extensions with data types. You can edit the default F file extension data file to add or modify the standard list of file B extensions and the data types to which they are associated. See E Section 4.2.1.G
Specify the default data type to use when DCPS cannot determine G the file's data type in any other way. You can specify a system wide y default and a queue-specific default text data type. See Section 4.2.2.

CIf necessary, you can create generic queues that have default data Gtypes, so that every file sent to the queue is assumed to be that data Ftype. Only the user's PRINT parameters can override the queue default data type.S

4.2.1 Linking File Extensions with Data Types

MThe DECprint Supervisor software uses a data file to link file extensions to Gdata types. Use the following procedure to create a local data file of <your system's file extensions and the associated data types.

If your system does not have a customized data file, use the sample I file supplied with your software. Copy the file, and change the file's / extension, as shown in the following command:
"
$ COPYM_From: SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT J_To: SYS$COMMON:[SYSLIB]DCPS$FILE_EXTENSION_DATA_TYPE.DAT
J
If the .DAT file is not in variable or stream format, DCPS cannot J read it when the queues are started. OPCOM will report the error, and J the symbiont process may be terminated. You should save the .DAT file J in the appropriate format, and then restart the printing system using # the DCPS$STARTUP.COM file.
F
Edit the file. The file has the default file extension and data types listed. For example:
"
POSTSCRIPT: EPS EPSF POST PS ;
L
The example shows that files with extensions of .EPS, .EPSF, .POST, L and .PS are linked to the PostScript data type.
Add extensions that I are specific to your site, or modify any that have a different local C meaning.
You can specify any valid DATA_TYPE value, except J AUTOMATIC. Do not abbreviate the data type names. The valid data type names are:
ANSI
ASCII
DDIF
LIST
PCL
POSTSCRIPT
PROPRINTER
REGIS
TEK4014

4.2.2 Specifying Default Data Types for the System and Queues

HYou can specify a system wide default text data type and queue-specific Ddefault text data types. If DCPS software cannot determine the data Atype, the file is processed as the default data type you specify.

GThe factory default data type is ANSI. If users regularly print PCL or CProprinter text files instead of ANSI files, you should change the 'default from ANSI to PCL or Proprinter.

2Define one or both of the following logical names:

DCPS$DEFAULT_TRANSLATOR specifies the system wide default text data D type.
To define a system wide default text data type, use the following command:
"
Z$ DEFINE/SYSTEM/EXECUTIVE DCPS$DEFAULT_TRANSLATOR text_data_type
?
DCPS$queuename_DEFAULT_TRANSLATOR specifies the C queue-specific default data type.
To define a queue-specific 4 default text data type, use the following command:
"
m$ DEFINE/SYSTEM/EXECUTIVE DCPS$queuename_DEFAULT_TRANSLATOR text-data-type

1Valid values for the text-data-type are:

ANSI (the default)
PCL
PROPRINTER

%Do not abbreviate the data type name.

HIf the system wide data type differs from the queue-specific data type, .the queue-specific data type takes precedence.

BThe queue-specific logical name is useful when a queue is used by HPATHWORKS clients. Text files printed from PCs may be PCL or Proprinter Gfiles. The following example specifies the PCL data type for the queue named PATHWORKS:

"
P$ DEFINE/SYSTEM/EXECUTIVE DCPS$PATHWORKS_DEFAULT_TRANSLATOR PCL

NThe DECprint Supervisor software attempts to determine the file data type for Eeach file sent to the PATHWORKS queue. If a file data type cannot be Fdetermined, the file is processed as a PCL file. If the file contains 8PCL text followed by PostScript, it is printed properly.X

4.2.3 How Users Control Data Type Detection

GUsers control the way print jobs are processed for automatic data type detection by specifying:

The data type with the /PARAMETERS=DATA_TYPE qualifier in the PRINT J command.
This qualifier overrides the automatic data type detection I process; only the presence of DDIF file tags can prevent the file from J being processed using the translator associated with the specified data F type. If the file contains DDIF tags and is explicitly specified as J another data type, the file is not printed. The following error message M is displayed, and the DECprint Supervisor software continues with the next ! file in the print job (if any):
"
8INVDDIFDATA, Invalid DDIF data, flushing to end of file
G
Automatic data type detection with the following PRINT parameter:
"
:/PARAMETERS=DATA_TYPE=AUTOMATIC[=text-data-type]
K
Users can specify the /PARAMETERS=DATA_TYPE=AUTOMATIC qualifier to K specify automatic data type detection (for example, if the print queue H has a default data type).
If the user includes the default text C data type (text-data-type) in the DATA_TYPE=AUTOMATIC P parameter, the DECprint Supervisor software assumes the specified data type C if the data type of a print file cannot be determined.
The J text-data-type value is optional; the default is ANSI. Users I should include this value to specify another text data type, such as R PCL or Proprinter.
The DECprint Supervisor software can print a file that K starts with the default text data type followed by PostScript data. If G a user needs to print a file that begins with PCL text followed by L PostScript data, the user can explicitly set the default text data type 0 to be PCL using the following PRINT command:
"
T$ PRINT/QUEUE=PS20$A10 PIC.MSG/PARAMETERS=(DATA_TYPE=AUTOMATIC=PCL)
J
This feature is useful for printing files generated by electronic I messaging systems. For example, you can print a PostScript file that D was sent to you from someone using the messaging system, if the I resulting file contains a text message header followed by PostScript data.

z a d f

Contents

Index

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

3.5.8 Suppressing Unsolicited PJL Messages

3.5.9 Suppressing the OPCOM Message USERNOTFOUND

Chapter 4Providing Automatic Data Type Detection

4.2.2 Specifying Default Data Types for the System and Queues

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

Chapter 4
Providing Automatic Data Type Detection