Re: System Audit journal question
Rob Berendt <[email protected]> Thu, 16 Jul 2026 07:29:10 -0400
| Newsgroups | gmane.comp.hardware.ibm.midrange |
|---|---|
| Message-ID | <CAPJ+qQO24GY8wcwWn6-HgVqOTF6awNbiiSBpyfjp0G0iRVviQQ@mail.gmail.com> |
x y, Does the IFS support commitment control? Rollbacks, APYJRNCHG, etc? On Wed, Jul 15, 2026 at 6:34 PM x y <[email protected]> wrote: > The only issue with multiple journals is commitment control won't work > across journals (unless IBM has changed something). But if that's not a > requirement, Bob's your uncle. Rob, actually. > > On Wed, Jul 15, 2026 at 6:37 AM Rob Berendt <[email protected]> > wrote: > > > Instead of journalling to the system audit journal, use a journal > dedicated > > to this particular set of stream files. Then it becomes quite easy to > > purge off historical data without losing unrelated journal entries. > > > > On Tue, Jul 14, 2026 at 9:37 AM DEnglander--- via MIDRANGE-L < > > [email protected]> wrote: > > > > > I am looking to track all READ and OPEN operations on selective IFS > > > folders. > > > > > > Is there a way to remove this information from the System Audit Journal > > > once it is extracted, so the Audit Journal doesn't balloon in size? > > > > > > Thank you, > > > > > > Doug > > > > > > > > > > > > "CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the > > attachments > > > accompanying it) contain confidential information belonging to the > > sender. > > > The information is intended only for the use of the intended recipient. > > If > > > you are not the intended recipient, you are hereby notified that any > > > disclosure, copying, distribution or the taking of any action in > reliance > > > on the contents of the information is strictly prohibited. Any > > > unauthorized interception of this transmission is illegal under the > law. > > > If you have received this transmission in error, please promptly notify > > the > > > sender by reply e-mail, and then destroy all copies of the > transmission." > > > -- > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > > To post a message email: [email protected] > > > To subscribe, unsubscribe, or change list options, > > > visit: https://lists.midrange.com/mailman/listinfo/midrange-l > > > or email: [email protected] > > > Before posting, please take a moment to review the archives > > > at https://archive.midrange.com/midrange-l. > > > > > > Please contact [email protected] for any subscription > related > > > questions. > > > > > > > > -- > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: [email protected] > > To subscribe, unsubscribe, or change list options, > > visit: https://lists.midrange.com/mailman/listinfo/midrange-l > > or email: [email protected] > > Before posting, please take a moment to review the archives > > at https://archive.midrange.com/midrange-l. > > > > Please contact [email protected] for any subscription related > > questions. > > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: [email protected] > To subscribe, unsubscribe, or change list options, > visit: https://lists.midrange.com/mailman/listinfo/midrange-l > or email: [email protected] > Before posting, please take a moment to review the archives > at https://archive.midrange.com/midrange-l. > > Please contact [email protected] for any subscription related > questions. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: [email protected] To subscribe, unsubscribe, or change list options, visit: https://lists.midrange.com/mailman/listinfo/midrange-l or email: [email protected] Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l. Please contact [email protected] for any subscription related questions.