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,
Post an idea
Upvote ideas that matter most to you
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.
IMAGECOPY support: LOAD PART to support STACK YES like REORG PART
For the subject image copy behavior in the LOAD utility, it is as the customer describes:
COPYDDN can be specified at the job / table space level but requires the RESUME or REPLACE keywords at the table space level, so this would effectively results in a table space level serialized LOAD where concurrent LOAD PART jobs cannot be run.
COPYDDN can alternatively be provided at the INTO TABLE PART level, but it is required for each INTO TABLE PART statement and hence a separate image copy data set is required on each partition being loaded
STACK YES on a COPYDDN TEMPLATE is not a possible option on the LOAD utility. Similar to REORG, the LOAD utility needs to allocate and to open/populate all the target image copy data sets at the same time while it is running in the RELOAD phase. So with STACK YES LOAD can only operate on a single image copy data set a time.
We believe what is really needs, is for LOAD PART to behave similarly like the REORG PART utility, where the utility can allocate a single inline image copy data set on a multi-part LOAD, and enable that single image copy data set to contain the pages from all target partitions loaded. That way, each LOAD PART job would only use up one tape drive, and customer can still exploit running concurrent LOAD PARTs to further reduce elapsed time (assuming there are no NPIs in the table being loaded).
Do not place IBM confidential, company confidential, or personal information into any field.