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 Is a defect
Workspace DataStage
Created by Guest
Created on Mar 19, 2020

IBM Datastage job migrated from V11.5 to V11.7 and use the Azure File System for storage account

We have migrated our jobs from V11.5 to V11.7 environment and uses soft link to Azure file system (storage account) for users input/output files. users are not allowed to drop files on server local system due to Azure server restriction on our environment.

When we run the sequencer job , it was getting struck in the middle of some child job finish and it create a lock in UV repository. Until we clear lock, job is struck in that state. If we try to check log in director for that job, it hangs and we cant move to any further to any jobs.

Needed by Date Mar 31, 2020
  • Admin
    Scott Brokaw
    Sep 10, 2020

    Thanks for the explanation - I'm still unclear on the issue here. Please open a Salesforce ticket to have the support team investigate. For now, I will mark this as a defect, but we need to understand better the change in behavior that is being requested and we can revisit this after the investigation in the ticket.

  • Guest
    Jun 3, 2020

    Hi Scott - In the attached document, I have explained the issue in detail. I hope that clarifies your questions. we are not talking abt any specific stage issue.

  • Admin
    Scott Brokaw
    Jun 3, 2020

    Thanks for submitting an Idea. Can you please clarify your request? Are you trying to use the Azure Blob Storage Connector with DataStage? If not, which stage are you using?

    Please also clarify the expectation during migration as far as what you are looking for DataStage to do.