106 lines
9.6 KiB
HTML
106 lines
9.6 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="How job logs are created" />
|
||
|
|
<meta name="abstract" content="Release V5R4 brings job logs into the "on demand" world. The job logs are available when needed, but no work is done to produce job logs for which there is no need." />
|
||
|
|
<meta name="description" content="Release V5R4 brings job logs into the "on demand" world. The job logs are available when needed, but no work is done to produce job logs for which there is no need." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjoblogpending.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogserverabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogdispchar.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinteractjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksqhistlog.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutspoolfile.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="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="rzakshowjoblogscreated" />
|
||
|
|
<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>How job logs are created</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakshowjoblogscreated"><a name="rzakshowjoblogscreated"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How job logs are created</h1>
|
||
|
|
<div><p>Release V5R4 brings job logs into the "on demand" world. The job
|
||
|
|
logs are available when needed, but no work is done to produce job logs for
|
||
|
|
which there is no need. </p>
|
||
|
|
<p>The <span class="parmname">LOG</span> parameter has three elements: the message
|
||
|
|
(or logging) level, the message severity, and the level of message text. Each
|
||
|
|
of these elements have specific values that when combined determine the amount
|
||
|
|
and type of information sent to the job log by the job. </p>
|
||
|
|
<p>For example, the *NOLIST value of the Text element causes no job log to
|
||
|
|
be produced if the job ends normally. (The job log does not go into pending.)
|
||
|
|
If the job ends abnormally (if the job end code is 20 or higher), a job log
|
||
|
|
is produced. The messages that appear in the job log contain both the message
|
||
|
|
text and the message help. </p>
|
||
|
|
<p>You can control what produces the job log. This is done with the <span class="parmname">LOGOUTPUT</span> parameter.
|
||
|
|
When a job completes, one of three actions occur that affects how the job
|
||
|
|
log is created. The following are values of the <span class="parmname">LOGOUTPUT</span> parameter:</p>
|
||
|
|
<ul><li><strong>The job log server produces the job log:</strong> (*JOBLOGSVR)</li>
|
||
|
|
<li><strong>The job itself produces the job log:</strong> If the job cannot produce
|
||
|
|
its own job log, the job log will be produced by a job log server. (*JOBEND)</li>
|
||
|
|
<li><strong>The job log is not produced:</strong> The job log remains in pending until
|
||
|
|
it is removed. (*PND)</li>
|
||
|
|
</ul>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> These values do not affect job logs that are produced when the message
|
||
|
|
queue is full and the job message queue full action specifies *PRTWRAP. Messages
|
||
|
|
in the job message queue are written to a spooled file, from which the job
|
||
|
|
log can be printed, unless the Control Job Log Output (QMHCTLJL) API was used
|
||
|
|
in the job to specify that the messages in the job log are to be written to
|
||
|
|
a database file. </div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">What controls the job log parameters?</h4><p>When a job
|
||
|
|
starts, it gets its <span class="parmname">LOGOUTPUT</span> value from the job description.
|
||
|
|
If the job description specifies *SYSVAL (the default for <span class="cmdname">CRTJOB</span>),
|
||
|
|
the job uses the job log output value that is specified in the Job log output
|
||
|
|
(QLOGOUTPUT) system value. (While the shipped value for the Job log output
|
||
|
|
(QLOGOUTPUT) system value is *JOBEND, the recommended value is *JOBLOGSVR.)
|
||
|
|
After the job has established its <span class="parmname">LOGOUTPUT</span> job attribute,
|
||
|
|
any changes to the job description or system value do not affect the active
|
||
|
|
job. Changes to the system value or to the job description take effect for
|
||
|
|
jobs entering the system after the change. </p>
|
||
|
|
<p>You can use the Change Job
|
||
|
|
(<span class="cmdname">CHGJOB</span>) command or API (QWTCHGJB) to change the <span class="parmname">LOGOUTPUT</span> job
|
||
|
|
attribute after it has already been set in the job. Changes to the job take
|
||
|
|
effect immediately.</p>
|
||
|
|
<p>Regardless of the method that you choose, the options
|
||
|
|
for handling job logs are the same. You can set the job to not produce a job
|
||
|
|
log (*PND), have the job produce the job log (*JOBEND), or have the job log
|
||
|
|
server produce the job log (*JOBLOGSVR).</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblogs.htm" title="A job log contains information related to requests entered for a job. A job log has two forms, a pending form and a spooled form.">Job logs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzaksaboutjoblogpending.htm" title="The job log pending state has been available for many years. When a job's job log attribute is *PND, no job log is produced. With the release of V5R4 enhancements have been made to both iSeries Navigator and the character-based interface so that you can now control how and under what circumstances the job log for a specific job will be produced.">Job log pending</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><a href="rzaksjoblogserverabout.htm" title="Typically the job log server writes a job's job log to a spooled file. You can route the job log to a printer or to an outfile, (if specified to do so by using the QMHCTLJL, Control job log API), however this is not the recommended method for producing job logs.">Job log server</a></div>
|
||
|
|
<div><a href="rzaksjoblogdispchar.htm" title="The iSeries Navigator provides you with a user friendly, easy to read interface from which you can view job logs and the job log's messages. You can also view job logs by using the character based interface.">Job log characteristics</a></div>
|
||
|
|
<div><a href="rzaksinteractjoblogs.htm" title="The IBM-supplied job descriptions QCTL, QINTER, and QPGMR all have a log level of LOG(4 0 *NOLIST); therefore all messages help text are written to the job log. However, the job logs are not printed if the job ends normally unless you specify *LIST on the SIGNOFF command.">Interactive job logs</a></div>
|
||
|
|
<div><a href="rzaksqhistlog.htm" title="The history (QHST) log consists of a message queue and a physical file known as a log-version. Messages sent to the log message queue are written by the system to the current log-version physical file.">QHST History Log</a></div>
|
||
|
|
<div><a href="rzaksaboutspoolfile.htm" title="A spooled file holds output data until it can be printed. The spooled file collects data from a device until a program or device is able to process the data. A program uses a spooled file as if it were reading from or writing to an actual device. This is input and output spooling.">Spooled files</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaksstoprodjoblog.htm" title="If you only want to stop the production of a particular job log, do not use the End Job Log Server (ENDLOGSVR) command. The ENDLOGSVR command ends all job log servers which results in stopping the production of all job logs.">Stop production of a specific job log</a></div>
|
||
|
|
<div><a href="rzaksstopjoblogproduction.htm" title="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 (QWTRMVJL) command or the End Job (ENDJOB) command.">Prevent the production of a job log</a></div>
|
||
|
|
<div><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>
|