Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


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
    Reply
    |
    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.