I am getting many flags where the CURRENT_USER of a job are QSECOFR. It's making it really hard to sort the wheat from the chaff.
To me this points to IBM swapping profiles to QSECOFR for many APIs. We've checked and we are not swapping profiles nor are we adopting authority of QSECOFR.
This one job does a
Eval Cmd = 'SAVOBJ OBJ('+%trim(PmQuery)+') LIB(' +
%Trim(CurLib) + ') ' +
'DEV(*SAVF) ' +
'OBJTYPE(*QRYDFN) ' +
'SAVF(QTEMP/QRYSAVF) ' +
'UPDHST(*NO) ' +
'SAVACT(*SYSDFN) '
ExSr $System
This generates CA and ZC entries with a current user profile of QSECOFR even though the job runs as a profile with much less authority.
Object types are *DIR and *STMF.
Based on the PATH_NAME values of
/QSR/QSR
/QSR/QSR/HL
Etc
I assume it's the save/restore flight recorders.
SELECT x.*
FROM TABLE (QSYS2.Display_Journal(
JOURNAL_LIBRARY => 'QSYS',
JOURNAL_NAME => 'QAUDJRN',
STARTING_RECEIVER_LIBRARY => 'QGPL',
STARTING_RECEIVER_NAME => '*CURCHAIN',
STARTING_TIMESTAMP => TIMESTAMP('2019-07-26-04.00.02'), ENDING_TIMESTAMP => TIMESTAMP('2019-07-26-04.02.05')
)) X
WHERE ( x."JOB_NAME" = 'ERPQRYFLST')
;
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
As an Amazon Associate we earn from qualifying purchases.