March 23, 2026
Assure Security Monitoring and Reporting
Introduction
In Service Pack 7.0.23, Assure Monitoring and Reporting (AMR) was updated to support longer journal records introduced with IBM i V7R6. To accommodate these records, the maximum available length for FIL output was increased by extending the JOESD (journal variable length record) field from 9,674 bytes to 31,750 bytes.
Because AMR programmatically allocates the maximum possible JOESD length, any newly generated AMR preparation file (FPR) created on Service Packs 7.0.23–7.0.27 will automatically use the larger 31,750‑byte JOESD field, regardless of whether all records require it.
Potential Customer Impact
As a result of this change:
- AMR preparation files (FPRs) and associated temporary work files in QTEMP can be significantly larger, often approximately three times their previous size.
- Large AMR extracts may require substantial temporary disk space. For example, extracting ~500,000 records may require tens of gigabytes of temporary storage during processing.
Customers may observe:
- Warnings or alerts related to excessive disk usage
- Increased consumption of system storage
- Queries stopping due to MAX_EXTRACT_SIZE limits
- In environments with limited available disk space, a risk of the system entering a restricted state
This behavior most commonly affects customers who use AMR preparation files as part of their reporting workflows.
Action Required
To ensure continued stability and avoid potential issues:
It is recommended that you upgrade to Service Pack 7.0.28, which is intended to resolve this issue and should be available to the public on March 31, 2026.
If upgrading to Service Pack 7.0.28 is not feasible before its availability, an interim fix is available for Service Pack 7.0.27 on the Software Download Site
Earlier releases can be reviewed upon request by opening a support case at Precisey Support
Contact Information
If you would like technical assistance, please contact the Precisely Global Support team at Precisely Support.