×
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.
Am I just being an angry bird by despising the proliferation of stuff
requiring WRKFCNUSG? For example
STR...
User QSECOFR not authorized to command STR...
Joblog contains a message like ".... You need to obtain permission from
your system administrator for function QIBM_..,_ADMIN"
CHGFCNUSG FCNID(QIBM_..._ADMIN) USER(QSECOFR) USAGE(*ALLOWED)
Now QSECOFR can use STR...
... is a redacted string so as not to draw attention to any one product but
focus overall on this WRKFCNUSG proliferation.
In my mind, if a shop is stupid enough to give *ALLOBJ to too many people
then they can easily enough do a CHGFCNUSG FCNID(QIBM_..._ADMIN)
ALLOBJAUT(*USED) and be done with it. Who are we to judge? All we're
doing is making them perform extra steps.
If everyone would use the same message id and I could simply trap that
message, read the data and automatically do a CHGFCNUSG I'd be tempted.
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.
midrange.com
