× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Evaluating "program only access". This will allow only programs to modify
data. The users may, or may not, continue to have "*USE" access to the
data to facilitate queries.

In my understanding all this takes is some program near the top of the
chain to have USRPRF(*OWNER) and for all other programs in the chain to
have USEADPAUT(*YES).
For example, in an Infor shop you might have BPCSMENU owned by SSA and set
to USRPRF(*OWNER). Infor does a fine job of using USEADPAUT(*YES) on all
of their remaining programs.

So some user may have *USE to BPCSMENU. They could call that and then run
Infor (providing their Infor security is set up right) to their hearts
content. However, even if they did have have access to a command line,
"Run SQL Scripts", etc they would not be able to use sql or anything to
modify the data. If the data is *PUBLIC *EXCLUDE or some such thing.

I realize that this has no bearing on stream file data and that has to be
handled with profile handles.

Now, I'd like to ensure that there are no programs that were modified to
have USEADPAUT(*NO).
Doesn't seem to be a DSPPGM MYLIB/*ALL capability to an outfile.

There's no such SQL service, is there?

There's no IBM supplied security audit, is there?

Am I down to a list api, and a program API or two, to perform this audit?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.