|
Bertil: Since there doesn't seem to be much point in changing the IBM-supplied default security for QSYGETPH in the first place (assuming you're at V4R2 or later which seems reasonable because you're posting about webfacing), I can't see any reason not to grant QUSER *USE authority to it. Security problems shouldn't arise from QSYGETPH but rather from inappropriate authority to other user profiles, etc. Tom Liotta wdsci-l-request@xxxxxxxxxxxx wrote: >>From the server log. >Attempt to use permanent system object QSYGETPH without authority. >Application error. MCH1001 unmonitored by QQFWFSVR at statement > 0000000009, instruction X'0000'. > >So there is a problem when the web facing server (running under QUSER) >tries to authenticate my log on to the system or? > >We have a quite secured environment with adopted authority etc. I do not >really know where to start. I assume I can give QUSER authority to >QSYGETPH, but to what level and is that the proper way to handle it? I >have to convince the sysadmin to do it so I have to have a good >explanation if this is the way ;-)
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.