To the method is 3-4 servers each sending printouts to 30-40 printers.  For
some reason a large printout gets sent to a department printer and the users
calls is to have the print canceled.  The it person then has to look on
several servers to find where the printout is coming from so the spooler can
be killed. And this server may be 2 time zones away.
What we =want to go to is a method where the server sends the printout to a
localized print server and the users can cancel their own printouts without
having to know the server commands on Unix where the printout was created.
the need to be able to move the printouts to the local server becomes quite
needed for support issues.


-------------------------------------------------
Larry Simonsen                Phone: 801-489-2450
Flowserve Corporation     Fax: 801-491-1750
PO Box 2200                    http://www.Flowserve.com
Springville, UT 84663      e-mail: [log in to unmask]
-------------------------------------------------
All opinions expressed herein are my own and reflect, in no way, those of my
employer.

 -----Original Message-----
From:   Wirt Atmar [mailto:[log in to unmask]]
Sent:   Tuesday, July 03, 2001 4:43 PM
To:     [log in to unmask]
Subject:        Re: NP92 Printing  and NT

Julie writes:

> Well, right now we find the Novell queues handy to kill monster
> print jobs the user decides they really don't want.

and Larry adds:

> However if what you want is an integrated print queue so that you can
manage
> what is being sent to the printer you will need to have a LPR/LPD service
> somewhere.

I presume from these comments that the primary architecture in place for
printing is that of one large printer somewhere in the computer room, where
all output appears, is later burst into segments, sorted by user, and then
put into pigeon-holed mailboxes for the recipients to later come pick up.

If so, this is a 1960's format that should have long ago been abandoned, and
now with network printing and the advent of inexpensive laser printers, it
is
a little bit of IS tyranny should be completely dispensed with.

A far more modern, user-friendly and much more efficient way to print
documents nowadays is to distribute dozens of inexpensive laser printers
around your campus, perhaps one printer for every three to ten people who
would receive output, all within a few steps of their desk, and have each
user print each of their own outputs directly to their appropriate printer.

Not only does IS never get involved with the printing process in this
procedure, the user gets his output just seconds after he asks for it,
greatly improving overall productivity. In essence, this architecture
converts the HP3000 into one of the finest personal computers that any user
can hope to use. It's instantaneous, it's efficient, and the user has total
control over what he's doing.

And should a giant print run occur that the user finds he really doesn't
want, the cancel buttons on the new laser printers do a magnificient job of
rapidly killing the print job on both the laser printer and the HP3000.

Wirt Atmar

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *