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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.