|
>From one Mike to yet another, Have to agree with MichaelR_41......better to treat the problem. We had exact same problem "years ago" and the cure was adding additional memory to the *SPOOL memory pool. Of course you can always write a monitor utility but it won't really "fix" the problem. HTH, Michael Rooney Citigroup International -----Original Message----- From: midrange-l-bounces+michael.p.rooney=citigroup.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+michael.p.rooney=citigroup.com@xxxxxxxxxxxx]O n Behalf Of michaelr_41@xxxxxxxxxxxxxx Sent: Thursday, July 29, 2004 10:35 AM To: Midrange Systems Technical Discussion Subject: Re: Background job to monitor outq? First off, don't get your haircut. Just let it grow. Second, you would be treating the symptom and not the problem. You either don't have enough memory in your printer or your timeout settings on the printer need to be set higher. Another problem could be not enough memory in your *SPOOL shared memory pool on your iSeries. It may need more memory to do the EBCDIc-ASCII conversion. Maybe a mullet. Just thinking out loud here. On Thu, 29 Jul 2004 07:25:31 -0700 (PDT), "Mike Berman" <mikeba777@xxxxxxxxx> said: > > We have a problem w/ a remote outq. What happens is that > Periodically, usually after a large spool file, it hangs there. The spool > file stays in *SND status, and thus doesn't let the next spools print. I > would like to write a program that would check the status of the first > spool file, if it has been in SND status for more than 30 minutes, put it > on hold. Of course, the only problem w/ my brilliant idea, is if the > paper is out, but I would rather deal w/ that than having to go into this > outq 30 times a day and getting calls while having my haircut for > example. > > Can this be done ? > > > > --------------------------------- > Do you Yahoo!? > Yahoo! Mail is new and improved - Check it out! > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > -- michaelr_41@xxxxxxxxxxxxxx -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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.