×
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.
I thought I was almost done... removing *PUBLIC from my production database
library....
I have a few objects that need specific authority to allow a very small set
of users to download, or have those CPYTOIMPF, or CPYTOSTMF commands. some
objects come in through FTP, and they wind up being owned by user profile
that runs job...
but I ran into many more cases of our job scheduling tool, running commands
like "clrpfm", or setting data areas, or CPYF directly, not within a
program. and these all run as QSYSOPR, and can't be ran (without levels
of effort above what I am doing...) as QPGMR.
so, I am having to grant QSYSOPR *ALL or *CHANGE authority.
since it appears I am going back through the objects(about 3500), should I
make a *AUTL? would it just be as easy to mass perform "grtobjaut qsysopr
*all/*change" ?
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.
midrange.com
