×
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.
Hello Gad,
Am 31.01.2022 um 11:51 schrieb Gad Miron <gadmiron@xxxxxxxxx>:
I would like the person(s) who acts as our SYSOP to use his own user profile and not QSYSOPR
So I could disable QSYSOPR and thus reduce our "Radar footage" for hacking.
Now, is there a way to route all QSYSOPR Messages to him? (In addition to his own messages)
Why clutter his message queue with QSYSOPR messages? Even QSECOFR does not "see" QSYSOPR messages without explicitly stating that upon calling DSPMSG.
I recommend to change the QSYSOPR message queue authority so that your other user (or an assigned group profile) is able to have write access to the QSYSOPR message queue (so he's able to delete messages) and instruct him to look into it regularly.
I had never come across the thought to directly sign on as QSYSOPR anyway. But then, I'm just a hobbyist.
:wq! PoC
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
