This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Inconsistent delete image catalog operation in IBM i
I recently encountered a confusing usage of the "delete" operation of Image Catalog object in IBM i V7R2 and need to ask a question to seek a response.
A few weeks ago, I had a chance to use IBM i Image Catalog object in my task delivery to a customer. When I worked with image catalog in IBM i V7R2, I had an occasional need to delete the image catalog objects. I used the command DLTIMGCLG which offered a parameter named "Keep Image Files" which is defaulted to *YES which is what I needed. But when I also used WRKIMGCLG command later on, I found that using its option 4 = Delete on the image catalog deleted all its associated files without asking me if I want to keep them and this caused me a surprising trouble in my work as I needed to re-transfer the (very large) files from my PC to IBM i again which wasted my time. I look into Knowledge Center web site and found that this is BY DESIGN for WRKIMGCLG command.
Now, I have to say this causes a serious CONFUSION to me (and presumably other people) who also know and use DLTIMGCLG command which defaults to keeping all the file while deleting just the image catalog object itself.
So, I wonder why there is such a potentially confusing conflict between using option 4 = Delete in WRKIMGCLG and DLTIMGCLG command ?
This is the very first time in my 27-year experience with IBM i that I find that the very same operation behaves differently when invoked from WRK... command than from its specific command.
I see that this behavioral difference should be considered as a design flaw that does not comply to the past in which any operation in WRK... commands would be CONSISTENT with the same operation provided by its individual command.
I would see that this issue should be rectified in the currently supported IBM i releases as PTFs and in the base code of future releases. This means that option 4 = Delete in WRKIMGCLG command should be promptable (F4) and provide the same options as those provided by DLTIMGCLG command.
Do not place IBM confidential, company confidential, or personal information into any field.