Frequently Asked Questions
* NEW *
Free AS400 App Monitoring
Free 1 Year Pro License Offer
Topics
Send Email
00204 - How can we reduce the journal transactions without having control over the application? (40)
1) Identify temporary work files that are being used out of permanent libraries. All objects in these libraries are now being journaled. Use the "ENDJRNPF" command to stop unnecessary journaling of these temporary transactions.

2) Find data queues and data areas that are used for temporary movement of data between jobs. They are being security audited every time data moves in and out of these objects. Use "CHGOBJAUD OBJAUD(*NONE)"
command to disable the creation of these transactions.

3) Locate temporary files and folders on the Integrated File System (IFS) that are not needed for security auditing or for data replication purposes. Use the "CHGAUD OBJAUD(*NONE)" command to discontinue generation of these unnecessary security auditing (QAUDJRN) transactions.

4) Analyze excessive database updates on specific physical files to determine whether software application changes could significantly reduce the journaling volume. You may have a batch process that runs repeatedly throughout the day on your system that updates every record in one of your master files. A detailed analysis of these update transactions could determine that only a small percentage of the records should be updated. The application is changing the "Last Activity Date/Time" on every record when it should only do this if other values on the transaction have changed.

These types of changes can be made without having a negative affect on security auditing or data replication. If you have the adopted authority changing on the same program 6 million times per day, something is wrong.