Technical data

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
users 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.
1. If your system does not have a customized data file, use the sample file
supplied with your software. Copy the file, and change the file’s extension,
as shown in the following command:
$ COPY
_From: SYS$LIBRARY:DCPS$FILE_EXTENSION_DATA_TYPE.DAT_DEFAULT
_To: SYS$COMMON:[SYSLIB]DCPS$FILE_EXTENSION_DATA_TYPE.DAT
If the .DAT file is not in variable or stream format, DCPS cannot read
it when the queues are started. OPCOM will report the error, and the
symbiont process may be terminated. You should save the .DAT file in
the appropriate format, and then restart the printing system using the
DCPS$STARTUP.COM file.
2. Edit the file. The file has the default file extension and data types listed.
For example:
POSTSCRIPT:
EPS
EPSF
POST
PS
;
The example shows that files with extensions of .EPS, .EPSF, .POST, and
.PS are linked to the PostScript data type.
Add extensions that are specific to your site, or modify any that have a
different local meaning.
You can specify any valid DATA_TYPE value, except AUTOMATIC. Do not
abbreviate the data type names. The valid data type names are:
ANSI
ASCII
DDIF
LIST
PCL
4–2 Providing Automatic Data Type Detection