55 lines
3.3 KiB
HTML
55 lines
3.3 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-09-06" />
|
|
<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>Communications performance considerations for batch jobs</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="rzajtper-combatchjobsin"></a>
|
|
<h4 id="rzajtper-combatchjobsin">Communications performance considerations for batch jobs</h4>
|
|
<p>Each piece of work run on the iSeries™ system is called a job. Each job
|
|
is a single, identifiable sequence of processing actions that represents a
|
|
single use of the system. The basic types of jobs that are performed are interactive
|
|
jobs, batch jobs, spooling jobs, autostart jobs, and prestart jobs.</p>
|
|
<p>Batch jobs are predefined groups of processing actions that are submitted
|
|
to the system to be performed with little or no interaction between the user
|
|
and the system. Batch jobs can be tuned for optimized performance.</p>
|
|
<p>To optimize batch jobs for communications, consider the following:</p>
|
|
<ul>
|
|
<li>Break the application into pieces and having multiple batch threads (jobs)
|
|
operate concurrently.</li>
|
|
<li>Reduce the number of open and close operations, input and output operations.</li>
|
|
<li>If you have a considerable amount of main storage available, consider
|
|
using the Set Object Access (SETOBJACC) command. This command preloads the
|
|
complete database file, database index, or program into the assigned main
|
|
storage pool if sufficient storage is available. The objective is to improve
|
|
performance by eliminating disk-read/write operations.</li>
|
|
<li>Try to limit the number of communications input and output operations
|
|
by doing fewer (and perhaps larger) application sends and receives when communications
|
|
lines are used.</li>
|
|
<li>Block the data in the application. Try to place the application on the
|
|
same system as the frequently accessed data.</li></ul>
|
|
<p>For more information about batch job performance, see the <a href="../books/sc415406.pdf" target="_blank">Communications Management</a>
|
|
<img src="wbpdf.gif" alt="Link to PDF" /> book.</p>
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|