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 Future consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Jun 13, 2022

System tables to use date / time fields instead of character fields in job format

Current IBM supplied output files, such as QADSPOBJ, that are use as templates for associated system commands store dates in 2 character fields and times in single character fields. Given the power of Db2 for i and the availability of date / time column types can these template files be updated to use relevant column types now? Use Case: Any task the generates output using an IBM command needs to know what the job format is so that the records can be correctly sorted into date / time sequence where required. Whilst this can be achieved with some SQL manipulation, for example, this is a time consuming exercise for each requirement. Providing this information in *ISO format date / time columns would be preferable. This is me re-opening IBMI-I-2207 for future consideration since the reply from IBM only referred to ONE of the possible tables impacted and how to resolve that issue. That RFE; as ideas were called when I originally raised it, was supported by CEAC as "a MEDIUM priority requirement that should be addressed". Asking IBM to look at the broader picture and not fixate on the one sample given by me.
Idea priority High
  • Guest
    Jul 14, 2022

    In the cases where a date and time is provided for a particular piece of information (for example object creation date/time), would adding a timestamp instead of separate date/time type fields be easier? If so, that would also make it easier to sort and compare values since there is only 1 field to deal with instead of 2. There's a little extra work if you're only interested in the date part of the timestamp, but I'd rather do that and get the functionality sooner.

  • Guest
    Jul 7, 2022
    We will take another look at this and see if we can fit it in. The outfiles contain MRI, so they are typically only updated on a release boundary.

    IBM Power Systems Development