89 lines
8.2 KiB
HTML
89 lines
8.2 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 server" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<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="rzaksaboutjoblogpending.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="rzakschangeautostart.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakstartjoblogserver.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksendjoblogserver.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QMHCTLJL.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="rzaksjoblogserverabout" />
|
|
<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 server</title>
|
|
</head>
|
|
<body id="rzaksjoblogserverabout"><a name="rzaksjoblogserverabout"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Job log server</h1>
|
|
<div><p>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.</p>
|
|
<p>You can view information about the job log server via iSeries™ Navigator
|
|
from the <span class="menucascade"><span class="uicontrol">Work Management</span> > <span class="uicontrol">Server
|
|
Jobs</span></span> display, or the <span class="menucascade"><span class="uicontrol">Work
|
|
Management</span> > <span class="uicontrol">Active Jobs</span></span> display.
|
|
(To make it easier to identify the jobs running on the job log server, make
|
|
sure that you include the Server column in your display.)</p>
|
|
<p></p>
|
|
<p>The maximum number of job log servers that can be active at one time is
|
|
30. You start additional job log servers and manage them in the same way as
|
|
other servers in your system. This is done by using the character-based interface
|
|
command <span class="cmdname">STRLOGSVR.</span></p>
|
|
<div class="section"><h4 class="sectiontitle">How the job log server starts</h4><p>By default, the job
|
|
log server will start automatically when the QSYSWRK subsystem starts. The
|
|
server ends whenever the QSYSWRK subsystem is ended. </p>
|
|
<p>The Start Job
|
|
Log Server (<span class="cmdname">STRLOGSVR</span>) command starts the job log server.
|
|
The job log server writes job logs for jobs that are in a job log pending
|
|
state and that do not have the attribute of *PND. The job log server writes
|
|
a job's job log either to a spooled file, to a printer, or to an outfile,
|
|
(if specified to do so by using the QMHCTLJL, Control job log API).</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="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><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="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="rzakschangeautostart.htm" title="As shipped, the job log server runs in QSYSWRK. QSYSWRK is continuously active. To enhance performance, you might want to reconfigure your job log server to run in a different subsystem.">Reconfigure the job log server</a></div>
|
|
<div><a href="rzakstartjoblogserver.htm" title="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 (STRLOGSVR) command.">Start the job log server</a></div>
|
|
<div><a href="rzaksendjoblogserver.htm" title="The End Job Log Server (ENDLOGSVR) command is used to end the job log server(s). The job log server writes job logs for jobs that are in a job log pending state. If more than one job log server job is active at the time this command is issued, all of the job log server jobs will be ended.">End the job log server</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../apis/QMHCTLJL.htm">Control Job Log Output (QMHCTLJL) API</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |