The following list defines terms commonly used with printing.
When you attach a printer to a node or host, the printer is referred to as a local printer.
The spooler used for printing provides a generic spooling function that can be used for queuing various types of jobs, including print jobs queued to a printer.The spooler does not normally know what type of job it is queuing. When the system administrator defines a spooler queue, the purpose of the queue is defined by the spooler backend program that is specified for the queue. For example, if the spooler backend program is the piobe command (the printer I/O backend), the queue is a print queue.
Likewise, if the spooler backend program is a compiler, the queue is for compile jobs. When the spooler's qdaemon command selects a job from a spooler queue, it runs the job by invoking the backend program specified by the system administrator when the queue was defined.
The main spooler command is the enq command. Although you can invoke this command directly to queue a print job, three front-end commands are defined for submitting a print job: the lp, lpr, and qprt commands. A print request issued by one of these commands is first passed to the enq program, which then places the information about the file in the queue for the qdaemon to process.
The printer backend is a collection of programs called by the spooler's qdaemon command to manage a print job that is queued for printing. The printer backend performs the following functions:
The qdaemon keeps track of the print requests in the /var/spool/lpd/qdir directory and ensures that the jobs are sent to the proper printer at the proper time. It also keeps track of the status of the printers and stores printer usage data for system accounting purposes (for example, lpstat and enq -A commands). This information is held in the /var/spool/lpd/stat directory.
If the qdaemon is stopped, it will be restarted by the srcmstr.
Note: Do not stop the srcmstr process; it controls other daemons running on your system.
Msa1: device = lp0
Usually, queues are created through Web-based System Manager.
lp0: file = /dev/lp0 header = never trailer = never access = both backend = /usr/lpd/piobe
In the previous example, lp0 is the device name, and the rest of the lines define how the device is used.
Adding a printer through Web-based System Manager (type wsm, then select Devices) creates a standard queue device entry to an existing queue.
Notes:
- There can be more than one queue device associated with a single queue.
- There will not be a file entry in the /etc/qconfig file when you are using a remote printer. The queue directs the file to the server.
A real printer is the printer hardware attached to a serial or parallel port at a unique hardware device address. The printer device driver in the kernel communicates with the printer hardware and provides an interface between the printer hardware and a virtual printer.
To use remote printing facilities, the individual nodes must be connected to a network using the Transmission Control Protocol/Internet Protocol (TCP/IP) and must support the required TCP/IP applications.