<?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="Provided directories" /> <meta name="abstract" content="The integrated file system creates these directories when the system is restarted if they do not already exist." /> <meta name="description" content="The integrated file system creates these directories when the system is restarted if they do not already exist." /> <meta name="DC.subject" content="directory, integrated file system" /> <meta name="keywords" content="directory, integrated file system" /> <meta name="DC.Relation" scheme="URI" content="rzaaxdir.htm" /> <meta name="DC.Relation" scheme="URI" content="rzaaxhomedir.htm" /> <meta name="DC.Relation" scheme="URI" content="rzaaxudptcp.htm" /> <meta name="DC.Relation" scheme="URI" content="rzaaxopenfs.htm" /> <meta name="DC.Relation" scheme="URI" content="../cl/wrklnk.htm" /> <meta name="DC.Relation" scheme="URI" content="ifsrecovpo.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="rzaaxtmpdir" /> <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>Provided directories</title> </head> <body id="rzaaxtmpdir"><a name="rzaaxtmpdir"><!-- --></a> <!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script> <h1 class="topictitle1">Provided directories</h1> <div><p>The integrated file system creates these directories when the system is restarted if they do not already exist.</p> <div class="note"><span class="notetitle">Note:</span> Do not replace the following system-created directories with symbolic links to other objects. For example, do not replace /home with a symbolic link to a directory on an independent ASP. Otherwise, there might be problems on the independent ASP as well as problems when creating new user profiles.</div> <dl><dt class="dlterm">/tmp</dt> <dd>The <samp class="codeph">/tmp</samp> directory gives applications a place to store temporary objects. This directory is a subdirectory of the <span class="q">"root"</span> (/) directory, so its path name is <samp class="codeph">/tmp</samp>. <p>Once an application puts an object in the <samp class="codeph">/tmp</samp> directory, the object stays there until you or the application removes it. The system does not automatically remove objects from the <samp class="codeph">/tmp</samp> directory or perform any other special processing for objects in the <samp class="codeph">/tmp</samp> directory.</p> <p>You can use the user displays and commands that support the integrated file system to manage the <samp class="codeph">/tmp</samp> directory and its objects. For example, you can use the Work with Object Links display or the WRKLNK command to copy, remove, or rename the <samp class="codeph">/tmp</samp> directory or objects in the directory. All users are given *ALL authority to the directory, which means that they can perform most valid actions on the directory.</p> <p>An application can use the application program interfaces (API) that support the integrated file system to manage the <samp class="codeph">/tmp</samp> directory and its objects. For example, the application program can remove an object in the <samp class="codeph">/tmp</samp> directory by using the <span class="apiname">unlink()</span> API.</p> <p>If the <samp class="codeph">/tmp</samp> directory is removed, it is automatically created again during the next restart of the system.</p> <p>The <samp class="codeph">/tmp</samp> directory can have the <tt>restricted rename and unlink</tt> attribute set to Yes for operating system commonality and security purposes.</p> <div class="note"><span class="notetitle">Note:</span> The <tt>restricted rename and unlink</tt> attribute is equivalent to the S_ISVTX mode bit for a directory.</div> <p>If the <tt>restricted rename and unlink</tt> attribute is set to Yes, you cannot rename or unlink objects within the <samp class="codeph">/tmp</samp> directory unless one of the following conditions is true:</p> <ul><li>You are the owner of the object.</li> <li>You are the owner of the directory.</li> <li>You have all object (*ALLOBJ) special authority.</li> </ul> <p>If the attribute is set to Yes, and you do not have the appropriate authorities, you will see error number 3027 (EPERM) or message MSGCPFA0B1 (<tt class="msgph">Requested operation not allowed. Access problem</tt>) for rename or unlink failures when using the following commands and APIs:</p> <ul><li><span class="cmdname">Remove Link (RMVLNK, DEL, and ERASE)</span> command</li> <li><span class="cmdname">Remove Directory (RMVDIR, RD, and RMDIR)</span> command</li> <li><span class="cmdname">Rename Object (RNM and REN)</span> command</li> <li><span class="cmdname">Move Object (MOV and MOVE)</span> command</li> <li><span class="apiname">Rename File or Directory (rename())</span> API</li> <li><img src="./delta.gif" alt="Start of change" />Rename File or Directory, Keep "new" If It Exists (Qp0lRenameKeep()) API<img src="./deltaend.gif" alt="End of change" /></li> <li><img src="./delta.gif" alt="Start of change" />Rename File or Directory, Unlink "new" If It Exists (Qp0lRenameUnlink()) API<img src="./deltaend.gif" alt="End of change" /></li> <li><span class="apiname">Remove Directory (rmdir())</span> API</li> <li><span class="apiname">Remove Link to File (unlink())</span> API</li> </ul> <p>The <tt>restricted rename and unlink</tt> attribute and S_ISVTX mode bit can be modified using the <span class="cmdname">Change Attribute (CHGATR)</span> command or the <span class="apiname">Set Attributes (Qp0lSetAttr())</span> or <span class="apiname">Change File Authorizations (chmod)</span> APIs if you are the owner of the object, or if you have all object (*ALLOBJ) special authority. But, if the attribute is changed to No, you will lose the operating system commonality and security benefits that the Yes setting provides.</p> <p><img src="./delta.gif" alt="Start of change" />When the <samp class="codeph">/tmp</samp> directory is created during a restart of the system, the attribute is set to Yes. If the <samp class="codeph">/tmp</samp> directory already exists during a restart of the system, the attribute is not changed.<img src="./deltaend.gif" alt="End of change" /></p> </dd> <dt class="dlterm">/home</dt> <dd>System administrators use the <samp class="codeph">/home</samp> directory to store a separate directory for every user. The system administrator often sets the home directory that is associated with the user profile to be the user's directory in <samp class="codeph">/home</samp>, for example<samp class="codeph">/home/john</samp>. </dd> <dt class="dlterm">/etc</dt> <dd>The <samp class="codeph">/etc</samp> directory stores administrative, configuration, and other system files.</dd> <dt class="dlterm">/usr</dt> <dd>The <samp class="codeph">/usr</samp> directory includes subdirectories that contain information that is used by the system. Files in <samp class="codeph">/usr</samp> typically do not change often.</dd> <dt class="dlterm">/usr/bin</dt> <dd>The <samp class="codeph">/usr/bin</samp> directory contains the standard utility programs.</dd> <dt class="dlterm">/QIBM</dt> <dd>The <samp class="codeph">/QIBM</samp> directory is the system directory and is provided with the system.</dd> <dt class="dlterm">/QIBM/ProdData</dt> <dd>The <samp class="codeph">/QIBM/ProdData</samp> directory is a system directory used for Licensed program data.</dd> <dt class="dlterm">/QIBM/UserData</dt> <dd>The <samp class="codeph">/QIBM/UserData</samp> directory is a system directory used for Licensed Program user data such as configuration files.</dd> <dt class="dlterm">/QOpenSys/QIBM</dt> <dd>The <samp class="codeph">/QOpenSys/QIBM</samp> directory is the system directory for the QOpenSys file system.</dd> <dt class="dlterm">/QOpenSys/QIBM/ProdData</dt> <dd>The <samp class="codeph">/QOpenSys/QIBM/ProdData</samp> directory is the system directory for the QOpenSys file system and is used for Licensed program data.</dd> <dt class="dlterm">/QOpenSys/QIBM/UserData</dt> <dd>The <samp class="codeph">/QOpenSys/QIBM/UserData</samp> directory is the system directory for the QOpenSys file system and is used for Licensed Program user data such as configuration files.</dd> <dt class="dlterm">/asp_name/QIBM</dt> <dd>The <samp class="codeph">/asp_name/QIBM</samp> directory is the system directory for any independent ASPs that exist on your system, where <samp class="codeph">asp_name</samp> is the name of the independent ASP.</dd> <dt class="dlterm">/asp_name/QIBM/UserData</dt> <dd>The <samp class="codeph">/asp_name/QIBM/UserData</samp> directory is a system directory used for Licensed Program user data such as configuration files for any independent ASPs that exist on your system, where <samp class="codeph">asp_name</samp> is the name of the independent ASP.</dd> <dt class="dlterm">/dev</dt> <dd>The <samp class="codeph">/dev</samp> directory contains various system files and directories.</dd> <dt class="dlterm">/dev/xti</dt> <dd>The <samp class="codeph">/dev/xti</samp> directory contains the UDP and TCP device drivers. </dd> </dl> </div> <div> <div class="familylinks"> <div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxdir.htm" title="A directory is a special object that is used to locate objects by names that you specify. Each directory contains a list of objects that are attached to it. That list can include other directories.">Directory</a></div> </div> <div class="relconcepts"><strong>Related concepts</strong><br /> <div><a href="rzaaxhomedir.htm" title="The home directory is used as the current directory when you sign on the system. The name of the home directory is specified in your user profile.">Home directory</a></div> </div> <div class="relref"><strong>Related reference</strong><br /> <div><a href="rzaaxudptcp.htm" title="The root (/) file system under the directory of /dev/xti will now hold two device drivers named udp and tcp.">UDP and TCP devices in the "root" (/) file system</a></div> <div><a href="rzaaxopenfs.htm" title="The QOpenSys file system is compatible with open system standards based on UNIX, such as POSIX and X/Open Portability Guide (XPG). Like the "root" (/) file system, this file system takes advantage of the stream file and directory support that is provided by the integrated file system.">Open systems file system (QOpenSys)</a></div> <div><a href="ifsrecovpo.htm" title="This table shows the objects provided by the integrated file system that the Reclaim Object Links (RCLLNK) command re-creates if they do not exist. These objects are normally created during the initial program load (IPL). You can also re-create some of these objects, if necessary, using the Reclaim Storage (RCLSTG) command.">Recreate integrated file system provided objects</a></div> </div> <div class="relinfo"><strong>Related information</strong><br /> <div><a href="../cl/wrklnk.htm">WRKLNK command</a></div> </div> </div> </body> </html>