IBM Power Ideas Portal
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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
(thumbs up) 8-)
Thank you for submitting this request. The RFE points to inconsistent behavior using Work with Object Links (WRKLNK) and other commands noting 2 distinct items.
1. Attempting to use Edit File (EDTF) and Option 9 (Recursive delete) against a directory failing that fails with CPFB620 (Object is too large to process) when the directory contains large files. The development team has investigated this failure. This is a code defect which will be corrected with a PTF in IBM i releases 7.3 and 7.4. The planned fix will not remove the limitation of viewing/edit of a file greater than 2GB in size, but will allow the "Recursive Delete" option to successfully remove large files from the directory.
2. Remove Link (RMVLNK) not supporting the SUBTREE (*ALL) option. This command will not operate against a directory. Only a directory will have a subtree to operate against so only commands that support a SUBTREE option are those that will operate against a directory. This is not something that will change. As noted in the request, using a wildcard character such as '*' in the path will remove more than a single link provided there are multiple link names that match the criteria.
We would recommend that instead of using WRKLNK option 2 (Edit) to unlink/remove objects, that you use WRKLNK, option 4 (Remove) and optionally prompt with F4. This will perform either the RMVLNK or RMVDIR commands as appropriate for the object type that you are operating against. If you use option 4 against a directory object and prompt, since it will run the RMVDIR command, it will show the SUBTREE option.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - IFS (Integrated File System) and Servers
Operating system - IBM i
Source - COMMON
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Core OS
Operating system - IBM i
Source - COMMON
If I'm understanding this correctly, the WRKLNK / Option 2 Holger is using is triggering the EDTF file manager (EDTF /)
It is this command that is issuing the Option 9 Recursive Delete and failing with CPFB620 Object is too large to process
If this is correct, if IBM fixes this in WRKLNK / Option 2 as Holger requests it will fix it in EDTF option 9 Recursive Delete which would fix it me too.
Just talked with support - this old API has issues with files >2GB. Workaround: use QSH, but we should have that native command work as expected.
Please vote :-)