Extra formfeed on TCP Printers

From: Nigel Gall <nigelg_at_ppsl.com>
Date: Tue, 22 Dec 1998 15:04:05 -0400

Hi!

Some months ago someone posted a query on how to prevent extra pages
from being formfed after each printjob. I''ve been searching the
archives (there must be a better way to do this? Glimpse, perhaps?) and
also I had a problem with our email server so for a period of time, some
of my mail was sent to oblivion; I suspect his summary was among these.
Perhaps he can contact me again?

I now have the same problem, and I'm at a loss as to how to solve it.
We have a mix of dumb printers, all connected via Xyplex Terminal
Servers (queues setup; printing well from NT Server 4.0, and DU 3.0B on
an AS2100), and network laser printers (HP 4000N's).

We migrated from an AS2100 to a new AS4100 running DU4.0D. Our old
method of printing involved using Xyplex's filters (a C program that was
compiled on the 2100). On the 4100, the filter's code compiled, but the
printjobs refused to appear on the printers (status showed that the
daemon was waiting for the printer to become available/online; jobs kept
waiting in queues). On the suggestion of the our local DEC Rep, we
decided to use TCP printing on the 4100. This was a breeze to setup and
worked straight off, but we're getting these extra pages being put out.

Last year, we were getting this same problem on the 2100, and we had to
upgrade the terminal server software to allow us to set the FORMFEED
option to none for the queue configuration. This solved our problem
then. This doesn't work now at all (it makes me wonder if TCP printing
uses the queues on the terminal servers at all). I've tried fiddling
with the ff and sf printcap settings; doesn't work.

The interesting things to note:

- Printing from NT Server 4.0 is fine.
- Printing from DU 3.0B using Xyplex's proprietary filter is fine.
- In one case, if I send a Windows printjob to a HP LaserJet 4
  that we use to print PO's from an application on DU 4.0D,
  immediately thereafter no UNIX printjobs print.

On the latter problem, I've temporarily given my users a separate
printer for Windows printing and retained the HP for PO (purchase order)
printing, since the program was written specifically for this printer
(it sends postscript control sequences before the job is printed to set
things like font, etc.).

Following is a snippet of the /etc/printcap which describes the setting
for the HPLJ4 PO printer:

xwh03|xit03|xmis04|Purchasing Area - 20.0.1.113 port 1:\
        :ct=tcp:\
        :lp=_at_mis720/port1:\
        :of=/usr/lbin/hplaserof:\
        :sh:\
        :ff=NULL:\
        :sf:\
        :mx#0:\
        :sd=/usr/spool/xmis04:\
        :pw=80:\
        :lf=/var/adm/errxmis04:\
        :xf=/usr/lbin/xf:\
        :br=57600:

mis720 is in the /etc/hosts file and port1 is service 2100/tcp in the
/etc/services file. Can anyone help me?

Best regards,

Edmund Nigel Gall
Information Systems Specialist
Process Plant Services Limited
Atlantic Avenue, Point Lisas Industrial Estate
Point Lisas, Couva, Trinidad & Tobago, W.I.
Tel: (868) 636 3153 Fax: (868) 636 3770


Received on Tue Dec 22 1998 - 19:07:27 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT