To everybody who answered, thank you...  This technique here looks pretty
straight forward... 

Thank you,
Tim

> -----Original Message-----
> From: John Earl [SMTP:john.earl@xxxxxxxxxxxxxxxxxx]
> Sent: Friday, October 10, 2003 10:05 AM
> To:   'Midrange Systems Technical Discussion'
> 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.
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.