|
|
Native Mode Spooler Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 3 Configuring and Operating Network PrintersA Small Sample Configuration |
|
This section shows you a sample network printer configuration that might be appropriate for a small network confined to one site with identical LaserJet 4Si printers. This example shows configurations for three such printers, LDEVs 6, 200, 210. One printer, LDEV 200, is used heavily for PostScript output, so it has been configured as two separate logical devices: LDEV 200, which uses a standard LaserJet setup file, and LDEV 201, which uses a PostScript setup file. The NPCONFIG file for this small configuration is shown below. Comment text appears after the pound sign (#), and is useful for making the configuration file self-documenting.
The setup files used in the small configuration example are explained below. The global setup file LJ4SISET.HPENV.SYS is a typical setup for portrait mode printing. It consists of several groups of settings which are first shown in tabular form in Table 3-4 “Setup elements for the LJ4SISET.HPENV.SYS Global File”, then as they might actually appear in the setup file. This file completely defines the printer setup. You may choose to configure many of these settings at the printer itself and omit them from the setup file. If you do, they will be set as soon as the spooler sends the EscE command sequence before printing begins. The line termination attribute, Esc&k2G, needs a bit of explanation. Text files generated on UNIX systems typically include only the <LF> as a record separator. The <CR> must be supplied, otherwise each line of the output would stairstep down the page (and most likely be truncated at the right margin). The value shown for this attribute directs the printer to supply a <CR> whenever it receives an <LF> or <FF> (formfeed). Note that an actual <CR> in the data stream before the <LF> or <FF> is redundant and does not change the output. Here is a typical record-oriented file containing the setup information. In this example, we have taken advantage of the PCL property of combining commands within the same parameter and group to reduce each such combination to one record of the setup file. The native mode spooler would trim leading and trailing blanks from each record and concatenate them to arrive at the final sequence actually sent to the printer.
For further details regarding PCL, consult your printer's PCL documentation. Table 3-4 Setup elements for the LJ4SISET.HPENV.SYS Global File
The contents of an LDEV-specific setup file are appended to those of any global setup file. This means that the setup data shown below, contained in the file LJ4PSSET.HPENV.SYS, is sent after the data shown above as LJ4SISET. This setup file merely switches the printer's language personality to PostScript so that it interprets the data properly. The first line of the setup file is a Universal Exit Language command. The carriage return (#13, %15, $0d, chr(13)), and line feed (#10, %12, $0b, chr(10)) characters (shown as the CR and LF keycaps, respectively) in the PJL commands are significant and must be included as data. Do not rely on MPE or the printer to supply any of these characters as line terminators. The spooler concatenates only the separate data records in the setup file and sends the result to the printer as one unbroken data stream. It does not insert any data of its own. You may include annotations and comments in your files only if you precede them with the COMMENT PJL command, as shown in the example below. Do not use other symbols such as the pound sign (#), curly braces ({}) or slash-asterisk combinations (&/*) to indicate comments in a setup file. The spooler has no provision for ignoring them. For this example, assume that all required PostScript, including any necessary non-resident font definition, is in the user's data stream.
mode at the end of each print job. There is no need for a user-supplied "exit" setup file, nor is there any provision for the spooler to use such a file. |
|