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 Delivered
Workspace IBM i
Created by Guest
Created on Dec 26, 2018

Annual/yearly option for i5/OS job scheduler

Add a frequency (FRQ) of *YEARLY to the system job scheduler, to go along with the *WEEKLY and *MONTHLY options. Allow the user to enter a specific date as the schedule date (SCDDATE) for the first run of the job, or a special value such as *YEARSTR or *YEAREND.


Use Case:

We have a few jobs that need to run only once a year. For example, we duplicate a certain set of data on January 1; run reports specific to year-end on December 31; and have to produce information for a regulating agency on, say, April 15.

It's easy to set up a scheduled job for twice a week, or once a month, or to run a job at every month-end except December 31 (by using OMITDATE).

There is no option to run a job once a year, or to enter a list of run dates. So we have to schedule these jobs to run *ONCE and save, and use a non-IBM product to remind us to change the year manually after the job has run. Our small shop doesn't have the complex scheduling needs that would require either IBM's Advanced Job Scheduler, or a third-party scheduler for the i, at extra cost.


Idea priority Low
  • Guest
    Reply
    |
    May 4, 2022
    A new special value of *YEARLY has been added to the frequency (FRQ) parameter on the Add Job Schedule Entry (ADDJOBSCDE) command.
    For more information, see the ADDJOBSCDE command documentation at the following link in IBM Documentation: https://www.ibm.com/docs/api/v1/content/ssw_ibm_i_75/cl/addjobscde.htm

    IBM Power Systems Development
  • Guest
    Reply
    |
    Nov 5, 2021

    Changing status to 'Planned for Future Release'.

  • Guest
    Reply
    |
    Aug 3, 2021

    We are working towards providing this function in a future release.

  • Guest
    Reply
    |
    Oct 30, 2019

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

  • Guest
    Reply
    |
    Dec 30, 2018

    I think JOSYS36 has nailed this one on the first shot.
    Write a CL wrapper program and you'll get all the flexibility you need :-)

  • Guest
    Reply
    |
    Dec 27, 2018

    Personally what I would do in this case is write a wrapper program that would calculate what date it was when the job was submitted. Then it could see that it was either the first of the year by looking at the day and the month,

    What I've also done in the past is have a job run every single day, but the first thing it does is see if it's the start of the month, end of the month, or the beginning of the year. Then depending on the date found it would either continue, or just end.

    Also writing a more advanced job scheduler would not be too difficult. So since there are many other options I would leave the scheduler as it is.

0 MERGED

Add *YEARLY Option to Job Scheduler

Merged
The Add Job Schedule Entry (ADDJOBSCDE) command has options for Frequency of *ONCE, *WEEKLY, and *MONTHLY. But we have the need for a *YEARLY option. Naturally, the CHGJOBSCDE and WRKJOBSCDE commands would also need to be changed to handle this ne...
about 5 years ago in IBM i / System Management 5 Delivered