|
Oliver, Outqs do have some special authority options all their own. If I recall correctly, WRKOUTQD outqname and then press F13 to change them. I've never tried to do this to the job log outq, so I'm not sure if you could essentially revoke authority to it so users would not see spooled files on it w/o having the system generate errors when it tries to create job logs. Perhaps someone else on the list has attempted this? Another option would be to change the logging level on the job descriptions so that job logs are not created if the job finishes normally. If you are having to debug app problems you can always change it back. Chuck ----- Original Message ----- From: <oliver.wenzel@cibavision.novartis.com> To: <MIDRANGE-L@midrange.com> Sent: Thursday, July 19, 2001 4:10 AM Subject: Hiding spoolfiles from outq x > Hello, > > when a user does a wrksplf, he sees all his spoolfiles in all outqueues. Can > I exclude an outq from this display, > perhaps by setting up authorities? > > Our users are getting confused with all the joblogs of their jobs. If I > could hide the joblogs, it would be lots easier > for them to find their spoolfiles. > > Until last week, we had prtf QPJOBLOG set to hold(*no), so all joblogs were > in status rdy and shown on top of the > wrksplf list. We had to change this to hold(*yes), as every now or then a > joblog would be printed on prt01 (and every > time several hundred pages). I haven't found how the joblog got from > QEZJOBLOG queue to our prt01 queue - I just > didn't have the patience to read through 500 pages of joblog. But it looks > like a bug in one of our apps. > > -- and something funny > > Two days ago people started complaining they couldn't find their spoolfiles > (sounds like the above problem). But it's > more like they can't find their jobs - as these users always work with > wrksbmjob and then go to the last entry - that's > the newest print. Suddenly, the latest job isn't where it is supposed to be? > Anybody know why? > > Regards, > > Oliver > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.