RE: Disabling QSYSOPR -- MIDRANGE-L

× 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.

Our QSYSOPR is set with
User profile . . . . . . . . . . . . . . . : QSYSOPR

Previous sign-on . . . . . . . . . . . . . : 02/07/01 11:16:10
Password verifications not valid . . . . . : 0
Status . . . . . . . . . . . . . . . . . . : *ENABLED
Date password last changed . . . . . . . . : 06/27/17 10:22:32
Password is *NONE . . . . . . . . . . . . : *YES
Change date/time . . . . . . . . . . . . . : 08/08/22 07:38:55
Last used date . . . . . . . . . . . . . . : 07/07/22

According to DSPLOG the only jobs in that time frame are:
Job 881214/ROB/ROBHQ1 started on 08/08/22 at 07:38:52 in subsystem QINTER in
Job 881215/BGEORGE/ORDSHPC started on 08/08/22 at 07:38:59 in subsystem QBATC
And all I did was DSPUSRPRF QSYSOPR. So IDK what altered the last changed date/time.

We only keep 30 days of QHST so DSPLOG was no help with "Last used date".

We are pretty intense on audit journal retention though so if you know what codes to look for to determine "Last used date" I could look that way.

Rob Berendt

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.