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 Delivered
Created by Guest
Created on Jul 4, 2016

HPU: support for common templates for multiple selects RFE 90963

When the same OUTDDN is used in several selects, HPU accepts to write in the same file the result of several select statements. We use a template to avoid having to allocate manually the output files. With AUTOTAG keyword or not HPU does not correlate the AUTOTAG and the controls for the TEMPLATE allocation at the moment. We have had a discussion already with Infotel and were asked to open that RFE.

Use Case:

We have to unload e.g. three tablespaces with 250 partitions each. The UNLOAD for each of these tablespaces will be done by PARTition, by means of three SELECT statements with a common OUTDDN. So, each of these output files, which are generation data sets, will contain the combined result of the four SELECTs for a single partition of a single tablespace. Of course, the easiest way to specify such an OUTDDN is using a TEMPLATE containing the &TS and &PART variables. IF HPU supported TEMPLATEs resolving to the same data set name for multiple SELECTs, we could avoid • the explicit specification of 750 different DD statements for OUTDDN • the explicit DEFINition of 750 GDG base entries using IDCAMS, as TEMPLATE processing does this automatically if needed. We would prefer a solution without the need to additionally specify the AUTOTAG operand, because in our case, there is no use tagging the output rows. Possibly, a new OPTION keyword might be introduced to enforce HPU's accepting a common TEMPLATE under the conditions mentioned above.