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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Feb 5, 2022

Add STRCLNUP QEZSCNEP option to run once per day

The STRCLNUP and its job QSYSSCD run QEZSCNEP and then it seems to go to sleep for a period. This leaves the QEZSCNEP job running in QCTL 100% of the time. Provide an option to use something else (perhaps the job scheduler) so that it only runs once per day and then ends rather than 24x7.


Use Case:

The things the Start Clean Up command "cleans up" are based on age in days. That does not change once the initial invocation of the program has run. So it shouldn't sit there in QCTL 24x7 waiting on whatever next "event" it is waiting. Instead an option that puts the job on the jobq via the job Schedule should be implemented to run only once per day.


Idea priority Low
  • Guest
    Reply
    |
    Mar 14, 2022

    Ah. I see. That makes sense. thanks for the information.

  • Guest
    Reply
    |
    Mar 2, 2022

    The QSYSSCD job handles events for both the cleanup and power scheduler. There are a fair number of events being handled in this job, some of which appears to be dependent on serialization through a single job. While I'm sure it is possible to do this another way, it would be a fair amount of work to unwind and rewrite it. And I'm not sure there is a clear benefit for the cost to do so.

    The daylight saving time problem Rudi describes was fixed with the following PTF's when the problem was reported in 2019:

    7.4 ??? SI70595
    7.3 ??? SI70594

    For these reasons, I am declining this RFE at this time. If there are other issues that have not been addressed, this RFE can be reopened for further evaluation.

  • Guest
    Reply
    |
    Mar 2, 2022

    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 - Core OS
    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 - System Management
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |
    Feb 10, 2022

    This is a good idea as this job also has problem with the daylight change twice a year. This job start itself after running, again with a delay op 24 hours. Due to the daylight change adjustment this job has an offset of 1 hour. Due to the time adjustment of daylight change.

  • Guest
    Reply
    |
    Feb 10, 2022

    To be clear, I realize this routine sits idle on an event wait. But I needs to do its job and then get out of the way, and the Job Scheduler approach is a better option IMHO. Users see this job sitting in QCTL (using WRKACTJOB or similar interfaces) and are wondering why it is running 24x7.