81 lines
5.3 KiB
HTML
81 lines
5.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="reference" />
|
|
<meta name="DC.Title" content="Large file support" />
|
|
<meta name="abstract" content="The integrated file system APIs are enhanced to allow your applications to store and manipulate very large files. The integrated file system allows stream file sizes up to approximately 1 TB (1 TB equals approximately 1 099 511 627 776 bytes) in the root (/), QOpenSys, and user-defined file systems." />
|
|
<meta name="description" content="The integrated file system APIs are enhanced to allow your applications to store and manipulate very large files. The integrated file system allows stream file sizes up to approximately 1 TB (1 TB equals approximately 1 099 511 627 776 bytes) in the root (/), QOpenSys, and user-defined file systems." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxprogapi.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/unix2.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/stat64.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/stat.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaaxlargefile" />
|
|
<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>Large file support</title>
|
|
</head>
|
|
<body id="rzaaxlargefile"><a name="rzaaxlargefile"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Large file support</h1>
|
|
<div><p><span>The integrated file system APIs are enhanced
|
|
to allow your applications to store and manipulate very large files. The integrated
|
|
file system allows stream file sizes up to approximately 1 TB (1 TB equals
|
|
approximately 1 099 511 627 776 bytes) in the <span class="q">"root"</span> (/), QOpenSys, and
|
|
user-defined file systems.</span></p>
|
|
<div class="section"><p>The integrated file system provides a set of 64-bit UNIX-type
|
|
APIs and allows an easy mapping of existing 32-bit APIs to 64-bit APIs that
|
|
are capable of accessing large file sizes and offsets by using eight byte
|
|
integer arguments.</p>
|
|
</div>
|
|
<div class="section"><p>The following situations are provided to allow applications
|
|
to use large file support:</p>
|
|
</div>
|
|
<div class="section"> <ul><li>If the macro label <samp class="codeph">_LARGE_FILE_API</samp> is defined at compile
|
|
time, applications have access to APIs and data structures that are 64-bit
|
|
enabled. For example, an application intending to use <span class="apiname">stat64()</span> API
|
|
and <samp class="codeph">stat64</samp> structure will need to define <samp class="codeph">_LARGE_FILE_API</samp> at
|
|
compile time.</li>
|
|
<li>If the macro label <samp class="codeph">_LARGE_FILES</samp> is defined by the applications
|
|
at compile time, existing APIs and data structures are mapped to their 64-bit
|
|
versions. For example, if an application defines <samp class="codeph">_LARGE_FILES</samp> at
|
|
compile time, a call to <span class="apiname">stat()</span> API is mapped to <span class="apiname">stat64()</span> API
|
|
and <span class="apiname">stat()</span>structure is mapped to <span class="apiname">stat64()</span> structure.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section"><p>The applications that intend to use the large file support can
|
|
either define <samp class="codeph">_LARGE_FILE_API</samp> at compile time and code directly
|
|
to the 64-bit APIs, or they can define <samp class="codeph">_LARGE_FILES</samp> at compile
|
|
time. All the appropriate APIs and data structures are then mapped to the
|
|
64-bit version automatically.</p>
|
|
</div>
|
|
<div class="section"><p>Applications that do not intend to use the large file support
|
|
are not impacted and can continue to use integrated file system APIs without
|
|
any changes.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxprogapi.htm" title="Many of the application program interfaces (APIs) that perform operations on integrated file system objects are in the form of C language functions.">Perform operations using APIs</a></div>
|
|
</div>
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
|
<div><a href="../apis/unix2.htm">Integrated file system APIs</a></div>
|
|
<div><a href="../apis/stat64.htm">stat64()</a></div>
|
|
<div><a href="../apis/stat.htm">stat()</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |