RE: authority question....

Sounds easy and is easy are two different things.  :-)

I copied ACR100FM into another library in my library list - ROBB13.  And 
made sure that it is locked down with *EXCLUDE.
So now it is in the following libraries in my library list:  ROB, 
BPCS405CD and ROBB13.
When I do a WRKOBJ ACR100FM I get:
Object      Type      Library     Attribute
ACR100FM    *FILE     ROB         DSPF 
ACR100FM    *FILE     BPCS405CDO  DSPF 

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

When I do:
DSPOBJD OBJ(*LIBL/ACR100FM) 
        OBJTYPE(*FILE) 
        OUTPUT(*OUTFILE) 
        OUTFILE(QTEMP/MYFILELIST)
DSPPFM QTEMP/MYFILELIST
I get:
.+....2....+....3....+....4....+
ROB       ACR100FM  *FILE   DSPF

If I move ROBB13 in front of ROB then I get the same results.

Maybe you were right?

So I tried it with this program:
      /DEFINE DSpec
      /INCLUDE ROUTINES/QAPISRC,OBJD0100
      /INCLUDE ROUTINES/QAPISRC,ERRC0100
      /UNDEFINE DSpec

      /free
       CALLP QUSROBJD(OBJD0100:
                      %LEN(OBJD0100):
                      'OBJD0100':
                      'ACR100FM  *LIBL     ':
                      '*FILE     ':
                      ERRC0100);
       dsply ExceptionId;
       dsply OBRetLib;
The value of ExceptionId was blank.  And the value of OBRetLib was ROB. 
So, using this to qualify EXTNAME might do the trick.

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 12:04 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


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

Subject
RE: authority question....






This seems simple enough...  Display all the object names
from the library list into an outfile, then CHKOBJ on each
one to see which one this group of users is authorized to.
The first one you find that you're authorized to, OVRDBF,
and execute on it.

Here's a sample - be forewarned that I used Outlook as by
editor, so the syntax may be close, but is not likely to be
flawless production level code :)



PGM

DCLF MyFileList

DSPOBJD *LIBL/TestFile OBJTYPE(*FILE) + 
 OUTFILE(QTEMP/MyFileList)

ReadLoop:
RCVF 
MONMSG CPF0864 GOTO(Error)

CHKOBJ OBJ(ODOBLB/OBODOB)OBJTYPE(*FILE) AUT(*USE)
   MONMSG CPF9802 GOTO(ReadLoop)

OVRDBF TestFile ODOBLB/OBODOB
CALL  MyApp

Error:
/* Do something here */


DLTOVR TestFile 

ENDPGM

jte



--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxxxxxxx
www.powertech.com 


> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Hatzenbeler, Tim
> Sent: Thursday, October 09, 2003 2:57 PM
> To: 'Midrange Systems Technical Discussion'
> Subject: authority question....
> 
> Is this possible?
> 
> Let say I have 2 files, named the same thing... "testfile"
> and I have
> "testfile" located in LIBA and in LIBB, and in the users
> library list, I
> have LIBA followed by LIBB,  is it possible to have a
> program read the file
> in LIBB, by *excluding the users authority to the file in
> LIBA,  instead of
> saying not authorized to the file in LIBA?
> 
> Just a curosity,
> 
> Tim
> This e-mail message, including any attachments, is for the
> sole use of the
> intended recipient(s) and may contain confidential or
> privileged
> information.  Any unauthorized review, use, disclosure or
> distribution is
> prohibited.  If you are not the intended recipient, please
> contact the
> sender by reply e-mail and destroy the message.
> _______________________________________________
> 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.