Re: Any way to avoid QPJOBLOG?

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Siva

There is no way not to get a joblog of some kind when a job ends abnormally 
that I know of. You can minimize the size by specifying 99 for severity, 
turn off CL command logging (except that a program setting can override 
this), and use *NOLIST.

Having said this, you could try the job notification exit point. This is 
specified in the registry (WRKREGINF - look for "Job notification" in the 
text description. You could set this for when jobs end and maybe you could 
DLTSPLF there - I don't know the timing involved - is the job log printed 
before the notification is sent? You want to look this up in the API finder 
in V5R3 InfoCenter. If it is not yet available, send the job information to 
a DTAQ and have another job waiting on that queue, which will wait until 
the job is in *OUTQ status and delete the joblog, if found.

There was a good discussion on logging recently on the list. You might go 
to the archives - link is at the bottom of each message - and search on 
"job log full" or "job message queue".

HTH
Vern

At 11:06 PM 3/18/2005, you wrote:
> Hi
>
> Whenever the job ends abnormally , QPJOBLOG is generated. How to avoid 
> this , since the size of the spool file is too large, i need to avoid 
> this. Hwo to do that?.
>
> CHGJOB/CHGJOBD is not halping in this. Even changes of message severity, 
> level and text logging and CL PRG comment logging in SUBJOB command also 
> ends in vain. Any help?
>
> One more things will QPJOBLOG get created only when job ends abnormally 
> otherwsie will the normal execution of job also create QPJOBLOG???. please 
> clear me.
>
> Thanks
> Siva
>
>
> ---------------------------------
> Do you Yahoo!?
>  Yahoo! Small Business - Try our new resources site!
> --
> 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.