|
You will not have issue with accesiblity of JetDirect card because it will be taken care of at the AS/400 level. All jobs or report from the AS/400 will be control by FIFO, LIFO or whatever your preference is for that specific printer (an outq and a device is created when you use device description for your printer). Dare ----- Original Message ----- From: "Adam Lang" <aalang@rutgersinsurance.com> To: <midrange-l@midrange.com> Sent: Wednesday, December 26, 2001 3:19 PM Subject: Re: Are these valid arguments for DevicePrinters? > I know the AS/400 CAN send print directly to the printers, but the AS/400 > writers were timing out. Example, say I print a 20 page manual to a printer > over the network from my PC... If it took a little while to send and the > AS/400 couldn't build a connection, it would eventually shutdown the writer. > By setting up the AS/400 to send print to Linux print server, it solved that > problem. Linux handles the queueing of the jobs from multiple users, as > opposed to them fighting for connections to the JetDirect card. > > Adam Lang > Systems Engineer > Rutgers Casualty Insurance Company > http://www.rutgersinsurance.com > ----- Original Message ----- > From: "Dare" <oludare@ix.netcom.com> > To: <midrange-l@midrange.com> > Sent: Wednesday, December 26, 2001 3:14 PM > Subject: Re: Are these valid arguments for DevicePrinters? > > > > If your AS/400 is on your LAN you should be able to ignore the Linux and > let > > the AS/400 communicate with the printer through TCP/IP. You want to allow > > your user to start the printer writer if there is a glitch on the network > or > > if your writers are not automatically started at IPL. Your users will > still > > be able to send their reports to a printer device without using a PC (I > > think that's how you have it now) for virtual device. I will refer you to > > SG242160.PDF (size is 5,157Kb). This is a redbook that addresses all > current > > printer configurations and can be downloaded from ibm redbook website > > www.redbooks.ibm.com or I can send it to you privately > > > > Dare > > > > ----- Original Message ----- > > From: "Adam Lang" <aalang@rutgersinsurance.com> > > To: <midrange-l@midrange.com> > > Sent: Wednesday, December 26, 2001 2:56 PM > > Subject: Re: Are these valid arguments for DevicePrinters? > > > > > > > Our autoinsurance program has other subprograms that dump to printer > > > devices. > > > > > > Also, I think when users specify where they want to send an OfficeVision > > > document to print, they send it to the printer device. > > > > > > Why do you want users to start the printers? Shouldn't the writers be > > > running at all times? > > > > > > The final reason I have it setup that way, it was the only documentation > I > > > found from IBM that detailed how to setup a network printer. :) I had > no > > > other option to choose from. :) > > > > > > The AS/400 is not printing "directly" to the printer. IT is sending the > > > print to a Linux print server I setup that handles all the queues. I > had > > > problems with the AS/400 timing out writers and stopping them if someone > > > else was using the network port on the printer. > > > > > > Adam Lang > > > Systems Engineer > > > Rutgers Casualty Insurance Company > > > http://www.rutgersinsurance.com > > > ----- Original Message ----- > > > From: "Dare" <oludare@ix.netcom.com> > > > To: <midrange-l@midrange.com> > > > Sent: Wednesday, December 26, 2001 2:48 PM > > > Subject: Re: Are these valid arguments for DevicePrinters? > > > > > > > > > > If you're using remote outqs, why do you have to mapped them to a > > virtual > > > > device? > > > > In my original post I'm seeking others knowledge on the advantages of > a > > > > device description printers over remote outqs. > > > > I do believe that RO are inefficient way of setting up printers on the > > > > AS/400. For one, pagerange printing become difficult to acheive, > > > > programming for some special printing with printer files becomes > > > difficult, > > > > users can not start printers with RO etc. > > > > > > > > Dare > > > > > > > > ----- Original Message ----- > > > > From: "Adam Lang" <aalang@rutgersinsurance.com> > > > > To: <midrange-l@midrange.com> > > > > Sent: Wednesday, December 26, 2001 2:30 PM > > > > Subject: Re: Are these valid arguments for DevicePrinters? > > > > > > > > > > > > > Yes, "Could you". :) > > > > > > > > > > Adam Lang > > > > > Systems Engineer > > > > > Rutgers Casualty Insurance Company > > > > > http://www.rutgersinsurance.com > > > > > ----- Original Message ----- > > > > > From: "Dare" <oludare@ix.netcom.com> > > > > > To: <midrange-l@midrange.com> > > > > > Sent: Wednesday, December 26, 2001 2:22 PM > > > > > Subject: Re: Are these valid arguments for DevicePrinters? > > > > > > > > > > > > > > > > What do you mean by "Could clarify this a bit for an AS/400 > novice?" > > > Is > > > > > > "you" missing in your statement? > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Adam Lang" <aalang@rutgersinsurance.com> > > > > > > To: <midrange-l@midrange.com> > > > > > > Sent: Wednesday, December 26, 2001 2:13 PM > > > > > > Subject: Re: Are these valid arguments for DevicePrinters? > > > > > > > > > > > > > > > > > > > Could clarify this a bit for an AS/400 novice? I setup about 5 > HP > > > > > > laserjet > > > > > > > printers over the network using remote outqueues and mapping > them > > to > > > a > > > > > > > virtual device. > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > 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. > > > > > > > > > > > > > _______________________________________________ > > > > 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. > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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. > > > > > > > _______________________________________________ > > 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. > > > > > > > > _______________________________________________ > 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.