110 lines
8.8 KiB
HTML
110 lines
8.8 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Manage job logs" />
|
||
|
|
<meta name="abstract" content="Most jobs on your iSeries have a job log associated with it. Job logs tell you many different things such as when the job starts, when the job ends, what commands are running, failure notices and error messages. This information gives you a good idea of how the job cycle is running." />
|
||
|
|
<meta name="description" content="Most jobs on your iSeries have a job log associated with it. Job logs tell you many different things such as when the job starts, when the job ends, what commands are running, failure notices and error messages. This information gives you a good idea of how the job cycle is running." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksdailyworkmanage.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksmanagejoblogserver.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakstartjoblogserver.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaccessjoblog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalsfindjoblog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogoutputqueue.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksstoprodjoblog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksstopjoblogproduction.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscontroljobloginfo.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksdeljoblog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjlpendviewjoblog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakscleanupjoblogpend.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="rzakswrkjoblog" />
|
||
|
|
<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>Manage job logs</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakswrkjoblog"><a name="rzakswrkjoblog"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Manage job logs</h1>
|
||
|
|
<div><p>Most jobs on your iSeries™ have a job log associated with it. Job logs
|
||
|
|
tell you many different things such as when the job starts, when the job ends,
|
||
|
|
what commands are running, failure notices and error messages. This information
|
||
|
|
gives you a good idea of how the job cycle is running.</p>
|
||
|
|
<p>The following information discusses the various tasks that you can perform
|
||
|
|
when working with job logs.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksmanagejoblogserver.htm">Manage the job log server</a></strong><br />
|
||
|
|
The QSYSWRK subsystem controls the job log server. However, there are some tasks that you can perform to customize or manage the job log server.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakstartjoblogserver.htm">Start the job log server</a></strong><br />
|
||
|
|
By default, the job log server automatically starts when the QSYSWRK
|
||
|
|
subsystem starts. You can manually start a job log server by using the Start
|
||
|
|
Job Log Server (<span class="cmdname">STRLOGSVR</span>) command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksaccessjoblog.htm">How to display job logs</a></strong><br />
|
||
|
|
You can see a job log from any place within work management that
|
||
|
|
you access jobs, such as through the Subsystem area or the Memory Pool area.
|
||
|
|
You can use iSeries Navigator
|
||
|
|
or the character-based interface to display job logs.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzalsfindjoblog.htm">What to do when the job log won't display</a></strong><br />
|
||
|
|
In iSeries Navigator,
|
||
|
|
to find and display a job log, whether a batch job or an interactive job,
|
||
|
|
right-click the job and then click <span class="uicontrol">Job log</span> from the
|
||
|
|
menu. However, depending upon the status of your job or how the job log values
|
||
|
|
were set in the job description, your job log may be in the output queue,
|
||
|
|
or it may be in a job log pending status or it may not be available. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjoblogoutputqueue.htm">Specify the output queue for a job log</a></strong><br />
|
||
|
|
By default the printer file that is used to spool a job log is QPJOBLOG. You can have multiple QPJOBLOG printer files on your system. In QSYS the output queue that the OUTQ attribute uses is QEZJOBLOG, in library QUSRSYS. When the system creates a job log, it looks for the printer file QPJOBLOG in the job's library list. The first one that is found is the one that it uses. You use the character-based interface to adjust these settings.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksstoprodjoblog.htm">Stop production of a specific job log</a></strong><br />
|
||
|
|
If you only want to stop the production of a particular job log,
|
||
|
|
do not use the End Job Log Server (<span class="cmdname">ENDLOGSVR</span>)
|
||
|
|
command. The <span class="cmdname">ENDLOGSVR</span> command ends all job log servers
|
||
|
|
which results in stopping the production of all job logs. </li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksstopjoblogproduction.htm">Prevent the production of a job log</a></strong><br />
|
||
|
|
Preventing the production of a job log is useful if you already
|
||
|
|
know that you will not need the job log and you want to conserve system resources.
|
||
|
|
When you specify that you do not want to produce a job log, the job log will
|
||
|
|
not be produced and remains in pending until removed either by the Remove
|
||
|
|
Pending Job Log (<span class="cmdname">QWTRMVJL</span>) command or the End Job (<span class="cmdname">ENDJOB</span>)
|
||
|
|
command.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakscontroljobloginfo.htm">Control information in a job log</a></strong><br />
|
||
|
|
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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksdeljoblog.htm">Delete job log output files</a></strong><br />
|
||
|
|
Job logs are removed from the system when a job completes normally,
|
||
|
|
or when the Remove Pending Job Log (QWTRMVJL) API or the End Job (<span class="cmdname">ENDJOB</span>)
|
||
|
|
command is issued. Additionally if "clear incomplete job logs" is specified
|
||
|
|
on the IPL, all of the jobs in job log pending will be removed from the system
|
||
|
|
during an IPL. Any remaining job log output files can be found under <span class="menucascade"><span class="uicontrol">Basic Operations</span> > <span class="uicontrol">Printer Output.</span></span></li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksjlpendviewjoblog.htm">Produce printer output from job log pending</a></strong><br />
|
||
|
|
Jobs that do not have the iSeries Navigator <span class="uicontrol">Job Properties
|
||
|
|
- Job Log</span> setting, <span class="uicontrol">Produce a job log</span> field
|
||
|
|
selected do not produce job logs. Instead the job log is in job log pending.
|
||
|
|
To produce printer output from a job log that is in job log pending,
|
||
|
|
use the character-based interface.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakscleanupjoblogpend.htm">Clean up job log pending</a></strong><br />
|
||
|
|
There are a few ways to clean up, or remove jobs from job log pending.
|
||
|
|
You can end the job with a value of 0 for the Maximum log entries (<span class="parmname">LOGLMT</span>)
|
||
|
|
parameter. If the job is already ended, you can run the Remove Pending Job
|
||
|
|
Log (QWTRMVJL) API. You can also use the Work with Job Logs (<span class="cmdname">WRKJOBLOG</span>)
|
||
|
|
command.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksdailyworkmanage.htm" title="As a system operator or administrator, one of your tasks is to keep your server running smoothly. This means you monitor, manage, and ensure that your jobs, job queues, subsystems, memory pools, job logs, and output queues function properly.">Manage work</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|