I was headed down that path until I learned that *USE at the library level
applies to whether you can use items within the library. If you have *USE to
the library and *CHANGE to an object. you can change the object. Furthermore,
*USE at the library level permits a delete.
-----Original Message-----
From: security400-bounces@xxxxxxxxxxxx
[
mailto:security400-bounces@xxxxxxxxxxxx]On Behalf Of Edwin Davidson
Sent: Tuesday, June 12, 2007 3:45 PM
To: Security Administration on the AS400 / iSeries
Subject: Re: [Security400] Private authority report
Couldn't you just specify at the library level ODBCuser *use ?
Wouldn't that be easier and achieve the same results, in your case? You
can do this without having to deal with file locks. That's how we
approached some libraries in a case similar to this.
**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please reply to the sender of the message.
The views expressed in this correspondence may not
reflect the views of Prime, Inc.
This footnote also confirms that this email message has
been scanned for the presence of computer viruses.
http://www.primeinc.com
**********************************************************************
midrange.com
