FAQ on AIX Print Queues and Devices

Contents

About this document
Common question List
Problem list
Answers to common questions
Answers to common problems

About this document

Common question list

1. What is a print queue?
2. How do I set the default queue?
3. What is the right way to remove a print queue?
4. What are the meanings for printing of each serial wire?
5. What are the pinouts for a particular printer and adapter?
6. How can I display all of the queues on my machine?
7. What happens if I remove the /etc/qconfig.bin file?
8. How do I pipe the output of a command to a printer?
9. What software product can be used to print APA on AIX?
10. How do I know what printers are supported by AIX?
11. Where do console messages go when using CDE?
12. Can I view PostScript files before I print them?
13. How can I cat a PostScript file to /dev/lp0?
14. What does INITING status mean for MarkNet or 4033?

Problem list

1. Cannot cat to printer port (error 0403-005, for example)
2. Cannot print as non-root user, but root can print
3. The queue hangs and I can't print. Queue says ready, but jobs don't print.
4. Local printing in AIX and nothing prints, but the job disappears
5. Remote printing to AIX server but nothing prints
6. lpstat gives error that queue abcd does not exist
7. When I print with lpr why do I getunwanted headers?
8. What does Queue died running request indicate?
9. After upgrading to AIX 4.1, sometimes when printing with 'cat > /dev/lp0' the command returns to the prompt, but nothing is sent out the port.
10. I get a no queue error when doing an lpstat.
11. Why can't I print an AFS file?

Answers to common questions

1. What is a print queue?

A print queue technically is a pair of stanzas or paragraphs in the file /etc/qconfig. Each queue is made up of a queue stanza and a queue device stanza. The program that controls spooling on AIX is called the qdaemon, and the qdaemon uses the queue information in /etc/qconfig to determine what to do with each job that is submitted.

The queue stanza starts with a line giving the queue its name. The next line of the queue stanza always contains the name of the queue device stanza. Following this is additional information defining the queue. For remote queues, the queue stanza contains information such as the remote print server, the remote print queue name, and the type of lpd protocol used on the print server.

The queue device stanza begins with the queue device name pointed to by the queue stanza. This stanza contains information such as if a header or trailer page is going to be sent with the print job. Probably the most important line in the queue device stanza is the backend program name. This backend program is the first program that actually reads the data file and processes the file and sends it to the printer. Actually backend programs can process data in other ways,and the print queue can be used as a way to serialize data. When the backend program is piobe, or any other program that calls piobe such as piojetd and piorlfb, there must be a virtual printer associated with the queue.

When a print job is submitted by a local print command such as enq, lp, lpr, qprt, or dtprint, these commands all call enq which submits the job to the qdaemon. A queued job is represented by a JDF or Job Description File in /usr/lib/lpd/qdir that describes the job number, the user environment, the print flags, and the files to be printed. The qdaemon passes this information to the backend program that processes the print job.

2. How do I set the default queue?
• The default queue for the system is the first queue in /etc/qconfig.
• At AIX 4 use the following smit commands:
• smitty spooler
• Choose: Manage queues
• Choose: Set the default queue and enter queue name
• At AIX 3 use vi and move the queue and queue device stanzas in /etc/qconfig.
• To change an individual user's default queue use "export LPDEST=<queue>" in the user's .profile.
3. What is the right way to remove a print queue?

I'm having problems with queue daemon after removeing a queue.
First make sure that all jobs are removed from the queue. If you have jobs queued, there will be a dummy stanza or paragraph left in /etc/config. This can cause the qdaemon to stop and will give problems when adding new queues. After you remove queues, it is always a good idea to use grep to check for the word dummy in /etc/qconfig.

At AIX 4, the process is simple.

• Type smitty rmpq to remove virtual printer, queues, and print devices in one step.
• Select the queue to remove and press the enter key to remove the queue.
• When the last queue for a device is a removed, you will be prompted to see if you want to remove the print device.

