|
i can't put my finger on it, but the Printing IV or Printing V redbook has memory requirements for remote outq, and some other performance tips. You have to decide how many will be active at the same time and adjust accordingly. As far as dependability - it all depends on network traffic and the printer itself. STRONGLY recommend "network printers". I would definitely not use any printer model not listed by IBM Knowledge Base doc on ASCII Printers. We have set a corp standard that no printer can be purchased outside that list (for 42 remote sites). I have found HP 2200N or HP 4000N work fine, but HP1100's (not a network printer) is more trouble, and far more expensive to keep up. If your dealing with every branch buying their own laser/copier from Office Depot, then you better give them a menu option or button to reset their own writer. Look in the ibm knowledge base for documents on ascii printer timing. Their are specific recommends for changing things like Jet Direct card timeout values. As I said above, this can work very well with good printers & good settings. hth jim franz ----- Original Message ----- From: "Konrad Underkofler" <kdunderk@hoshizaki.com> To: <midrange-l@midrange.com> Sent: Friday, August 23, 2002 5:10 PM Subject: RE: Performance hit for Remote outqs? > Buck, > > It sounds like it should be but in case where we have > a true IBM ipds type printer defined both ways DEVD > and remote tcp/ip queue, the DEVD one always starts to > print right away while the tcp/ip fails on retries. > Note we also route all our attached ip printers through > a Windows NT print server using the RAW attribute and > this may influence some of the timing. > > I would love to know the real story myself and aside from > the cpu % for host printer transform, IBM does not talk about > it much. > > Regards > > Konrad > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
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.