The QSECOFR profile can still be used to sign on to the system console even if it's disabled.

Paul Fenstermacher | Sys Admin, Sr | Corporate Systems - POWER Systems
Administration | Jack Henry & Associates, Inc.
663 West Highway 60 | Monett, MO 65708 | 417-235-4114 x177389 |

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Lavinder
Sent: Wednesday, August 13, 2014 11:08 AM
To: midrange-l@xxxxxxxxxxxx
Subject: QSECOFR Profile Oddness

Does anyone know much about how QSECOFR is treated? We did a penetration test back in July and during the test QSECOFR was disabled.
We did not find that out until today. When we go to WRKUSRPRF it shows a successful sign-on occurring Saturday (8/9). We IPL on Saturday, but it bugs us that we see it signing on when it was supposedly disabled.

I am just looking for some peace of mind that this is what we should see. When we discovered the profile was disabled we initially assumed it had been disabled after that successful sign-on Saturday morning, but the only disabled message we found in the logs occurred back in July.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page