|
I always thought it rather strict that a person needs *ALL access to a file to do CLRPFM, ADDPFM, RMVPFM but *CHANGE is ok to do strsql delete from myfile Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/26/2004 02:31 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Losing Authority to a file in Batch There are very valid reasons to specify USRPRF(*OWNER). For example: I want a user to be able to add a member to a file, but I don't want *PUBLIC to have either that authority in their profile or to the file. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Jim Damato <jdamato@dollarge neral.com> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 01/26/2004 01:53 Subject PM RE: Losing Authority to a file in Batch Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Have you ever had to expose your system to a security audit? Programs compiled as USRPRF(*OWNER) are among the first things to go. -Jim James P. Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@xxxxxxxxxxxxxxxxx> -----Original Message----- From: Malchow, Grizzly [mailto:GMalchow@xxxxxxxxxxxxxxxxxxxxx] Sent: Friday, January 23, 2004 12:58 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: Losing Authority to a file in Batch Apparently my user profile has been changed. Whenever I used to compile programs, the user ID default was *OWNER. Now I noticed that the default is *USER. I recompiled with *owner and that solved my problems. Thanks everyone. _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.