At AIX 3, the process can be more difficult.

1. Make sure you remove the virtual printer first with "lsvirprt", then Select the queue. This removes the virtual printer, queue, and the queue device. If you simply use "rmvirprt -q queue" from the command line, then you will only remove the virtual printer and you will still have the queue and the queue device that are not removed.
2. If you don't have a virtual printer, or if the above didn't remove the queue device, the next step is to remove the queue device before the queue. Do this with: rmquedev -q <queue> -d <queue_device>
3. Finally, remove the queue: "rmque -q <queue>
4. Once this is done, use smit to remove the printer.
4. What is the meaning of the individual serial lines?

The pinouts for serial adapters on the system differ between adapters, but the meaning of the signals remains constant when applied to printing. The following list shows the signal name and function:


Signal Abreviation	Signal Meaning	Definition and function of the signal
TxD	Transmit Data	Data from the computer to the printer
RxD	Receive Data	Data like XON/XOFF back from computer.
CTS	Clear To Send	Used by AIX as a sign that the printer is turned on. Must be asserted by printer for AIX port to open. Queue will go down if signal not available.
RTS	Ready To Send	Signal is asserted by AIX when the port is opened.
DSR	Data Set Ready	Input signal to AIX, but not used in printing
DTR	Data Terminal Ready	Signal is asserted by AIX when the port is opened.
DCD	Data Carrier Detect	Input signal to AIX used for DTR (hardware) flow control. When signal drops, AIX stops sending data. When signal raises, AIX resumes.
SGND	Signal Ground	Used to keep signal levels balanced between the system and printer.




5. What are the pinouts for a particular printer and adapter?
• See the technical document AIX Printer Tips: Serial Printer Wiring.
• AIX requires CTS to be asserted or the printer port will not open, and thus it will give a "can't create" error.
• For HP LaserJet 4M and HP LaserJet 4Plus, you will have to wrap RTS to CTS on the system side of the cable, or the queue will keep going down when the buffer is full.
• For Epson printers you will have to wrap RTS to CTS on the system side of the cable, or the queue will keep going down.
• You will almost always need an interposer to swap signals, and system ports are DTE (Data Terminal Equipment), as are most printers. The other type is serial devices (DCE: Data Communications Equipment).
6. How can I display all of the queues on my machine?
• You can display all of the queues defined on your machine with the lsallq command.
• lpstat will show both local and remote queues and their status.
• enq -sA or enq -isA will show the status of only local queues. The advantage of this is you don't have to wait for remote queues to return status or time out.
• lpstat -t will show file names of files being printed.
7. What happens if I accidently remove the /etc/qconfig.bin file?
• /etc/qconfig.bin gets rebuilt each time /etc/qconfig is changed.
• If /etc/qconfig.bin is missing, the next time you print, it will be rebuilt. No harm done.
8. How do I pipe the output of a command to a printer?
• Use command | qprt -Pqueue or command > /dev/lp2.
• Example: lpstat | lp -d.
9. What software product can be used to print APA on AIX?
• This depends on exactly what you mean by APA.
• In the IBM context this means All Points Addressable. If this is the case the leading candidate would be PSF for AIX.
• In a sense all laser printers are APA, and so are the languages that are most popular when printing to them--namely PostScript and PCL.
10. How do I know what printers are supported by AIX?
• lsdev -Pc printers will show a list of all printer devices.
• Look in /usr/lib/lpd/pio/predef for the installed virtual printer drivers.
• Look at the list when installing a virtual printer. If it's not there, you don't have it.
11. Where do console print messages go when using CDE?

Question: The printer operator is logged on to a CDE (common desktop environment) window. When users print with qprt -m "Load my form" the operator doesn't see the message and when mail arrives back at the user, he doesn't know how to respond.

Answers: The problem is the console is /dev/lft. Change the console or use it.

