RE: authority question....

[rob@xxxxxxxxx]

Actually John, they wanted the first one they had access to.  Therefore 
using that API, or the long drawn out way of DSPOBJD *LIBL/OBJ to an 
outfile and processing that should work just fine.  Me, I prefer the API. 
Not counting the includes, you saw how simple it was.

The only time you get dinged is if you do the DSPOBJD (hardcodedlib)/obj 
on an object you don't have authority to.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"John Earl" <john.earl@xxxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/10/2003 03:13 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: authority question....






Rob,

> When I do DSPOBJD ROBB13/ROB *FILE I get:
> Not authorized to object ACR100FM in ROBB13 type *FILE.

Good catch!  I missed that one.  OK, so modify the approach
in one of the following two ways:

1) - Place the DSPOBJD in an external program, and have it
adopt enough authority to display all the occurrences of
file "TestFile"
                                                                 OR
2) - Give all of the users *OPJOPR to all of the files, but
not any Data Rights.  The Object Operations rights will
allow them to list the properties of the file, but the
CHKOBJ will still fail if you specify AUT(*USE) or
AUT(*CHANGE).

For ease of use and long term management, I would personally
probably go with #1.


Still, a good catch Rob.

jte 





_______________________________________________
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.