Re: Complete job deletion

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

Chuck,
Joblogs going to a spool file is so passé. If you have access to a
newer machine try:
SBMJOB ... LOGOUTPUT(*PND)
Then, even after the job is ended you can do a WRKJOB, option 10 to
display joblog and there will not be an associated QPJOBLOG spool
file. ... providing the job generates a job log in the first place...
(message logging level, severity, etc)

I have no access to such a system. I was aware of the feature, and had been affected by its use where that was in effect; I setup my jobs to avoid that. Regardless, the OP said they have spooled joblogs just as the later inquirer [in another /Subject/ message] mentioned spooled juoblogs. Thus addressing the reply to me is not very helpful; i.e. the reply is not specific to me, and probably is better offered to the OP and the followup inquirer.? FWiW: Some may read the salutation and just move on to the next message without reading any further.

Anyhow I believe my point was correct, that the already spooled files named QPJOBLOG will not be deleted... No? That is to suggest... Although specifying ENDJOB LOGLMT(0) when "the job has already ended and the job log has not yet been produced, the job log is removed regardless of the value of the job log output (LOGOUTPUT) job attribute", I am confident that when the job has ended and the joblog has *already* been produced, the joblog is *not* removed regardless of the job log output (LOGOUTPUT) job attribute?? 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.