Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Jun 10, 2026

Include Specific Entry Type in SYSLOG Output from QSYS2.DISPLAY_JOURNAL

Description:

When generating SYSLOG output using the QSYS2.DISPLAY_JOURNAL function, the resulting information only includes the journal code and the journal entry type. However, it does not include the specific entry subtype contained in each entry (the first position of the ENTRY_DATA field).

Including this additional level of detail would significantly improve the ability to perform more granular analysis of journal entries—especially in scenarios where the data is forwarded to external systems such as SIEM platforms.

Use Case:

Having the specific entry subtype available would allow better filtering, correlation, and interpretation of events, leading to more precise monitoring and auditing capabilities.

Example (with invalid password entries):


SELECT SYSLOG_EVENT
FROM TABLE(QSYS2.DISPLAY_JOURNAL
(
JOURNAL_LIBRARY => 'QSYS',
JOURNAL_NAME => 'QAUDJRN',
JOURNAL_ENTRY_TYPES => 'PW',
GENERATE_SYSLOG => 'RFC5424'
)
)
WHERE SYSLOG_EVENT IS NOT NULL;

Current Behavior:

  • Output includes: |T-PW|

Proposed Enhancement:

  • Output includes: |T-PW-Q| (adding the specific entry subtype)

Additional Enhancement (Optional)

As an extra improvement, it would also be very valuable to include a human-readable description of the entry subtype as part of the SYSLOG output. This would make the logs more self-explanatory and reduce the need for external lookups or mappings during analysis.

Expected Benefits:

  • More detailed and accurate event analysis

  • Improved integration with SIEM and monitoring tools

  • Reduced effort in interpreting journal entries thanks to optional descriptive context

Idea priority Medium
  • Guest
    Aug 25, 2026

    The CAAC has reviewed this IBM Idea and recommends that IBM view this as a medium priority Idea that should be addressed.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers.  CAAC has a key role in working with IBM i development to help assess the value and impact of individual IBM Ideas on the broader IBM i community and has therefore reviewed your Idea.

    For more information about CAAC, see www.common.org/caac

    Brandon Pederson - CAAC Program Manager

  • Guest
    Jul 4, 2026
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it.

    Db2 for i development team
    IBM Power Systems Development
  • Guest
    Jun 10, 2026

    I agree with this request, it should be included as default, but I do not think it should be included as part of the JOURNAL_CODE and JOURNAL_ENTRY_TYPE, i.e T-PW.
    I think it should be a separate keyword.

    You can extract the subtype like this:

    SELECT SYSLOG_EVENT concat ' entrySubType=' concat interpret(substr(ENTRY_DATA, 1, 1) as char(1))

    FROM TABLE(QSYS2.DISPLAY_JOURNAL

    ( JOURNAL_LIBRARY => 'QSYS',

    JOURNAL_NAME => 'QAUDJRN',

    JOURNAL_ENTRY_TYPES => 'PW',

    GENERATE_SYSLOG => 'RFC5424'

    )

    )

    WHERE SYSLOG_EVENT IS NOT NULL;