RE: CPF1393

Good idea but there's an extra step: Change the owner of QSYS/QSYSMSG to QSECOFR, or create it with QSECOFR.

Incomplete results otherwise.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Thursday, May 6, 2021 2:07 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CPF1393

Create a message queue named QSYSMSG in QSYS. Then in addition to sending critical messages to QSYSOPR (and QHST) the system will also send them to QSYSMSG.

It is then easy to write a program to monitor QSYSMSG for certain errors and "take appropriate action." (CPF1393 does get sent to QSYSMSG.)

On Thursday, May 6, 2021, 2:38:17 PM EDT, dr2@xxxxxxxx <dr2@xxxxxxxx> wrote:

OK, the windoze guys evidently get a message when a windoze has disabled a usrprf. The question du jour is, other than monitoring for a msgid in QHST, is there a way to be proactively informed when someone gives you a CPF1393?

(CPF1393 is generated when you screwup your password so many times you get disabled)

Thanks

/DR2
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com