ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaki_5.4.0.1/rzakisyschanges.htm

91 lines
6.1 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="How SMAPP handles changes in disk pool configuration" />
<meta name="abstract" content="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." />
<meta name="description" content="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." />
<meta name="DC.Relation" scheme="URI" content="rzakismappintro.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalydmkickoff.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="rzakisyschanges" />
<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>How SMAPP handles changes in disk pool configuration</title>
</head>
<body id="rzakisyschanges"><a name="rzakisyschanges"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How SMAPP handles changes in disk pool configuration</h1>
<div><p>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.</p>
<p>When you restart your system, the system checks to see if your disk pool
configuration has changed. The system does the following:</p>
<ul><li>If any disk units have been added or removed from an existing disk pool,
the system may change either the size of the SMAPP receiver or the placement
of the receiver.</li>
<li>If any new disk pools are in the configuration and do not have any access
path recovery times assigned for SMAPP, the system assigns a recovery time
of *NONE for that disk pool. If you remove a disk pool from your configuration
and later add it back, the access path for that disk pool is set to *NONE,
even if that disk pool previously had a recovery time for access paths.</li>
<li>If all basic user disk pools have been removed from your configuration
so that you have only the system disk pool, the system access path recovery
time is set to the lower of the following values: <ul><li>The existing system access path recovery time.</li>
<li>The current access path recovery time for disk pool 1. If the current
access path recovery time for disk pool 1 is *NONE, the system access path
recovery time is not changed.</li>
</ul>
</li>
</ul>
<p>When you vary on an independent disk pool, the system checks to see if
any disk units have been added or removed from the independent disk pool.
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. If this is the first
time the independent disk pool is varied on, then the system assigns a recovery
time of *NONE for that independent disk pool.</p>
<p>When you add disk units to your disk configuration while your system is
active, or your independent disk pool is varied on, the system does not consider
those changes in making SMAPP storage decisions until the next time you restart
the system, or vary on the independent disk pool. The system uses the size
of the disk pool to determine the threshold size for SMAPP receivers. If you
add disk units, the system does not increase the threshold size for the receivers
until the next time you restart the system restart or vary on the independent
disk pool. This means that the frequency of changing SMAPP receivers will
not go down until you restart the system, or vary off the independent disk
pool.</p>
<p>When you create a new user disk pool while your system is active, add all
of the planned disks to the disk pool at the same time. The system uses the
initial size of the new disk pool to make storage decisions for SMAPP. If
you later add more disk units to the disk pool, those disk units are not considered
until the next time you restart the system or vary on the independent disk
pool. When you create a new user disk pool, the access path recovery time
for that disk pool is set to *NONE. You can use the EDTRCYAP command to set
a target recovery time for the new disk pool, if desired.</p>
<p>For more information about disk pools and how to manage them, see Manage
disk units in disk pools.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakismappintro.htm" title="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.">System-managed access-path protection</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="../rzaly/rzalydmkickoff.htm">Disk management</a></div>
</div>
</div>
</body>
</html>