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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Nov 23, 2021

Add JOB TIME Property to CHGJOB cmd and QWTCHGJB API

Customers are running applications that need to set the time to something other than the System Time (i.e. QTIME system value). Today they have to change the QTIME system value which impacts all things on the system and then remember to change it back!
Expose the TIME property of the Job and allow it to be changed, just like the DATE, to a user-specified value. Both the CHGJOB command and the QWTCHGJB API should support this change as well.

Use Case:

A user has to run a job for "today" however due to whatever reason, it is now 01:30 (AM) the next day.
The user has to change the job date to the prior day (no problem) but the time has to be changed via CHGSYSVAL QTIME which is nonsense and really unbelievable. Then they have to remember to change it back to whatever the current time is.

Idea priority Medium
  • Guest
    Dec 22, 2021

    We cannot set the time for a job on this platform. That's the request (to resolve that limitation).
    If what you're implying is that all those interfaces are pulling the time for the job from the system clock (i.e. the System Time) and there is no Job property/attribute currently that is separate and distinct from the System Time, then I understand the decline.
    However if there is a Job property that is the Job Time that runs perhaps by convention in parallel to but separate from the System time, then I would kindly ask that you provide access to changing this value via CHGJOB (at minimum) and provide it as the Job Time in place of the System Time that is currently display on DSPJOB.

  • Guest
    Dec 21, 2021

    Thank you for submitting this RFE. While I understand the use-case and agree that it would be useful, I am going to decline the request at this time for a couple of reasons.
    Firstly, if we were to add a job time, it would make sense to add it to all (or most) of the same places that the Job date is externalized. The Job date (key 1002) is on many interfaces, including commands, displays, APIs, SQL services and the graphical user interface. Here is a list of the interfaces that allow you to display, change or retrieve the Job date:
    CHGJOB command
    RTVJOBA command
    SBMJOB command
    CRTJOBD command
    CHGJOBD command
    WRKJOB/DSPJOB display
    IBM Navigator for i (job properties)
    Even if we were able to pare that list down to say half, it is still a big change, and would be hard to fit in unless the priority were higher than several other work requests.
    The second reason that I am declining this request is because I am afraid that this new "job time" would be confused with our existing concept of job time (which can be viewed on DSPJOB, option 2) and is defined as the local job time which is determined by the job's time zone.