Comments on: iSeries – Can I have a program that can read QSYSOPR msgq and execute a pgm?

By: splat

splat — Wed, 11 Nov 2009 15:14:13 +0000

I’d suggest creating the QSYSMSG message queue in QSYS – messages about profiles being disabled will go there rather than to QSYSOPR. Monitoring that queue, either manually or via a program, would be easier.

I would never set up a job to automatically re-enable QSECOFR – it’s an invitation to trouble.

By: woodengineer

woodengineer — Tue, 10 Nov 2009 17:04:02 +0000

Check out the Start Watch (STRWCH) command. It allows you to watch for specific messages and take an action of your choice. Once started, it just keeps running until you end it. One of the recent newsletters included a program to re-enable a user profile when disabled by watching for the exact message you mentioned. As suggested above, we use it to watch for a common user profile many people use to log into the system to enter their time. These folks can only do that one function so it is safe to auto re-enable the user profile.

In your case, you could use the data retrieved to learn exactly when QSECOFR became disabled and who triggered it. As others have said, just re-enabling QSECOFR is not the answer. It is important to find out who is trying to use QSECOFR and stop them. Maybe someone has a script that tries to log on as QSECOFR with an old password.

I don’t know when STRWCH was introduced. We are running it on a V5R4 system.

By: jplamontre

jplamontre — Tue, 13 Sep 2005 15:32:37 +0000

if you reroute qsysopr msgq to a user program, you can have side effects when logging with qsecofr.

for a sample of break-message receiver, look at http://jplamontre.free.fr/AS400/BRKMSG.htm

for a sample of regular-basis qsysopr inspection, look at my qsysopr supervisor http://jplamontre.free.fr/AS400/SurveillerQsysopr.htm

By: thequigs

thequigs — Tue, 13 Sep 2005 14:58:27 +0000

You can monitor any message queue by using a Break Handling exit program. Here’s the URL for the V5R2 Information Center: http://publib.boulder.ibm.com/iseries/v5r2/ic2924/info/apis/XBREAK.htm

and for the V5R3 Information Center:
http://publib.boulder.ibm.com/iseries/v5r3/ic2924/info/apis/XBREAK.htm

Then you use would issue a CHGMSGQ QSYSOPR *BREAK PGM(yourlib/yourpgm)