IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Spectrum LSF
Created by Guest
Created on Jan 5, 2017

Increase MAX_JOBID in PE environment - 4194303 too low

When using PE in LSF the maximum job ID is 4194303.
We have already cycled through the range in 12 months and we'll likely do it twice this year.
Having jobs with duplicate IDs causes a lot of problems with things like job accounting.

  • Guest
    Jan 9, 2017

    It is actually from PE rather than an LSF limit.

    LSF holds the jobid as a 64bit int. Half the bits represent the jobid, and half the array index. So normally you could have 2^31 jobs, and each job could have 2^31 array elements. However, PE holds the jobid as a 32bit int.

    So when PE is enabled, we have to remap the LSF jobid to just be 32bit, with 10bits to store the index, 22bits to store the job id.
    This means when PE is enabled, MAX_ARRAY_SIZE is 1000, and LSF_MAX_JOB_ID cannot be larger than 2^22-1 (4194303).

    A hack would be to split the job ranges, so PE jobs get a base ID in the range 1 .. 2^22 - 1. and non-PE jobs get a base ID from 2^22 .. MAX_JOBID. However this would still mean that have PE job would already have a duplicate in your accounting database, so it does't really address the problem.