63 lines
5.5 KiB
HTML
63 lines
5.5 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="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
|
<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="File types" />
|
||
|
|
<meta name="DC.subject" content="DDM files, distributed file, definition, database file, device file" />
|
||
|
|
<meta name="keywords" content="DDM files, distributed file, definition, database file, device file" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3overview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3copyfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3open.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3secpub.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3share.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbal3applyovr.htm" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbal3ft" />
|
||
|
|
<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>File types</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbal3ft"><a name="rbal3ft"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">File types</h1>
|
||
|
|
<div><div class="p">The file management functions support the following types of files: <ul><li><span class="uicontrol">Database files</span> are files (including distributed files) whose associated data is stored permanently in the system.</li>
|
||
|
|
<li><span class="uicontrol">Device files</span> are files that provide access to externally attached devices such as displays, printers, tapes, diskettes, and other systems that are attached by a communications line. The device files supported are: <ul><li>Display files, which provide access to display devices</li>
|
||
|
|
<li>Printer files, which describe the format of printed output</li>
|
||
|
|
<li>Tape files, which allow access to data files on tape devices</li>
|
||
|
|
<li>Diskette files, which provide access to data files on diskette devices</li>
|
||
|
|
<li><span class="uicontrol">Intersystem communications function</span> (<span class="keyword">OS/400<sup>®</sup></span>-ICF) files, hereafter referred to as ICF files, which allow a program on one server to communicate with a program on the same server or another server</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li><span class="uicontrol">Save files</span> are files that are used to store saved data on disk (without requiring diskettes or tapes).</li>
|
||
|
|
<li><span class="uicontrol">Distributed data management (DDM) files</span> are files that allow access to data files stored on remote servers.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>Each file type has its own set of unique characteristics that determines how the file can be used and what capabilities it can provide. The concept of a file, however, is the same regardless of what type of file it is. When a file is used by a program, it is referred to by name, which identifies both the file description and, for some file types, the data itself. This information is designed to help you understand the common characteristics of all file types so you can use the files to their full capabilities.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbal3overview.htm" title="File management provides the functions that an application uses in creating and accessing data on the server and ensures the integrity of the data according to the definitions of the application.">Overview of database file management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbal3copyfile.htm" title="The copy function on iSeries can copy physical and logical files, copy members and records, copy complex objects, and copy files between servers.">Copy files</a></div>
|
||
|
|
<div><a href="rbal3open.htm" title="When you want an application to use a file, you do so by referring to that file by name. The file description for that file will then control how the program and the server will interact.">Open files</a></div>
|
||
|
|
<div><a href="rbal3secpub.htm" title="Specifying authorities allows you to control access to a file. You use the AUT parameter on the create command to specify public authority when you create a file">Limit access to files and data when creating files</a></div>
|
||
|
|
<div><a href="rbal3share.htm" title="File management on iSeries provides several levels of support for shared files. Files can be shared among many users, many jobs, or many programs within the same job.">Share files</a></div>
|
||
|
|
<div><a href="rbal3applyovr.htm" title="You can perform two general types of overrides, which are file overrides and overrides for program device entries.">Apply overrides</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|