Skip to Main Content
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 DataStage
Created by Guest
Created on May 10, 2019

Need a DataStage super operator role with export permission

We have a requirement due to SOX auditing rules that developers can have read-only access to the DataStage jobs in production. However, we would still like the developers to be able to export the jobs so they can be moved to the non-prod environments. We found the super operator role most closely fits our needs, except it does not grant permission to export jobs.

Needed by Date May 10, 2019
  • Admin
    Scott Brokaw
    Oct 20, 2020

    Thank you for the clarification. We would suggest in this case utilizing a source control system for change control/management instead of relying on exporting production assets. Keep in mind that many times, jobs are deployed to production with just runtime and not design artifacts, so the experience would not be consistent.

  • Guest
    Oct 12, 2020

    Many a times developer make inadvertent changes to jobs in DEV. This access will allow them to refresh the DEV jobs with the version in PROD

  • Guest
    Nov 26, 2019

    why would a job need to be exported from production. Shouldn't the job be available in dev already as it was moved to production eventually and why are 't you moving design artifacts to production?