× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Printers: Network v 400
  • From: Glenn Gundermann <ggundermann@xxxxxxx>
  • Date: Fri, 11 Jul 1997 12:44:30 GMT

Doug,

Call me dense but I don't understand your situation entirely.  Why would you
have so many printer writers?  Wouldn't you just have one and everyone
printing to it?

We have a 3916 on the AS/400 for AS/400 output as well as PC output through
printer emulation.  The printer is not attached to a PC and hence does not
require the PC to be up and running.  This is crucial.

There is also a 4033 attachment for the 3916 which is a printer server and
would allow LAN printing to the 3916 without the printer emulation.  I have
never configured it but it's here.  It's similar to the HP Jet Direct card.
Using this would free up memory on the PC clients.  I have found this is
more critical for the Windows 3.1 users than the Windows 95 users.

The newer IBM printers have the network card built in and wouldn't require
this 4033.

In another area of the office, we have an HPIII Si with a Jet Direct card
for LAN printing.  As soon as we go to V3R7 (from V3R6) I've been told we
can configure it as an AS/400 printer.

Ideally, no one area should have two printers; one for AS/400 output and one
for LAN output.

Glenn

At 10:56 AM 7/10/97 +0000, Doug Barnes wrote:
>We have a workgroup that is considering having 10 - 20 AS/400 users
>(CA/400 Win95)
>connected to a system (510, V3R7) and a PC Network. They are trying
>to decide wether to replace an IBM3812 with another AS/400 printer
>(IBM 4317 - we are using elsewhere and like it) or have each user use
>their own PC to support a printer session to a network printer
>(HP5something) and have one printer support all their printing.
>
>My question/comment(s) are...
>
>How much overhead does having a printer writer for each user cause.
>
>Should it be avoided?
>
>I'd rather support a single printer device name, than have to deal
>with PCPRT01P1, PCPRT02P1, PCPRT03P1, PCPRT04P1, PCPRT05P1,
>PCPRT06P1, PCPRT07P1, PCPRT08P1, PCPRT09P1, PCPRT10P1, PCPRT11P1,
>PCPRT12P1, etc...
>
>The cost for a new 4317 v maintaining the 3812 is a no-brainer.
>Although originally we had some trouble getting the 4317s up and
>running, we have them doing just fine now.
>
>Some users only have a terminal and would have to rely on other users
>printer sessions on the 400, assuming they were active when they
>needed it.
>
>Although we have been able to print PC docs to the 4317 I'd rather
>have one printer for the 400 and one for the PC network.

    _/_/_/_/   _/         _/_/_/_/   _/_/    _/   _/_/    _/
   _/         _/         _/         _/ _/   _/   _/ _/   _/
  _/  _/_/   _/         _/_/_/     _/  _/  _/   _/  _/  _/
 _/    _/   _/         _/         _/   _/ _/   _/   _/ _/
_/_/_/_/   _/_/_/_/   _/_/_/_/   _/    _/_/   _/    _/_/

Glenn Gundermann
ggundermann@ibm.net
work tel: (416) 967-8222
cel:      (416) 409-4551

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.