82 lines
7.7 KiB
HTML
82 lines
7.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="concept" />
|
|
<meta name="DC.Title" content="Job log pending" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogs.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowjoblogscreated.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="rzakscleanupjoblogpend.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjobsendatsametime.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="rzaksaboutjoblogpending" />
|
|
<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>Job log pending</title>
|
|
</head>
|
|
<body id="rzaksaboutjoblogpending"><a name="rzaksaboutjoblogpending"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Job log pending</h1>
|
|
<div><p>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. </p>
|
|
<p>This new feature is useful when you place the system into a restricted
|
|
state. When the system goes into a restricted state, subsystems end and a
|
|
potential of thousands of jobs can end at once. This in turn can create a
|
|
large burden on the output resources. By preventing the production of these
|
|
job logs, you can significantly reduce the impact on these resources. </p>
|
|
<p>Another example of when you can use this new feature is during a communications
|
|
failure. Perhaps there are many similar jobs that produce the same job log
|
|
error messages. You can set the job log to not produce a spool file for all
|
|
of the jobs. Then if there happens to be a communications failure, you can
|
|
use the Work with Job Log (<span class="cmdname">WRKJOBLOG</span>) command to determine
|
|
which logs to print. You can also use the Work with Job Logs (WRKJOBLOG) screen
|
|
to manage job logs.</p>
|
|
<p>Jobs might be in a job log pending state due to the workings of the Power
|
|
Down System (PWRDWNSYS) command. The iSeries™ Navigator user interface shows
|
|
the status "Completed - Job log pending" for these jobs. This is a subset
|
|
of character-based interface status of *OUTQ. </p>
|
|
<p>Taking advantage of these enhancements can help you to reduce the number
|
|
of job logs produced and thereby reduce the contention for resources. This
|
|
can result in improved system performance. </p>
|
|
</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="rzakshowjoblogscreated.htm" title="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.">How job logs are created</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><a href="rzaksjobsendatsametime.htm" title="Sometimes, jobs end at the same time. For example, a network error occurs and the job attributes are set to *ENDJOB or *ENDJOBNOLIST. In addition to the job ending, the following device recovery actions occur.">When jobs end at the same time</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="rzakscleanupjoblogpend.htm" title="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 (LOGLMT) 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 (WRKJOBLOG) command.">Clean up job log pending</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |