|
The st_mode attribute has the rights information - it is Unix-type info and does not have the object authorities, I think. It is the data authorities only, AFAIK. Vern -------------- Original message -------------- > I already use Stat. Can't see anything in the documentation regarding user > rights or object authority. > > Thanks, > > Mark > > Mark D. Walter > Senior Programmer/Analyst > CCX, Inc. > mwalter@xxxxxxxxxx > http://www.ccxinc.com > > > > Vernon Hamberg > > .net> To > Sent by: Midrange Systems Technical > midrange-l-bounce Discussion > s@xxxxxxxxxxxx > cc > > 03/08/2005 08:47 Subject > AM Re: IFS File Authority > > > Please respond to > Midrange Systems > Technical > Discussion > > nge.com> > > > > > > > These are for library objects, not the rest of the IFS. > > There is the stat() function - it is callable with CALLPRC from a CLLE > program because it uses pointers. First parameter is the path name, second > parameter is a structure that contains the various information you want - > declare a *CHAR long enough to get it all. See InfoCenter API Finder to get > > the details. Scott Klement probably has the layout translated into the > various binary, etc., data chunks. > > HTH > Vern > > At 07:15 AM 3/8/2005, you wrote: > >Hi Mark > > > >You can use the Retrieve Object Description (QUSROBJD) API to retrieve the > > >owner information for the object, and the Retrieve users Authorised to an > >Object (QSYRTVUA) API to find out any user specific authiorities (this > >includes, *PUBLIC, group, etc). > > > >All the best > > > >Jonathan > > > >-----Original message----- > >From: MWalter@xxxxxxxxxxxxxxx > >Date: Tue, 8 Mar 2005 12:37:27 +0000 > >To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx > >Subject: IFS File Authority > > > > > Is anyone aware of an API or command that will allow me to retrieve the > > > object authority and rights to a file on the IFS programmatically > without > > > having to list it to a printer file and parse that? > > > > > > Thanks, > > > > > > Mark > > > > > > Mark D. Walter > > > Senior Programmer/Analyst > > > CCX, Inc. > > > mwalter@xxxxxxxxxx > > > http://www.ccxinc.com > > > > > > -- > > > 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. > > > > > > > > >Jonathan Mason > >www.astradyne-uk.com > > > >-- > >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. > > -- > 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. > > > > -- > 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.