|
Great, thanks for the advice, Rob. /b; -----Original Message----- From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] Sent: Monday, February 12, 2007 9:57 AM To: Midrange Systems Technical Discussion Subject: Re: Allowing CLRPFM with Limitied Capabilities No, the limitation LMTCPB does not affect the ability to run that command, unless they are typing it themselves at the command line. What limits them is that they cannot simply have *CHANGE authority to the file. They have to have *ALL. Not *ALLOBJ, just *ALL to the file. Personally I think it is a stupid requirement. I can easily run a sql statement DELETE FROM MYFILE which will delete every record, but I can't run any member command like CLRPFM. 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. - 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). :-) Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.