Re: CPY command works on one system, but not another...

I'll give that a shot when I'm onsite there tomorrow and let you know what I find.

TomH

-----Original message-----
From: Kirk Goins kirkgoins@xxxxxxxxx
Date: Tue, 28 May 2013 22:44:40 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: CPY command works on one system, but not another...

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.