RE: Allowing CLRPFM with Limitied Capabilities

Rob,

Great answer(s)

So, your options include:
- Using SQL instead of CLRPFM.  (Note:  will not remove deleted

records

and free up that space).
- Use a HLL program with the same limitation as above.
- Use adopted authority on a program to some profile with enough

authority

to get the job done.  Must have *ALL access to the file.

^^^^^^^^^^^^^
This one is my favorite option, though as someone else already noted,
you need *OBJMGT, not *ALL to the file (small difference, but a
difference)

- Use profile handles, but unless you have some shop standard to be
consistent the odds of you doing this versus adopted authority are

slim to

none.
- Grant the user *ALL instead of *CHANGE authority to the file.
- Give the user *ALLOBJ (but then there will be a line of people

waiting

at COMMON to "pants" you for your stupidity).  :-)

^^^^^^^^
...but - this one makes me LOL.

jte


--
John Earl, VP and Chief Technology Officer
PowerTech:   253-872-7788
Direct:          253-479-1408
John.Earl@xxxxxxxxxxxxx
 

 
First Annual PowerTech Customer User Group - iNSIGHT '07 -- March 4-6,
2007 in Las Vegas, NV
iNSIGHT '07 is the only conference focused on System i security and
compliance issues.  
Learn more! www.powertech.com/insight.asp
 
===========================
This email message and any attachments are intended only for the use of
the intended recipient named above and may contain information that is
privileged and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message or by telephone and delete the
message from your email system. Thank you.