Previous | Contents | Index |
The DCPS symbiont purges its working set after it has been idle for a period of time in order to conserve system resources. The time delay is intended to help prevent the system from thrashing by keeping the program in physical memory while more work is apt to arrive.
By default, DCPS waits ten (10) minutes after becoming idle before purging its working set. You can increase this value, if desired, by defining a system-wide logical name:
$ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$PURGE_TIME "0 hh:mm:ss.00" |
where hh:mm:ss.00 is an OpenVMS delta-time value specifying
the desired time delay. If the value is less than the default of ten
seconds, the default is used.
3.4.5 Suppressing the OPCOM Message USERNOTFOUND
If DCPS is running on an OpenVMS cluster that has more than one User Authorization file (UAF), it is possible the user submitting a print job 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-MAR-2002 18:43:55.87 %%%%%%%%%%% Message from user SYSTEM on LITERA Queue SHARIE: %DCPS-W-USERNOTFOUND, user name FOO not found, no log files created -RMS-E-RNF, record not found |
To prevent this OPCOM message from being displayed for every job, define one of the following logical names, depending on whether you want the message suppressed for one print queue or all queues:
$ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queuename_IGNORE_UNKNOWN_USER TRUE $ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$IGNORE_UNKNOWN_USER TRUE |
All versions of the ANSI translator prior to DCPS V1.1A had a problem printing 66 lines of text in landscape mode on A4 paper. Certain printers have slightly smaller than average print areas when using A4 paper, which resulted in the 66th line being lost or clipped when using print parameters of PAGE_SIZE=A4,PAGE_ORIENTATION=LANDSCAPE .
The ANSI translator now correctly prints 66 lines of text in landscape mode on A4 paper. The fix involved changing the vertical spacing of the 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 behavior, you can retain the old behavior by defining a DCPS logical name:
$ DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$queuename_OLD_ANSI_PAGE_SIZES TRUE |
Generic queues are not associated with a specific printer; rather, they point to the execution queues. Generic queues can be associated with more than one execution queue and can distribute print jobs among queues, or they can be used to associate specific DECprint Supervisor functions with a print job. Generic queues are optional.
Example 3-3 shows how to set up a generic queue for printing with a layup definition file. This generic queue feeds print jobs to either of two ScriptPrinter execution queues.
Example 3-3 Setting Up a Generic Queue |
---|
$ @SYS$STARTUP:DCPS$GENERIC_QUEUE - DRAFT_DOCS - ! P1 - Generic queue name "LN03R_TTB4,LN03R_TTB7" - ! P2 - Execution queue name(s) "LAYUP=LPS$SINGLEHOLES" ! P3 - Default queue parameters |
Parameter | Value |
---|---|
P1 (required) |
Name of the generic queue.
In Example 3-3, DRAFT_DOCS is the generic queue to which users will send print jobs. |
P2 (required) |
Name of the execution queue(s) to which the generic queue can send
jobs. You must supply at least one execution queue name for each
generic queue definition.
In Example 3-3, the generic queue will send print jobs to two execution queues: LN03R_TTB4 and LN03R_TTB7. |
P3 (optional) |
Default PRINT parameters.
In Example 3-3, LAYUP=LPS$SINGLEHOLES provides a default layup definition file for the generic queue. |
P4 (optional) | Explicit INITIALIZE/QUEUE qualifiers. |
P5 (optional) | Setting of the SET VERIFY command. The default is SET NOVERIFY. |
When you create or modify the DCPS$STARTUP.COM file, you must activate the changes for the DECprint Supervisor to use the new queue definitions. You can wait until you stop and restart the system, or you can execute the DCPS$STARTUP.COM file, as follows:
$ STOP /QUEUE /NEXT queuename |
$ @SYS$STARTUP:DCPS$STARTUP |
$ @SYS$STARTUP:DCPS$STARTUP |
If the queues are on a VMScluster system, you should execute the command above from all nodes in the cluster.
The print queues are started by the printer startup command file. See
Section 3.7 for information on testing your new queue definitions.
3.7 Testing the Printing System
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 SYS$COMMON:[SYSTEST.DCPS]. The IVP files represent the different data types that DCPS supports. The IVP files are listed in Table 3-4.
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 |
DCPS can automatically detect the file's data type. You do not have to specify the data type on the command line. For example, you can enter the following PRINT command:
$ PRINT/QUEUE=queuename/NOTIFY DCPS$IVP_data-type.DAT |
If 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.
For example, to print DCPS$IVP_POST.DAT, use the following PRINT command:
$ PRINT /QUEUE=queuename - /PARAMETERS=DATA_TYPE=POSTSCRIPT /NOTIFY - SYS$COMMON:[SYSTEST.DCPS]DCPS$IVP_POST.DAT |
DECprint Supervisor software can determine the data type of the file to be
printed. This chapter explains how you can customize your printing
system to print the types of files that users need to print.
4.1 How DCPS Automatically Detects Data Type
If a user does not specify the data type and the print queue has no default data type, DCPS examines each file in the print job. DCPS attempts to determine the data type of the file from instructions in the file, or from the file name extension.
If DECprint Supervisor software cannot determine the file data type by any of these methods, the file is printed as a text file. Text files are handled as ANSI files unless another default text file data type (PCL or Proprinter) has been defined by the system manager for the queue or for the system.
When files are treated as text files in this way, the DECprint Supervisor software can detect PostScript data after the text, so a file that starts with text followed by PostScript is printed properly.
The process of determining the file data type is repeated for each file
in a print job, so a single print job can contain different types of
files.
4.2 Specifying Automatic Data Type Detection
You can control how the DECprint Supervisor software determines the data type of files as they are printed. You can:
If necessary, you can create generic queues that have default data
types, so that every file sent to the queue is assumed to be that data
type. Only the user's PRINT parameters can override the queue default
data type.
4.2.1 Linking File Extensions with Data Types
The DECprint Supervisor software uses a data file to link file extensions to data types. Use the following procedure to create a local data file of your system's file extensions and the associated data types.
$ COPY _From: SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT _To: SYS$COMMON:[SYSLIB]DCPS$FILE_EXTENSION_DATA_TYPE.DAT |
POSTSCRIPT: EPS EPSF POST PS ; |
ANSI
ASCII
DDIF
LIST
PCL
POSTSCRIPT
PROPRINTER
REGIS
TEK4014
You can specify a system wide default text data type and queue-specific default text data types. If DCPS software cannot determine the data type, the file is processed as the default data type you specify.
The factory default data type is ANSI. If users regularly print PCL or Proprinter text files instead of ANSI files, you should change the default from ANSI to PCL or Proprinter.
Define one or both of the following logical names:
$ DEFINE/SYSTEM/EXECUTIVE DCPS$DEFAULT_TRANSLATOR text_data_type |
$ DEFINE/SYSTEM/EXECUTIVE DCPS$queuename_DEFAULT_TRANSLATOR text-data-type |
Valid values for the text-data-type are:
Do not abbreviate the data type name.
If the system wide data type differs from the queue-specific data type, the queue-specific data type takes precedence.
The queue-specific logical name is useful when a queue is used by PATHWORKS clients. Text files printed from PCs may be PCL or Proprinter files. The following example specifies the PCL data type for the queue named PATHWORKS:
$ DEFINE/SYSTEM/EXECUTIVE DCPS$PATHWORKS_DEFAULT_TRANSLATOR PCL |
The DECprint Supervisor software attempts to determine the file data type for
each file sent to the PATHWORKS queue. If a file data type cannot be
determined, the file is processed as a PCL file. If the file contains
PCL text followed by PostScript, it is printed properly.
4.2.3 How Users Control Data Type Detection
Users control the way print jobs are processed for automatic data type detection by specifying:
INVDDIFDATA, Invalid DDIF data, flushing to end of file |
/PARAMETERS=DATA_TYPE=AUTOMATIC[=text-data-type] |
$ PRINT/QUEUE=PS20$A10 PIC.MSG/PARAMETERS=(DATA_TYPE=AUTOMATIC=PCL) |
Previous | Next | Contents | Index |