ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahj_5.4.0.1/rzahjerrwrkjoblogsinsts.htm

68 lines
4.0 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" 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. -->
<meta name="dc.date" scheme="iso8601" content="2005-10-03" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<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))' />
<title>Joblog considerations that can affect communications error recovery</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzahjerr-wrkjoblogsinsts"></a>
<h5 id="rzahjerr-wrkjoblogsinsts">Joblog considerations that can affect communications error recovery</h5>
<p>You should consider whether to generate job logs when an error condition
occurs and the active jobs are ended. Producing job logs can use considerable
system resources, especially during error recovery in which many jobs end
at one time. In this case, it may be better to not generate job logs. If you
do not produce job logs, you will not have any data for analysis if something
goes wrong. There is a trade-off to be made.</p>
<p>To configure your system so that job logs are not generated, do the following:</p>
<ul>
<li>Set the DEVRCYACN parameter to *ENDJOBNOLIST. There is also a QDEVRCYACN
system value for ease of configuration.
<a name="wq58"></a>
<div class="notetitle" id="wq58">Note:</div>
<div class="notebody">The QDSCJOBITV system
value determines when the unused disconnected jobs are ended.</div></li>
<li>Change the job description (or the job itself through an initial program
for the user profile) to LOGLVL(4 0 *NOLIST). With this description, the job
logs are not generated if jobs end normally, but are generated if jobs end
abnormally.
<a name="wq59"></a>
<div class="notetitle" id="wq59">Note:</div>
<div class="notebody">Disconnected jobs also use resources. The System
Work Control Block Table can grow, which has other side effects. Do not disconnect
from jobs to which you will never reconnect.
<p>If some of your users reconnect
after a failure, however, the disconnect options can offer increased performance
for them.</p></div></li></ul>
<ul>
<li>For advanced configuration pages, see the <a href="../books/c4154010.pdf" target="_blank">Communications Configuration</a>
<img src="wbpdf.gif" alt="Link to PDF" /> book.</li>
<li>For more information about iSeries&trade; communications, see the <a href="../books/sc415406.pdf" target="_blank">Communications Management</a>
<img src="wbpdf.gif" alt="Link to PDF" /> book.</li>
<li>For system management pages, see the <a href="../rzaks/rzaks.pdf" target="_blank">Work Management</a>
<img src="wbpdf.gif" alt="Link to PDF" /> book.</li></ul>
<p>For related information, see:</p>
<ul>
<li><a href="rzahjerrcfgjobref.htm#rzahjerrcfgjob-ref">Considerations for jobs that can affect error recovery</a></li>
<li><a href="rzahjerrcomsysvalref.htm#rzahjerr-comsysvalref">Considerations for communications-related system values</a></li></ul>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>