Date: June 5, 2026
Technical Alert – EXLOGCPR Issue
Overview
A defect has been identified in Assure Security versions 7.0.26.00 and later that can cause the EXLOGCPR logical file to grow significantly larger than expected - in some cases consuming hundreds of gigabytes of disk space, requiring intervention.
We are actively working on a permanent fix. This notice explains the problem, how to check if your system is affected, and steps you can take immediately to protect your system.
What Is the Problem?
Assure Security maintains a SAM (System Access Manager) exit point log file called EXLOG001. A companion logical file, EXLOGCPR, is used by the log compression command CPRQXLOGE, which is called during monthly maintenance (QJRN_SCDM).
In version 7.0.26.00, a change was made to increase the size of a field in EXLOG001 to support longer log strings. As a side effect, the index maintained by EXLOGCPR grew disproportionately - because the logical file uses that field as part of its index key. The larger the EXLOG001 file (more records = more log activity), the more severe the growth.
Running the standard reorganize command (RUNQJRGZ / RGZPFM) does not fix this - it rebuilds the index at the same inflated size.
How to Check If Your System Is Affected
Run the following commands on your IBM i system to check the sizes of both files:
DSPOBJD OBJ(SECOPS/EXLOG001) OBJTYPE(*FILE)
DSPOBJD OBJ(SECOPS/EXLOGCPR) OBJTYPE(*FILE)
You are affected if EXLOGCPR is significantly larger than EXLOG001. A ratio of EXLOGCPR being 2x or more the size of EXLOG001 is a clear indicator of the problem.
Example from a confirmed affected system:
|
File
|
Type
|
Size
|
|
EXLOG001
|
Physical file (PF)
|
218 GB
|
|
EXLOGCPR
|
Logical file (LF)
|
837 GB
|
Which Customers Are Most Likely Affected?
You are at higher risk if all the following apply:
• You upgraded to v7.0.26.00 or later
• You have high SAM exit point logging activity (large EXLOG001 file with many records)
• Your log retention spans a wide range of dates (via RMVQXLOGE with a long retention period), meaning EXLOG001 grows large over time
• Your system ASP has limited free space (less than 2x the current size of EXLOG001)
Immediate Action - What You Should Do Now
If your system is affected or you want to prevent the issue, follow these steps:
Step 1 - Delete the oversized logical file to immediately reclaim disk space:
DLTF FILE(SECOPS/EXLOGCPR)
Step 2 - Remove the CPRQXLOGE call from your QJRN_SCDM maintenance job.
All other maintenance steps (RMVQXLOGE, RUNQJRGZ, etc.) are unaffected and should continue to run as normal.
Step 3 - Resume your normal monthly maintenance schedule.
|
⚠ Important: Do not run CPRQXLOGE again until a Service Pack containing the permanent fix has been applied. We will notify you when that SP is available.
|
Impact of the Workaround
The CPRQXLOGE command merges duplicate consecutive SAM log entries to reduce the size of EXLOG001. Disabling it means duplicate entries will not be merged, so EXLOG001 may grow slightly faster than usual. However:
• No existing log data is altered or lost
• All other SAM monitoring, logging, and reporting functions continue to operate normally
• The workaround is safe to apply immediately on affected systems
Next Steps
A permanent fix is in development and will be delivered as a cumulative fix and in an upcoming Service Pack. When available, the fix will:
• Reinstate EXLOGCPR with a corrected structure
CPRQXLOGE compression command can be reinstated in QJRN_SCDM job after this.
We will communicate the availability of the fix and provide instructions required.
Contact Information
If you would like technical assistance, please contact the Precisely Global Support team at Precisely Support.