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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Workspace IBM i
Categories Security
Created by Guest
Created on Jun 1, 2016

When a user is expired by specifying USREXPDATE then QSECEXP1 should log it in the history log

I have put an expiration date on a user profile (USREXPDATE) and it was disabled as expected by the job QSECEXP1. But it is only logged in the joblog of QSECEXP1 not in the History log ( nor in the *SYSOPR message queue). This makes it difficult to see what have caused the expiration. Also we would have documentation that the user is disabled in proper time when we are audited.

Use Case:

Example of how it could be logged in the history log:

Job 349985/QSECOFR/QSECEXP1 started on 01.06.16 .......
User ABCDEF disabled by job QSECEXP1
User GHIJKLM disabled by job QSECEXP1
Job 349985/QSECOFR/QSECEXP1 ended on 01.06.16 .......

Idea priority Low
  • Guest
    Jun 3, 2016

    The QAUDJRN auditing journal will contain the record (audit entry) that indicates that user profile has been disabled. The audit record will be of type CP (Change Profile). The system uses the audit journal to track these type of user profile changes rather than doing anything with QHST/QSYSOPR.

  • Guest
    Jun 3, 2016

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Security
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Languages - CL (Control Language)
    Operating system - IBM i
    Source - None

  • Guest
    Jun 2, 2016

    Creating a new RFE based on Community RFE #89294 in product IBM i.