Re: QSECOFR Disabled

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

I agree with Jim on this one.

I'd also recommend upgrading your OS from 7.3.

Are you paying the premium for the extended support for 7.3?  If so, you
can always try and see what IBM says.  Just might be a known issue which
has a PTF out there.

There is a PTF available for 7.5.  You can look up the legacy ptf number
for the 7.5 issue at
https://www.ibm.com/mysupport/s/defect/aCI3p0000008mtUGAQ/dt284316?language=fi
then you could always look at the 7.3 to 7.5 PTF cross reference at
https://public.dhe.ibm.com/services/us/igsc/PSP/SF97053.txt

On Mon, Oct 13, 2025 at 2:28 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> I am trying to track down what is causing QSECOFR to become disabled.
>
> I can see in the QSYSMSG message queue that QSECOFR was disabled.
>
> Using F1 confirms the profile was disabled because the maximum number of
> sign-on attempts was exceeded.
>
> If I press F9 for message details I see the following.
>
> From job . . . . . . . . . . . :   QP0ZSPWP
>    User . . . . . . . . . . . . :     QSECOFR
>    Number . . . . . . . . . . . :     787066
>
>  From program . . . . . . . . . :   QSYUSRVF
>
> Now from reading QP0ZSPWP are jobs created by spawn() and fork() functions.
>
> Looking in the history log I do not see anything just prior to the profile
> being disabled that indicates any error.
>
> In QUSRWRK subsystem I can see many QP0ZSPWP and these jobs use job
> description QGPL/ QP0ZSPWP which I was thinking of temporarily increasing
> the logging ?
>
> How can I find more information as to what is causing this profile to be
> disabled which seems to be happening a couple of times per week ?
>
> Box is a 7.3 so I can't open a case with IBM.
>
> Thanks
> Don Brown
>
>
> Brisbane - Sydney - Melbourne
>
>
> Don Brown
>
> Senior Consultant
>
>
>
>
> P: 1300 088 400
>
>
>
>
> DISCLAIMER. Before opening any attachments, check them for viruses and
> defects. This email and its attachments may contain confidential
> information. If you are not the intended recipient, please do not read,
> distribute or copy this email or its attachments but notify sender and
> delete it. Any views expressed in this email are those of the individual
> sender
> --
> 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.