|
Mike, I agree with Eric. While we do NOTHING similar to what you are doing, I have seen this same behavior when there is an issue with a device. What we have had is IBM 4230-102 printers (IPDS) go bad and it being (temporarily) replaced by an IBM 4230-101. Sometimes the system will delete and recreate the device and sometimes it won't. When it doesn't I've seen two things happen: 1) you start the writer and it IMMEDIATELY ends 2) the writer is started and you release something to print and it IMMEDIATELY goes back on hold - like you are seeing... I would definitely contact Gumbo. Good luck, Chuck -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan Harris Sent: Monday, May 24, 2004 5:54 AM To: Midrange Systems Technical Discussion Subject: Re: Need Help. A Spool file stayed HELD even after RELEASE Hi Mike I'm going to assume that you are releasing the spool file then re-displaying the outqueue to see what has happened to it and seeing it still with a held status. Most likely the spool file was just set straight back to held by whatever processes it to handle some kind of processing error. Check: the job log of the writer job (if there is one attached to the queue) the job log of the job that processes the entries on the queue (if you know it) the gumbo job log or whatever log(s) that product uses the QSYSOPR message queue the history log If you have no idea where to look but know the name of the dataqueue associated with the outqueue try WRKOBJLCK against the data queue and see if you can see a job name. The job log of this job may give you a clue as to what is happening. The gumbo manual, their web site or their support team may be able to provide more specific help. Regards Evan Harris
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.