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
IFS: Add attribute that objects created in that directory use the authority of the parent.
In the QSYS.LIB file system I can run CHGLIB LIB(MYLIB) CRTAUT(MYAUTL) and now any new object created in that library will have the authority as per the authorization list MYAUTL. I am looking for something similar for the IFS. For example, if I create an authorization list MYAUTL and have user TOM as a member and try this: CRTDIR DIR('/SampleDirectory') DTAAUT(GDIDIVF) OBJAUT(*NONE) edtf '/SampleDirectory/deleteme.txt' dspaut '/SampleDirectory/deleteme.txt'
the object '/SampleDirectory/deleteme.txt' does not have the authority of the authorization list but has what you see with *PUBLIC. So, if TOM is a member of MYAUTL he still cannot delete this file.
Data --Object Authorities-- User Authority Exist Mgt Alter Ref *PUBLIC *RW ROB *RW X X X X
There are some commands with a hack in them to help with this crippling limitation. For example the CPY command as the AUT(*INDIR) parameter CPY OBJ('/fromdir/fromfile') TOOBJ('/todir/tofile') AUT(*INDIR)
I'm not saying that authorization lists should be a requirement (although I like them and would accept that) but something like CHGATR OBJ('/SampleDirectory') ATR(*CRTOBJAUT) VALUE(*INDIR) would be acceptable also. Maybe even preferred.
I have directories now in which even the user who creates file (when using a Client/Server tool instead of EDTF) cannot delete the file.
Do not place IBM confidential, company confidential, or personal information into any field.