52 lines
3.3 KiB
HTML
52 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 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 the iSeries views storage" />
|
||
|
|
<meta name="abstract" content="This topic describes how objects are stored on your iSeries server and lays the groundwork for the other topics in this section." />
|
||
|
|
<meta name="description" content="This topic describes how objects are stored on your iSeries server and lays the groundwork for the other topics in this section." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzam4overview.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="rzam4sls" />
|
||
|
|
<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 the iSeries views
|
||
|
|
storage</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzam4sls"><a name="rzam4sls"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">How the iSeries views
|
||
|
|
storage</h1>
|
||
|
|
<div><p>This topic describes how objects are stored on your iSeries™ server
|
||
|
|
and lays the groundwork for the other topics in this section.</p>
|
||
|
|
<p>The iSeries server
|
||
|
|
has a unique way of addressing storage. It views the disk space on your server
|
||
|
|
and your server's main memory as one large storage area. This way of addressing
|
||
|
|
storage is known as<dfn class="term">single-level storage</dfn>. The following diagram
|
||
|
|
shows how single-level storage works:</p>
|
||
|
|
<br /><img src="rzam4501.gif" alt="Single-level storage" /><br /><p>When you save a file, you do not assign it to a storage location; instead,
|
||
|
|
the server places the file in the location that ensures the best performance.
|
||
|
|
It may spread the data in the file across multiple disk units, if that is
|
||
|
|
the best option. When you add more records to the file, the system assigns
|
||
|
|
additional space on one or more disk units.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4overview.htm" title="As your company produces a greater volume of information, and as the value of that information grows, the methods you use to protect and preserve it become vital corporate strategies. Storage has gone from being a feature of a server to being an entity unto itself.">Storage solutions</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|