ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaly_5.4.0.1/rzalyhowiaspswork.htm

113 lines
7.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 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="topic" />
<meta name="DC.Title" content="How independent disk pools work" />
<meta name="DC.Relation" scheme="URI" content="rzalyconcepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalysupportedunsupportedobjects.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalydatabases.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalymultiplesystemlibraries.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyobjectidentification.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyprintingconsiderations.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalyswitchbetweenv5r1andv5r2.htm" />
<meta name="DC.Relation" scheme="URI" content="rzalystartup.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2002, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzalyhowiaspswork" />
<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 independent disk pools work</title>
</head>
<body id="rzalyhowiaspswork"><a name="rzalyhowiaspswork"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">How independent disk pools work</h1>
<div><p>The key characteristic of an independent disk pool is its ability to be,
of course, <em>independent</em> of the rest of the storage on a server. It
is independent because the data in the independent disk pool is self-contained.
This means that all of the necessary system information associated with the
data resides within the independent disk pool. The unique qualities of an
independent disk pool allow it to be switched in a multisystem environment
and to be made available and unavailable in a single-system environment.</p>
<p>Independent disk pools are available only when you choose to make them
available; they are not made available when you restart your server, unless
you include code (<a href="rzalystartup.htm">Example: Make independent disk pool available at startup</a>) to
make them available. When you select to make a disk pool available, the disk
pool goes through a process similar to that of restarting the server. While
this processing takes place, the disk pool is in an Active state.</p>
<p>While the disk pool is in Active state, recovery steps are being performed.
The disk pool is synchronized with other disk pools that may be in the disk
pool group. Also, journaled objects are synchronized with their associated
journal. System libraries are created for the primary disk pool: QSYSnnnnn,
QSYS2nnnnn, QRCLnnnnn, QRCYnnnnn, QRPLnnnnn, SYSIBnnnnn (where <em>nnnnn</em> is
the primary disk pool number, right-aligned and padded with zeros). For example,
the QSYS library for independent disk pool 33 is QSYS00033. </p>
<p>At this time database cross-reference files will also be updated. The system
libraries for the independent disk pool, QSYSnnnnn and QSYS2nnnnn, contain
metadata not only for the independent disk pool, but also for the system disk
pool. When the disk pool is made available, database cross-referencing clears
the information related to SYSBAS and updates it with current information.
The number and complexity of database file objects and SQL packages, procedures,
and functions that need to be updated will play a role in the time it takes
to make the disk pool available.</p>
<p>As the independent disk pool is made available, several server jobs are
started to support the independent disk pool. In order for server jobs to
remain unique on the server, those that service the independent disk pool
are given their own simple job name when the disk pool is made available.
The server jobs are essential to the operation of the disk pool; do not tamper
with these server jobs. The following is a list of server jobs that are created
(nn = number):</p>
<ol><li><span class="uicontrol">QDBXnnnXR</span> - handles database cross-reference file
server functions</li>
<li><span class="uicontrol">QDBXnnnXR2</span> - handles database cross-reference field
(column) information</li>
<li><span class="uicontrol">QDBnnnSV01</span> - handles database, journal, and commitment
control events</li>
<li><span class="uicontrol">QDBnnnSV02 through QDBnnnSVnn</span> - high priority jobs
that service the database</li>
<li><span class="uicontrol">QDBnnnSVnn through QDBnnnSVnn</span> - low priority jobs
that service the database</li>
</ol>
<p>When the recovery process is completed, the disk pool is in an Available
state, ready for you to use. When you make a disk pool group available, you
will see a completion messages for each disk pool. If the make available process
encounters problems, such as an object not synchronized with a journal, you
will need to resolve the issues reported in the error messages. See the job
log, the system operator message queue, and the history log to locate problems
and to verify the make available process.</p>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzalysupportedunsupportedobjects.htm">Supported and unsupported object types</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalydatabases.htm">Independent disk pools with distinct databases</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalymultiplesystemlibraries.htm">Multiple system libraries</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalyobjectidentification.htm">Object identification</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalyprintingconsiderations.htm">Printing considerations</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalyswitchbetweenv5r1andv5r2.htm">Switching independent disk pool between different releases</a></strong><br />
</li>
<li class="ulchildlink"><strong><a href="rzalystartup.htm">Example: Make independent disk pool available at startup</a></strong><br />
</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalyconcepts.htm">Independent disk pools</a></div>
</div>
</div>
</body>
</html>