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 Future consideration
Workspace DataStage
Created by Guest
Created on Dec 1, 2020

Request to easily integrate custom scripts into the managed, SaaS DataStage Runtime

Our company is using Cloud Pak for Data as a managed service, which means we don't have direct access to the OpenShift platform or any of the pods or servers that run the Cloud Pak services, like the DataStage server.

Occasionally with on-prem DataStage we'll build custom scripts in Python or bash that do pre or post processing on data in order to more effectively ingest or, or do do the actual initial ingestion itself (like when using external API's).

To give an example, in the past I have written scripts that invoke external API's like Google DoubleClick to pull the data from an external source via the Execute Command stage in a Sequence job, land it to a temporary file on the DataStage ETL server, and then use those files as input to the normal ingestion process in DataStage.

The current process to get a script to the cloud is to send it over to our IBM support contact and have them upload it for us, but the problem with this approach is we have no real way of testing how it will work in the target system without sending it over so:

  1. IBM support uploads

  2. We try to run it, see the error(s)

  3. Tweak it again

  4. Send it over again, and the process repeats

Some things we can test locally and might just require different filepaths to get it working on that environment, but not being able to just tweak it in the actual environment is a bit like flying blind.

IBM mentioned they have this feature documented, but no roadmap for getting it implemented:

Needed by Date Jan 1, 2021
  • Guest
    Dec 3, 2020

    Thanks Scott, I'm okay with the modified Title and also fine with any solution that would enable us to upload the scripts ourselves to some contained area of DataStage. I'm actually OOO for the rest of the month after tomorrow, so maybe we can meet in early January to discuss further, let me know.

  • Admin
    Scott Brokaw
    Dec 3, 2020

    Thank you for submitting this request for enhancement. I would like to have a deeper conversation with you regarding this request. As we look to bring DataStage to a SaaS (fully managed service), there will be certain security requirements that will prevent the sort of direct access you are referring to. However, this would be available in a private cloud deployment utilizing Cloud Pak for Data. That said, we will have mechanisms in place to allow for the inclusion of custom components such as Python or bash scripts into the managed runtime without having to open a ticket with support.

    I will accept this request for enhancement as I think we're able to meet the intent of your request, we just will not implement it by exposing the ability to directly SSH into the managed runtime. Please let me know if you would like to have a more in-depth conversation and if you agree with my re-phrasing of the title.