They are listed below but are probably merged in the text.  Here is the main document link:  www.ibm.com/support/docview.wss?uid=nas8N1019545
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 09, 2014 10:35 AM
To: Midrange Systems Technical Discussion
Subject: RE: CPF1301 ACGDTA not journaled
If the documents were sent as attachments they were stripped by the list. 
Got a URL for them?
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
From:   "Bakutis, Becky" <BBakutis@xxxxxxxxxxxxxxxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:   01/09/2014 12:31 PM
Subject:        RE: CPF1301 ACGDTA not journaled
Sent by:        midrange-l-bounces@xxxxxxxxxxxx
I contacted IBM with this issue and they pointed me to these documents 
along with offering assistance.  The joblogs were being spooled due to the 
settings in the qgpl/qdftsvr jobd which was also mentioned in these 
documents.  Thanks for sending me down the right path Chuck. 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, January 07, 2014 3:39 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CPF1301 ACGDTA not journaled
On 07-Jan-2014 13:07 -0800, Bakutis, Becky wrote:
We recently restored data to a new P7 running V7R1. Now when the DDM 
service profile job runs it is creating joblogs every minute. Message
CPF1301 is getting created:
Message:   ACGDTA for 712257/QUSER/QRWTSRVR not journaled; reason 1.
Cause: Job resource accounting data for job 712257/QUSER/QRWTSRVR was 
not journaled to the system accounting journal QSYS/QACGJRN. -- 
Reason codes and their meanings follow: -- 1-The accounting level 
system value (QACGLVL) indicated that this level of resource 
accounting was not to be done when the job entered the system.
System value QACGLVL is set to *NONE. Everything I have read states to 
ignore this error. I am concerned that it is creating so many joblogs. 
The jobd is set up with message logging of 4 0 *NOLIST with End 
severity of 30. The joblog shows a severity of 30 for CPF1301.
Someone suggested adding *JOB to the QACGLVL system value plus 
whatever else needs to be done. This is not a fix, but is it the right 
solution?
   My recollection also is that the msg CPF1301 in that [and various 
other] server job(s) is innocuous, as others state; i.e. merely a side 
effect of an explicit or implicit request to effect Change Accounting Code 
(CHGACGCDE), I believe at the start of reuse of each job.
   Thus, just ignore that message...
   Instead, investigate what is causing the jobs to spool a joblog; which 
is almost surely *not* the CPF1301.  I would probably review a job trace 
to see if I could infer a reason... but perhaps searching the IBM support 
or the web more generally might find a similar issue being resolved.
   There may be a trace or debug feature active, for which producing the 
joblog is the side effect; e.g. the IBM DRDA/DDM QRWOPTIONS Debug Data 
Area.  For that specifically, review the following KB article [found be a 
web search of QRTWSRVR] to see what might have been done to start forced 
logging and thus infer how to reverse the effects:
www.ibm.com/support/docview.wss?uid=nas8N1019545
_Getting Job Log from QRWTSRVR Job_
Technote Reference #: N1019545
Historical Number: 21063654
"... Refer to Rochester Support Center knowledgebase document N1017342, 
IBM DRDA/DDM QRWOPTIONS Debug Data Area, for more information on the 
QRWOPTIONS data area. To link to document N1017342 <
www.ibm.com/support/docview.wss?uid=nas8N1017342> ..."
   Although not helpful with regard to reducing the occurrences directly, 
these may mitigate the effects on the system Work Management for number of 
jobs on the system and the amount of spool data maintained.
   The effect of /detach/ of the joblog feature from tracking to the job 
may be of some use.  The Job Description could be changed to have
SPLFACN(*DETACH) instead of SPLFACN(*KEEP).  There is a system value 
QSPLFACN.
   Also there is the Job log output (LOGOUTPUT) setting for the JOBD, 
[there is a system value QLOGOUTPUT] and that is discussed in the 
following archived message; a doc link included after:
http://archive.midrange.com/midrange-l/201005/msg00408.html
Subject: QRWTSRVR jobs in JOBLOG PENDING status?; go CLEANUP!
From: <elehti@xxxxxxxxxxxxxxxxxx>
Date: Thu, 13 May 2010 12:48:47 -0500
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzalu/rzalucontrolnumber.htm
IBM i 7.1 Information Center -> Printing -> Basic printing -> Managing 
printing -> Managing spooled files _Controlling the number of spooled 
files_
--
Regards, Chuck
--
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,
visit: 
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a 
moment to review the archives at 
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.