The jobd I originally looked at was tied to the user profile used for addsvraute which was qgpl/qdftjobd. Those settings were fine. The jobd mentioned in the document you sent a link for was qgpl/qdftsvr. This jobd on my system had the settings set as 4 0 *SECLVL with CL Logging *YES. This has stopped a large number of spool files which was my original concern.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, January 09, 2014 11:26 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: CPF1301 ACGDTA not journaled

On 09-Jan-2014 09:29 -0800, Bakutis, Becky wrote:
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 <<SNIP>>

What change was performed to /resolve/ the issue? The OP stated the Job Description was already LOG(4 0 *NOLIST).? If truly corrected by a change to the JOBD, does that imply the *NOLIST was not previously set for the message level value of the LOG parameter as noted in the OP, or that the severity level was being exceeded for the job end? If the job was exceeding the end severity, a change that prevents the job log from being produced is likely just masking that issue; i.e. the reason for the job exceeding the end severity would best be resolved. Similarly if the joblog was being spooled while LOG(4 0 *NOLIST) was in effect, and a change was made to LOGOUTPUT(*PND) to mitigate the effects of the joblog spooling, e.g. by making the joblogs /pend/ instead of *JOBEND or *JOBLOGSVR, that is also just masking the original concern; i.e. if the job is not supposed to produce a joblog due to the combination of *NOLIST and ENDSEV, then it should neither generate a QPJOBLOG nor effect a *PND joblog.

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page