|
Thanks Scott, I think you are right about this solution being discussed before - the lightbulb went on when you mentioned QSH..... Regarding innovation - my sarcasm was directed at people who like long names, multiple directories, multiple sub-directories, etc. Finding files and adding appropriate security to the many directories used by a product like Websphere is a pain. I have whiny WPS administrator that has a recording stuck on 'give me *ALLOBJ'. Just me bitching in general - you can ignore my rants. Thanks for the input! Michael Crump Manager, Computing Services Saint-Gobain Containers 1509 S. Macedonia Ave. Muncie, IN 47302 (765)741-7696 (765)741-7012 f (800)428-8642 "The probability that we may fail in the struggle ought not to deter us from the support of a cause we believe to be just" Abraham Lincoln Scott Klement <midrange-l@scott klement.com> To Midrange Systems Technical 07/11/2005 05:13 Discussion PM <midrange-l@xxxxxxxxxxxx> cc Please respond to Subject Midrange Systems Re: IFS authority - granting to all Technical subfolders Discussion <midrange-l@midra nge.com> > I could have sworn that I had a solution for this. But on occasion > (especially dealing with Websphere and other 3rd party products) I find > myself needing to add authority to a whole load of folders and their > subfolders and the objects within. This is (relatively) easy with QShell. For simple changes, you can use "chmod" or "chown". For more complex work, you'll need to use "find" or write the list of objects to a file, and process that file from CL. For example, to give the public read access to everything in the /usr directory and all of it's subdirectories, do the following: STRQSH CMD('chmod -R o+r /usr') To make "quser" the owner of everything in the /var directory, type: STRQSH CMD('chown -R quser /var') If you need to do something more complex (like assign an authorization list) please tell me, and I'll post an appropriate CL program. > Anyway to do this with minimal effort - ie: 1 command entry. I've gone > back through my notes, checked midrange.com, and looked through TAATOOLS > and can't find anything. I could have sworn I did it a while back ago > but maybe I just dreamt it - I'm pretty sure that this was discussed on Midrange.com at least once before. > you know a solution to the wonderful type of innovation that Mr. Balmer > refers to.......sometimes I think someone's innovation is someone else's > support nightmare......... :-) The ability to mass-change permissions isn't an "innovation." It's certainly not new or particularly original. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.