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.
DataStage - orchadminn cp command - copy the schema and contents with the target
orchadminn cp command doesn't copy the schema if the target file already exists. IHAC knows that it works fine if the target is deleted and orchadminn cp is executed. However, the man page is not clear,
Copy the schema, contents and preserve-partitioning flag of the specified ORCHESTRATE file dataset. If the preserve-partitioning flag is set, the copy will have the same number of partitions and record order as the original. If the target file already exists, it will be truncated first. If the preserve-partitioning flag of the source file is set and the target file already exists, it must have the same number of partitions as the source file.
The customer think that the behavior should be changed.
Even though the target file already exists, "orchadminn cp" copy the schema and contents.
Some warning messages which mean the schema was not copied are output.
Do not place IBM confidential, company confidential, or personal information into any field.