http://try-as400.pocnet.net/index.php?action=history&feed=atom&title=How_to_force_a_job_log_being_savedHow to force a job log being saved - Revision history2026-05-05T21:01:45ZRevision history for this page on the wikiMediaWiki 1.43.8http://try-as400.pocnet.net/index.php?title=How_to_force_a_job_log_being_saved&diff=1262&oldid=prevPoC: New2023-01-23T16:04:46Z<p>New</p>
<p><b>New page</b></p><div>Batch jobs running in the background finishing without errors leave no trace what exactly they have done unless an error occurred. Sometimes it's desirable '''to force a job log''' even when the job finished without error.<br />
<br />
If a job log is created or not is determined by the job description being used when the job was started. Thus, you can either create or modify a job description for such jobs, or manually force the same parameters on the <code>SBMJOB</code> command, or for an existing job with the <code>CHGJOB</code> command.<br />
<br />
Job descriptions and <code>SBMJOB</code> know a three-part parameter called ''log:<br />
* Level<br />
* Severity<br />
* Text.<br />
<br />
Just forcing a job log can be done by adding<br />
LOG(*JOBD *JOBD *SECLVL)<br />
<br />
If this doesn't provide enough details, you can also use<br />
LOG(4 0 *SECLVL) LOGCLPGM(*YES)<br />
<br />
Job logs will be placed in the default printer queue, which are determined also by the job description's ''outq'' parameter.<br />
<br />
== Weblinks ==<br />
* [https://www.ibm.com/support/pages/forcing-joblog-batch-jobs Forcing a Joblog for Batch Jobs], IBM.com<br />
<br />
[[Category: System Administration]]</div>PoC