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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Created by Guest
Created on Mar 15, 2019

Admin Tool - MIG: do not allocate COL DD dataset for ADB2GEN in generate job.

When generating MIG DATA for objects in BATCH the program ADB28M allocates a COL DD dataset which is used in the generated unload JCL.

This causes a security violation for unloads that are destined to run in production.

 

Example:

1. In Panel ADB28M, field 'Prefix for Datasets' is set to PGKS.DB2. This is a production HLQ that we do not have access to, but is required for the unloads to write to when they run in production.

2. ADB28M program uses this prod HLQ to allocate a COL dataset. This dataset is allocated empty. The allocation fails as our userids have no access to define production datasets.

 

Ideal solution is to create the COL dataset in the same job as the unloads rather than up front. Maybe start with an IDCAMS delete if it already exists and then define it as new. There are of course many ways to achieve the same thing.

 

At the moment we are, again, having to manipulate the JCL via rexxes to get this to work.

  • Guest
    Feb 12, 2020

    Thank you for submitting this enhancement request. While we view all the enhancement requests we receive as valuable and we would like to implement all of them, in an effort to have maximum transparency we are closing the ones that don’t currently appear on our two year product roadmap. This is not to say that these enhancements may not still be implemented at some point in the future as we constantly evaluate our requirements on the basis of customer demand and technical impact and try to deliver maximum value to our customers. We appreciate your feedback and would be happy to discuss your enhancement requests further if you’d like.