|
Sorry, but I always wonder why people need to prevent QSECOFRfrom
doing something. If you can't trust your "SECURITY OFFICER", you have
bigger problems. QSECOFR should never be restricted, in my opinion. The
whole point of this profile is to do things no one else can.If have a
problem later and need to do something, I never want to here someone say
call IBM to fix that. No one, not even QSECOFR can do that. We secured
that option. QSECOFR should have all access. you then secure the QSECOFR
profile.
I know this still leaves you the problem of securing the file, as
the original question asked. I have one question. Why do you have to
create it using SQL? From what everyone has said, DDS will give you what
you want. Just use the right tool for the job. In this case, DDS for this
particular file.
"Raul A. Jager W." <raul@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
05/30/2007 10:20 AM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc
Subject
Re: AW: Can I create an ALWUPD/ALWDLT *No file with embeded SQL?
This will work until somebody uses "GRANT".
How can we keep everybody (even QSECOFR) from giving a GRANT or CHGAUT?
______________________________________________________________________
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.