|
With reference to recovering deleted spooled files, please note the following facts: Spool is really kept in the library QSPL in a compressed format. Until V5R2, job structures holds spool to jobs. (In V5R2, there is a new job attribute - inherited from a new system value QSPLFACN - which allows jobs to be deleted while the spool remains on the system. I'm a bit amazed/puzzled how IBM pulled this one off.) The QSPL library cannot be saved. When you delete a spooled file in any fashion (DLTSPLF, CLROUTQ), the spooled data is *GONE, and the member in QSPL is cleared, becoming available for re-use. Period, end of discussion, The system value QRCLSPLSTG merely determines how many days unused (already used and now cleared) spool members remain on the system, before the system removes the members. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Mike.Barton@pinkro ccade.co.uk To: midrange-l@midrange.com Sent by: cc: midrange-l-admin@m Subject: Re: Recover deleted spool files idrange.com 07/09/2002 03:49 AM Please respond to midrange-l > Hello everybody, > > An important outq has been cleared up and the user didn't has chance to > print the reports. > > 1) There is any way to recover the spool files on specific out queue?. I > couldn't find anything related with this topic in the archive. > > 2) How can I know who cleared up this out queue or who deleted the output > that were on that outq?. I checked the system log and I couldn't find any > record that indicate who and when this outq was cleared. I also checked > the audit journal without any luck. > > Any help will be appreciated. > > Thanks. > Nilda do you have a system save taken shortly before the output queue was cleared ? I guess probably not .... Spool storage is regularly cleared up (depending on system values) & is not easy to retreive from the QSPL files anyway. Regarding who cleared the queue, suggest you look into either: (a) preventative measures, ie ensuring only correct authority to deleting of spool files, or (b) setting up auditing on the system to find out who the culprits are *after* the event. ... HTH Mike This communication and the information it contains: - (a) Is intended for the person(s) or organisation(s) named above and for no other person(s) or organisation(s). Access to this mail by anyone else is unauthorised. (b) Is confidential, and may be legally privileged or otherwise protected in law. Unauthorised use, circulation, copying or disclosure of any part of this communication may be unlawful. (c) May be susceptible to interference, and should not be assumed that it has come in its original form and/or from the stated sender or PinkRoccade UK accepts no responsibility for information, errors or omissions in this e-mail or use or misuse thereof or any act done or omitted to be done in connection with this communication. If you are not the intended recipient, please inform postmaster@pinkroccade.co.uk immediately and delete it and all copies from your system. _______________________________________________ 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-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.