Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/


Status Not under consideration
Workspace Spectrum LSF
Components Reporting/Explorer
Created by Guest
Created on Aug 4, 2022

Change job submit time to include milliseconds for precision.

Job submit time to include milliseconds for precision. Instead of HH:MM:SS, make it like 12:29:05.1234. This will enable this column to be used as a unique identifier when generating data in an incremental fashion. We are extracting the RTM data and running a refresh on our report but for efficiency purpose, we would like to only add the new data rather than refreshing the entire data which take a long time and not necessary as the old data never changes. If we have a unique column then it can just go through the column and add only the new records. We cannot use job_id as we have multiple clusters and therefore the job_id can be common.

Needed By Yesterday (Let's go already!)
  • Admin
    Bill McMillan
    Aug 9, 2022

    A patch to support globalID will hopefully be available by the end of the quarter. SP13 will be a pre-requisite for it.

    It effectively adds a clusterid (like in RTM) to the job ID.
    So in Cluster 01 the jobids will be: 1234501 1234601 1234701 etc;

    and in Cluster02, 1234502 1234602 1234702 etc
    so the last 2 digits represent the clusterid; so you can clearly see from the jobid what cluster is originated from (so if you are using multicluster, the globalid is preserved when the job is forwarded)

    It can be enabled in an existing environment, and the new id's will be used from that point forward.


  • Guest
    Aug 9, 2022

    Also, is this new global unique jobid going to be in sequence/incremental?

  • Guest
    Aug 8, 2022

    Hi Bill,


    I like the proffered solution and it is exactly what we are looking for. Any idea when the next SP will be released?


    Thanks.

  • Admin
    Bill McMillan
    Aug 8, 2022

    Changing the submit time granularity would have wide reaching, and possibly disruptive impacts across the whole LSF family, and to all 3rd party tools that make use of LSF data. Such a change could also only be made at a major release.
    The next service pack for LSF will include the ability to assign a globally unique jobid across a group of clusters, and this would be the preferred solution.