Using the LPD compatibility filter
For each type of data format that Print Interface supports, you
can specify the name of an associated filter. A filter is
a program that can modify data before Print Interface writes the data
to an output data set on the JES spool. When you specify the name
of a filter for a supported data format in a printer definition, Print
Interface automatically calls that filter before writing data to the
JES spool.
Infoprint Server
provides the LPD compatibility filter, lpd_compat.so,
which formats text data and line data in a similar way to the z/OS TCP/IP
LPD and creates line data. This filter is suitable for use with the line data and text data formats
for printers that accept line data.
The LPD compatibility filter, lpd_compat.so,
provides support for some LPD command codes and parameters that the
Print Interface LPD does not otherwise support. (LPD command codes
and parameters are specified in the LPD control file sent by the LPR
with each document to be printed.) This filter also lets you specify
the -f, -l, and -w filter options, which correspond to the FILTER,
LINECOUNT, and WIDTH parameters of the TCP/IP LPR command.
Table 14 summarizes the LPD command codes supported
by the Print Interface LPD, with and without the LPD compatibility
filter. For a full description of the LPD command codes, see RFC 1179.
Table 14. LPD command codes supported by Print Interface LPD| Command code | Description | Supported by Print Interface LPD |
|---|
| Without compatibility filter | With compatibility filter |
|---|
| C | Class | No | No | | H | Host name | No | No | | I | Indent printing | No | No | | J | Job name. This value becomes the title in the Infoprint Server title-text job attribute if the T command code does
not exist.2 | Yes | Yes | | Job name parameters 1 | No | No | | L | Print banner page | No | No | | M | Mail when printed. This value activates notification. | Yes | Yes | | N | Name of source file. This value becomes the
filename displayed by the lpq or lpstat command.
The compatibility filter also uses this name as the title if the T
command code does not exist and the p command
code is specified. | Yes | Yes | | P | Owner. Print Interface allocates data sets on
the JES spool with this value in the job name field. 2 | Yes | Yes | | T | Title. This value becomes the title in the Infoprint Server title-text attribute. | Yes | Yes | | W | Width of output | No | Yes | | X | Infoprint Server job attributes. If attributes
are prefixed with AOP, the LPD validates that the job attributes are
supported by the printer. | Yes | No | | 1, 2, 3, 4 | File names for troff fonts. | No | No | | c | Plot CIF file | Yes 3 | Yes 3 | | d | Print DVI file | Yes 3 | Yes 3 | | f | Print formatted file | Yes 34 | Yes | | g | Plot file | Yes 3 | Yes 3 | | l | Print file leaving control characters | Yes 4 | Yes | | n | Print ditroff output file | Yes 3 | Yes 3 | | o | Print PostScript output
file | Yes3 | Yes 3 | | p | Print a header and page numbers on each page | No | Yes | | r | Print with FORTRAN (ANSI) carriage controls | Yes | Yes | | t | Print troff output file | Yes 3 | Yes 3 | | v | Print raster file | Yes 3 | Yes 3 |
- The z/OS TCP/IP LPR command lets you specify these parameters
as part of the job name: DEST, FOR, FORM, IDENTIFIER, LINECOUNT, OTHER,
PASS, and PRIORITY. Print Interface does not support these parameters.
- JES does not permit the Print Interface LPD to allocate data sets
on the JES spool with the owner's name. Therefore, to make the owner
name visible on the JES spool, the Print Interface LPD makes the owner
name the job name except when IP PrintWay™ submits the data set
to the Print Interface LPD. In this case, the Print Interface LPD
keeps the original job name so that the operator can use the original
job name to find the data set on the spool.
- Print Interface automatically detects the data format of the input
data stream and ignores the format specification in the command code.
For example, Print Interface detects a PostScript data stream even if the o command
code is not specified.
- Without the compatibility filter, command codes f and l are equivalent. Print Interface leaves all ASCII
control characters in the output data stream.
- If an unsupported command code is specified in the LPD control
file, the command code is ignored and no error is reported.
- The Print Interface LPD, with or without the compatibility filter,
does not support these functions that you can specify with the z/OS TCP/IP
LPR command:
- Carriage control specification
- Top margin
- The
Print Interface LPD, with or without the compatibility filter, can
print multiple copies of the same file when the LPD control file contains
multiple lowercase command codes followed by the name of the same
print file. (The Print Interface LPD always prints at least one copy
of a file, even if no lowercase command code is specified in the LPD
control file.)
| Guidelines:
- If you want the functions that filter lpd_compat.so provides,
specify it for the Text and Line
data data formats in PSF printer definitions, General printer
definitions, and in IP PrintWay printer
definitions when you select the VTAM® protocol.
- Do not specify filter lpd_compat.so in IP PrintWay printer definitions
except when you select the VTAM protocol.
|
z/OS Infoprint Server Operation and Administration
Copyright IBM Corporation 1990, 2014