1. Type tty in the window you want to be console.
2. Type swcons /dev/pts/10 to the name returned by the tty command.
3. Alternative: Install productivity tools. There is a window there for console response.
12. Can I view Postscript files before I print them?

There are a number of postscript viewers available to view postscript formatted files on the screen as they will appear when printed. Some of the choices from AIX are:

• gs - Ghostscript
• ghostview
• xpreview
• psprev - PS Preview
• xv
13. How can I use cat to send PostScript file to a printer device?

I have a PostScript file and I want to 'cat file > /dev/lp0', but the printer just goes to FLUSHING. The same file prints fine to a queue. I don't want a queue, how can I get the cat to work?
When you cat a file to /dev/lp0, the device driver can add carriage returns and line feeds to the file based on the device width parameter. One command to look at the device driver parameters is splp.
For example:
splp lp0
This will show you the width of the device. You can also use smit printer and then change/show devices. Usually this value is set to something around 80. Now look at the PostScript file. If there are lines longer than 80, a line feed and carriage return are being added at the end of the first 80 characters in the line. Thus the PostScript command has garbage in the middle. Now try splp -w 10000 lp0. This is usually longer than the line in the PostScript file and the file will go untouched. Of course this may cause problems with any text you were trying to format.
Another course of action with a PostScript file is:


 splp -p+ lp0

In SMIT this looks like:


 Send all characters to printer UNMODIFIED: YES for passthrough.

Both of these print a postscript file for me that won't print the default settings.
14. What does INITING status mean for MarkNet or 4033?

    The queue status of INITING for either a 4033 LAN attached printer or 4039 LAN attached printer indicates a problem with a "lockfile" in the /tmp directory on the system.

    To prevent 2 print jobs from attempting to print to the same device at the same time, the 4033/4039 utility establishes a lock file in /tmp for the duration of the print job. Normally this file is erased at the end of the job.

    If the INITING status remains for more than a few seconds then one of two things has occurred.

    a) The same physical printer is being addressed using 2 different print device names, in which case the print job will continue as soon as the first print job is completed.

    or

    b) For some reason the process of sending the print job to the printer was interrupted. This might happen if you kill the actual backend process via a kill -9 command or if the system for some reason halts (for example, due to a power outage). The normal qcan or cancel command will NOT cause this problem as the backend processes will clean up and remove the lockfile as part of the job cancel.

    To recover: With no print jobs running to the printer, go to the /tmp directory and delete the temp file. It will look something like: /tmp/10005A102781.TOK0.0 where '10005A102781' is the LAN address of the printer or 4033. This should clear up the problem.

Answers to common problems

1. Cannot cat to printer port (error 0403-005, for example)
• Usually this means there is bad wiring. Printer RTS is not going to AIX CTS, or the printer RTS is not HIGH.
• Be careful of printer RTS lines that toggle with flow control. This is a problem for HP LaserJet 4M and 4+ printers.
• AIX expects CTS is a sign of the printer on line.. If this signal is not asserted, then you will get this error.
• One solution is to wrap back the RTS signal from the system to the CTS signal.


2. Can't print as non-root user, but root can print fine
• This condition almost always indicates permission problems or bad or missing information in the /etc/password or /etc/user files.
• Check permissions on all directories in the /var/spool/lpd/... chain.
• Check permissions on /tmp, /usr/lpd, and /usr/lib/lpd.
• Check permissions on print programs /usr/bin/enq, qprt, piobe, and so on.
• Supportline has a program called prtcheck to check permissions on applicable files.
3. The queue hangs and I can't print. Queue says ready, but jobs don't print.
• This usually occurs when someone changed or added a queue when a printer is printing a large job, or a queue is in the DEV_WAIT state. Clear this problem and the queue will free up in most cases.
• See the technical document AIX Printer Tips: Clearing and Preventing Queue Hangs in AIX.
• Install fix:
1. IX62875 AIX 3
2. IX62876 AIX 4.1.4
3. IX62877 AIX 4.2
4. Not required at AIX 4.3
4. Local printing in AIX: Nothing prints, but the job disappears from the queue.
1. Formatted PCL files or ASCII files sent to PS queue: Fix by sending to ASCII queue or PCL queue.
2. Sometimes when printing files in passthrough, there are no carriage returns, and only the first line prints. If that line is all spaces, then it might appear as if nothing printed. This can be fixed by adding carriage returns to the file with a filter, or by changing the ct attribute in the virtual printer to tell the printer to add its own carriage returns.
3. The only other problem is wiring or printer problems.
5. Remote printing to AIX server, but nothing prints

