Re: Complete job deletion

On 09 Apr 2013 08:58, rob@xxxxxxxxx wrote:

If spooled joblogs are being produced, and they are still associated
with the job, why wouldn't either SPLFILE(*YES) or LOGLMT(0) on the
ENDJOB command delete them?

<snip>
AFaIK if the run-time environment is such that spooled joblogs are
being produced, whether that is desirable, passé, or otherwise, the
ENDJOB SPLFILE(*YES) LOGLMT(0) will not assist for a job which has
already spooled its joblog.
</snip>

I do not know why it works that way, but it does. The spooled files named QPJOBLOG will not be deleted if they exist. Refer to the documentation I have linked\quoted a couple times now in past messages; it is quite clearly noted in the help text for the SPLFILE parameter help text.

<only half sarcasm> I suppose it could have been because the OS development teams complained that including the QPJOBLOG spooled files in that feature to effect deletion would be yet another way the customer is likely to end up not sending in anything useful to look at when they report an issue.? </only half sarcasm>