113 lines
8.9 KiB
HTML
113 lines
8.9 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="System-managed access-path protection" />
|
||
|
|
<meta name="abstract" content="System-managed access-path protection (SMAPP) allows you to use some of the advantages of journaling without explicitly setting up journaling. Use SMAPP to decrease the time it takes to restart your system after an abnormal end." />
|
||
|
|
<meta name="description" content="System-managed access-path protection (SMAPP) allows you to use some of the advantages of journaling without explicitly setting up journaling. Use SMAPP to decrease the time it takes to restart your system after an abnormal end." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakikickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakibenefits.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakihowworks.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakichoosesap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakieffectsperform.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisyschanges.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakismappapjourn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakismappiasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiusesmapp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidisplaysmapp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnbi.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakibigrecvr.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="rzakismappintro" />
|
||
|
|
<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>System-managed access-path protection</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakismappintro"><a name="rzakismappintro"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">System-managed access-path protection</h1>
|
||
|
|
<div><p>System-managed access-path protection (SMAPP) allows you to use
|
||
|
|
some of the advantages of journaling without explicitly setting up journaling.
|
||
|
|
Use SMAPP to decrease the time it takes to restart your system after an abnormal
|
||
|
|
end.</p>
|
||
|
|
<p>SMAPP is a way to reduce the time for an iSeries™ server or independent disk pool
|
||
|
|
to restart after an abnormal end. An <span class="uicontrol">access path</span> describes
|
||
|
|
the order in which records in a database file are processed. A file can have
|
||
|
|
multiple access paths, if different programs need to see the records in different
|
||
|
|
sequences.</p>
|
||
|
|
<p>When the system or an independent disk pool ends abnormally, the system
|
||
|
|
must rebuild the access paths the next time you restart the system, or vary
|
||
|
|
on an independent disk pool. When the system must rebuild access paths, the
|
||
|
|
next restart or vary on operation takes longer to complete than if the system
|
||
|
|
ended normally.</p>
|
||
|
|
<p>When you use SMAPP, the system protects the access paths so the system
|
||
|
|
does not need to rebuild the access paths after an abnormal end. This topic
|
||
|
|
introduces SMAPP, describes SMAPP concepts, and provides setup and management
|
||
|
|
tasks.</p>
|
||
|
|
<dl><dt class="dlterm">SMAPP concepts</dt>
|
||
|
|
<dd>Use this information to find out why you might want to use SMAPP, how
|
||
|
|
it works, and how it affects your system.<ul><li>Benefits of SMAPP</li>
|
||
|
|
<li>How SMAPP works</li>
|
||
|
|
<li>How the system chooses access paths to protect</li>
|
||
|
|
<li>Effects of SMAPP on performance and storage</li>
|
||
|
|
<li>How SMAPP handles changes in disk pool configuration</li>
|
||
|
|
<li>SMAPP and access path journaling</li>
|
||
|
|
<li>SMAPP and independent disk pools</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
<dt class="dlterm">Start or change SMAPP and display SMAPP status</dt>
|
||
|
|
<dd>Use this information to start or change SMAPP and to display the status
|
||
|
|
of SMAPP on your server.<ul><li>Start SMAPP or change SMAPP values</li>
|
||
|
|
<li>Display SMAPP status</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakibenefits.htm">Benefits of SMAPP</a></strong><br />
|
||
|
|
System-managed access-path protection (SMAPP) can greatly reduce the amount of time it takes to restart your system or vary on an independent disk pool, after an abnormal end.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakihowworks.htm">How SMAPP works</a></strong><br />
|
||
|
|
The purpose of system-managed access-path protection (SMAPP) is to reduce the amount of time it takes to restart the system or vary on an independent disk pool, after an abnormal end.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakichoosesap.htm">How the system chooses access paths to protect</a></strong><br />
|
||
|
|
The system periodically examines access path exposure and estimates how long it would take to rebuild all the exposed access paths. If the rebuild time exceeds your target recovery times for access paths, the system selects additional access paths for protection.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakieffectsperform.htm">Effects of SMAPP on performance and storage</a></strong><br />
|
||
|
|
System-managed access-path protection (SMAPP) is designed to have minimal affect to your system. Though it is minimal, SMAPP does affect your system's processor performance and auxiliary storage.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakisyschanges.htm">How SMAPP handles changes in disk pool configuration</a></strong><br />
|
||
|
|
When you restart the system, the system checks to see if your disk pool configuration has changed. The system may change either the size of the SMAPP receiver or the placement of the receiver based on the change to the disk units.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakismappapjourn.htm">SMAPP and access path journaling</a></strong><br />
|
||
|
|
In addition to using system-managed access path protection (SMAPP), you can choose to journal some access paths yourself by using the Start Journaling Access Path (STRJRNAP) command. This is
|
||
|
|
called <span class="uicontrol">explicit journaling</span>.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakismappiasp.htm">SMAPP and independent disk pools</a></strong><br />
|
||
|
|
Use SMAPP to protect access paths for independent disk pools.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakiusesmapp.htm">Start SMAPP or change SMAPP values</a></strong><br />
|
||
|
|
Use the Edit Recovery Access Path (EDTRCYAP) display to start or change values for system-managed access-path protection (SMAPP).</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakidisplaysmapp.htm">Display SMAPP status</a></strong><br />
|
||
|
|
You can display many types of status for SMAPP.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakikickoff.htm" title="Journal management provides a means by which you can record the activity of objects on your system. When you use journal management, you create an object called a journal. The journal records the activities of the objects you specify in the form of journal entries. The journal writes the journal entries in another object called a journal receiver.">Journal management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrnap.htm" title="If you journal access paths, the system can use the journal entries to recover access paths instead of rebuilding them completely.">Reasons to journal access paths</a></div>
|
||
|
|
<div><a href="rzakijrnbi.htm" title="When you journal an object, the system always writes an after-image for every change that is made. You can request that the system write before-image journal entries for database files and data areas. All other object types only journal after-images. This significantly increases the auxiliary storage requirements for journaling.">Reasons to journal before-images</a></div>
|
||
|
|
<div><a href="rzakibigrecvr.htm" title="Some optional functions available with journal management can significantly increase auxiliary storage requirements.">Functions that increase the journal receiver size</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|