Some things that can cause this problem are:
1. Wrong user id for lpd, missing lpd, lpd not running
2. Wrong permissions on files, /tmp, /, /var, /var/spool/lpd
3. From Novell, Novell sends -T flag without title; fixed with U437429 or U438621 or supersede
4. Printing from PC, Windows 3.1, Windows NT, OS/2 often sends a -l flag (says to add carriage return to line feed)
To solve this problem, the virtual printer must have an fl attribute. If it doesn't have one, you will have to edit the colon file with vi. The file will be in /var/spool/lpd/pio/custom at AIX 3, or at /var/spool/lpd/pio/@local/custom at AIX 4. The file name will start with the queue name, then contain a colon, and then the device name. Add a line:
:664:fl::%ip
This should solve the problem. Most AIX 4 colon files have this fix already.
5. Formatted PCL files or ASCII files sent to PS queue: Fix by sending to ASCII queue or PCL queue.
6. lpstat gives error that queue abcd does not exist, when there is no abcd queue on the system.

This is usually an indication that there are extra files in /var/spool/lpd/qdir.

• cd /var/spool/lpd/qdir
• ls | grep abcd where abcd is the queue name given in error
• Remove the extra files.
• Make sure that /etc/qconfig does not contain the name dummy. If it does, remove the queue associated with qdev dummy.
7. When I print with lpr I get headers no matter how I set up the queues.

Unwanted header problems come from 2 places.
• The /etc/qconfig queue device stanza says header = group or header = always.
• The print command calls for it. lpr by default issues a command that gets sent to 'enq' as '-c -Bgn file'. This means that you will always get headers with lpr no matter what is set in /etc/qconfig unless you use lpr -h filename -> '-c -Bnn file'. enq, lp and qprt all default to NO flags. You can always force no headers with 'enq -Bnn' or 'qprt -Bnn'. You can also DESTROY the virtual printer header capability by setting the 'sh' attribute to nothing: 'sh=[enter]'.
8. What causes Queue died running request?
• This is usually caused because the CTS line is LOW.
• See the technical document AIX Printer Tips: Serial Printer Wiring.
• This can also happen if a remote queue returns an error, if the remote hostname is not found, or if the remote LPD is not running.
9. After upgrading to AIX 4.1, cat command returns, but nothing is sent to port

Sometimes when printing with 'cat > /dev/lp0' the command returns to the prompt, but nothing is sent out the port.
• There is a BUG that is fixed by IX56226 that creates this situation.
• This can also be caused by bad printer wiring.
10. When doing an lpstat I get a "no queue" error that says:

queue status warning: no queue ?????????????? in /etc/qconfig...for
file /var/spool/lpd/qdir/default.log

• ANS: This indicates that you have an extra non-JDF (Job Description File) in /var/spool/lpd/qdir. Remove /var/spool/lpd/qdir/default.log and this will go away.
11. I can't print an AFS mounted file.

AFS (Andrews File System) files have security permissions.

• When I try to print /afs/pathname/file with qprt, the job fails with permission problems.
• I am able to print the file using lpr.
• The problem is that the qdaemon does not have an AFS coken.
• The command syntax with qprt that will work is:

qprt -c -P<queue> <file>

[ Doc Ref: 92031961517612     Publish Date: Oct. 17, 2000     4FAX Ref: 6436 ]