61 lines
4.7 KiB
HTML
61 lines
4.7 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="task" />
|
|
<meta name="DC.Title" content="Control batch job log information" />
|
|
<meta name="abstract" content="For your batch applications, you may want to change the amount of information logged. The log level (LOG(40 *NOLIST)) specified in the job description for the IBM-supplied subsystem QBATCH supplies a complete log if the job abnormally ends. If the job completes normally, no job log is produced." />
|
|
<meta name="description" content="For your batch applications, you may want to change the amount of information logged. The log level (LOG(40 *NOLIST)) specified in the job description for the IBM-supplied subsystem QBATCH supplies a complete log if the job abnormally ends. If the job completes normally, no job log is produced." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscontroljobloginfo.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004-2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaksbatchjoblogs" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Control batch job log information</title>
|
|
</head>
|
|
<body id="rzaksbatchjoblogs"><a name="rzaksbatchjoblogs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Control batch job log information</h1>
|
|
<div><p>For your batch applications, you may want to change the amount
|
|
of information logged. The log level (LOG(40 *NOLIST)) specified in the job
|
|
description for the IBM-supplied subsystem QBATCH supplies a complete log
|
|
if the job abnormally ends. If the job completes normally, no job log is produced.</p>
|
|
<div class="p">Controlling job logs at the job queue level (QBATCH) is done by adjusting
|
|
the job log settings for the QBATCH subsystem job. You have the same options
|
|
for controlling how job logs are produced at the subsystem job level as you
|
|
do at the individual job level.</div>
|
|
<div class="section">To adjust the job log settings for the job queue subsystem, do the
|
|
following:</div>
|
|
<div class="p"><span>In iSeries™ Navigator
|
|
open the <span class="uicontrol">Subsystem Properties - Job Log</span> window for
|
|
the job queue subsystem. </span> (<span class="menucascade"><span class="uicontrol">Work Management</span> > <span class="uicontrol">Subsystems</span> > <span class="uicontrol">Active Subsystems</span> > <span class="uicontrol">QBATCH</span> > <span class="uicontrol">Right-click the QBATCH job</span> > <span class="uicontrol"> Properties</span> > <span class="uicontrol">Job Log tab</span></span>)</div>
|
|
<div class="section"><div class="note"><span class="notetitle">Note:</span> If you uncheck the <span class="uicontrol">Produce a job log field</span> field
|
|
(*PND) for the subsystem, the job log specific to the subsystem
|
|
will not be listed with the other printer output. You will then need to use
|
|
the Display Job Log (<span class="cmdname">DSPJOBLOG</span>) command to view the pending
|
|
job log.</div>
|
|
<p>If the batch job is running a CL program, the CL program
|
|
commands are logged only if the LOGCLPGM(*YES) is specified on the Create
|
|
Control Language Program (<span class="cmdname">CRTCLPGM</span>) command or the Change
|
|
Program (<span class="cmdname">CHGPGM</span>) command.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakscontroljobloginfo.htm" title="When working with problems, you might want to record the maximum amount of information for jobs that have frequent problems. Alternatively, you might not want to create a job log for jobs that completed normally. Or you might want to exclude informational messages.">Control information in a job log</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |