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

56 lines
3.4 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>Considerations for jobs that can affect 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="rzahjerrcfgjob-ref"></a>
<h4 id="rzahjerrcfgjob-ref">Considerations for jobs that can affect error recovery</h4>
<p>When a line or controller fails, and the application programs are notified,
often you must end those jobs that were running over the line and controller.
Those jobs must be started again after the communications resource is recovered.
Jobs ending (particularly abnormal job ending) should be considered from a
performance perspective as an extremely complex transaction. Use the following
links to help you recover from an abnormal job ending.</p>
<ul>
<li>Device recovery, see <a href="rzahjerrconcmnrcylmtin.htm#rzahjerr-concmnrcylmtin">Considerations for the CMNRCYLMT parameter that can affect error recovery</a></li>
<li>Prestart jobs, see <a href="rzahjerrwrkprejobsinsts.htm#rzahjerr-wrkprejobsinsts">Change prestart job entries that can affect APPC error recovery</a></li>
<li>Joblog generation, see <a href="rzahjerrwrkjoblogsinsts.htm#rzahjerr-wrkjoblogsinsts">Joblog considerations that can affect communications error recovery</a></li>
<li>Using the Change System Job (CHGSYSJOB) commands
<p>The CHGSYSJOB command
allows you to change the run priority of a system job. The following are system
jobs of interest for communications recovery:</p>
<ul>
<li>QCMNARB01 through QCMNARB99</li>
<li>QSYSCOMM1</li></ul>
<p>In general, these system jobs should be allowed to run at their
default, system-provided priority. However, if one of these jobs begins using
large amounts of CPU, and is affecting other work on the system, it is possible
to lower its priority. Note that this may result in queued-up work for that
job.</p></li>
<li>Device Wait Timeout
<p>The device wait (DEVWAIT) timeout is used to limit
the amount of time a subsystem waits for workstation input/output to complete.</p></li></ul>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>