Menu

IBM i: The SQL Way · #24

Are the PTFs for This CVE Applied? Start with CVE_CURRENCY

Use the new SYSTOOLS.CVE_CURRENCY view to begin reviewing IBM i CVEs and remediation status, with a read-only query and a practical validation workflow.

Related native optionIBM Navigator for i — CVE Currency
IBM iSQLCVE_CURRENCYPTFSecuritySYSTOOLS

A vulnerability bulletin identifies a problem. The maintenance team needs to know whether the relevant fix is applied on this partition. CVE_CURRENCY brings those questions closer together.

Announcement preview — October 28, 2026

The associated Db2 groups are planned for November 20, 2026. This first-look example has not been run on IBM i. Detailed column definitions, authority requirements, and data-access prerequisites still need verification before this example becomes a tested walkthrough.

Start with the view

IBM describes SYSTOOLS.CVE_CURRENCY as a view of CVEs and their remediating PTFs, including information that can determine whether relevant PTFs or group levels are applied on the current system. IBM service description.

The initial query is deliberately small:

SELECT *
FROM SYSTOOLS.CVE_CURRENCY;

This lesson uses the view form. IBM also lists a table function with the same name; the view query does not use parentheses or a TABLE(...) expression. IBM service listing.

Download the SQL query.

Run the first review in ACS

After the documented prerequisites are met, connect ACS Run SQL Scripts to the intended partition and execute the query. Save the result with the system identity, timestamp, and installed Db2 group level.

Expected kind of result: CVE and remediation information for review. There is no fixed expected row count, and this lesson does not supply fabricated bulletin IDs or status values. Your partition and the service data determine the result.

For a first validation, select one real bulletin from the report and compare it with the installation evidence for its listed fix. Choose a case whose maintenance history the administrator already understands. This makes it easier to detect an incorrect interpretation of a status column before that interpretation becomes a report rule.

What to verify before filtering

Once the detailed service reference is available, check:

Only then add a filter for items needing attention. Guessing a column named PTF_STATUS or a status value such as MISSING would make a plausible-looking example that may not run—or may answer the wrong question.

An empty result is not sufficient evidence to label a system fully remediated. First establish that the request completed successfully, that its data was available, and that the service covers the question being asked. Investigate diagnostic messages before recording a successful maintenance check.

Availability to check

Release Associated Db2 group level Planned availability
IBM i 7.6 SF99960 level 4 November 20, 2026
IBM i 7.5 SF99950 level 13 November 20, 2026

These levels come from IBM’s enhancement pages and 2026 Db2 schedule. Confirm current service-specific requirements before running the query.

Build on the earlier workflow

Use this report as a review input: identify the item, inspect the bulletin and installation evidence, assign an owner, then repeat the check after maintenance. Keep the before-and-after evidence with the change record.

The earlier CVE_INFO lesson and security and PTF visibility workflow provide the background. This lesson adds a focused first query; a later tested version can add verified status filters and captured output.

Back to the TR3/TR9 overview.

References

IBM documentation and support references used for this entry.

Comments

Share your thoughts, questions, or real-world IBM i experiences related to this article.