|
Tom,
CRPense gave me the following tip when I was trying to find error. The key
part was to review the QAUDJRN for Authority Failures ( T-AF codes ) in the
journal. If yo are not currently using the audit journal you can set it up
pretty easy.
CRTJRNRCV JRNRCV(YOURLIB/QAUDR0001)
CRTJRN JRN(QSYS/QAUDJRN) JRNRCV(YOURLIB/QAUDR0001)
WRKSYSVAL QAUD* and change
QAUDCTl to *AUDLVL
QAUDLVL to include at least *AUTFAIL
Now try you cmd and then use the DSPJRN cmd to serach fot the T codes with
AF
When server jobs fail to properly start, and a joblog does not
conspicuously reveal the cause, I almost always look for T-AF entries in
the auditing as a likely origin... which I have many times found to be
the cause, and thus /correcting/ the authority for the object(s) to
which the user is not authorized would resolve the problem.
As an Amazon Associate we earn from qualifying purchases.
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.