173 lines
6.4 KiB
HTML
173 lines
6.4 KiB
HTML
|
|
||
|
|
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<title>Release File System Locks (RLSIFSLCK)</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
|
||
|
|
</head>
|
||
|
|
<body bgcolor="white">
|
||
|
|
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<a name="RLSIFSLCK.Top_Of_Page"></a>
|
||
|
|
<h2>Release File System Locks (RLSIFSLCK)</h2>
|
||
|
|
<table width="100%">
|
||
|
|
<tr>
|
||
|
|
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
|
||
|
|
<b>Threadsafe: </b>No
|
||
|
|
</td>
|
||
|
|
<td valign="top" align="right">
|
||
|
|
<a href="#RLSIFSLCK.PARAMETERS.TABLE">Parameters</a><br>
|
||
|
|
<a href="#RLSIFSLCK.COMMAND.EXAMPLES">Examples</a><br>
|
||
|
|
<a href="#RLSIFSLCK.ERROR.MESSAGES">Error messages</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<div> <a name="RLSIFSLCK"></a>
|
||
|
|
<p>The Release File System Locks (RLSIFSLCK) command can be used to release all Network File System (NFS) byte-range locks held by a specified NFS client, or to release all byte-range locks (of any type) held on a specified object. This command should only be used to free resources that cannot be freed using normal means.
|
||
|
|
</p>
|
||
|
|
<p>For more information about byte range locks, see the <i>fcntl</i> API in System API Reference information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter or Network File System book, SC41-5714
|
||
|
|
</p>
|
||
|
|
<p><b>Restrictions:</b>
|
||
|
|
</p>
|
||
|
|
<ol>
|
||
|
|
<li>The user must have input/output (I/O) system configuration (*IOSYSCFG) special authority to use this command.
|
||
|
|
</li>
|
||
|
|
<li>The user must have execute (*X) authority to the directories in the path name prefixes.
|
||
|
|
</li>
|
||
|
|
<li>The user must have read (*R) authority to the object whose locks are being released.
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
<hr size="2" width="100%">
|
||
|
|
|
||
|
|
<div>
|
||
|
|
<h3><a name="RLSIFSLCK.PARAMETERS.TABLE">Parameters</a></h3>
|
||
|
|
<table border="1" cellpadding="4" cellspacing="0">
|
||
|
|
<!-- col1="10" col2="15" col3="30" col4="10" -->
|
||
|
|
<tr>
|
||
|
|
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
|
||
|
|
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
|
||
|
|
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
|
||
|
|
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><a href="#RLSIFSLCK.RMTLOCNAME"><b>RMTLOCNAME</b></a></td>
|
||
|
|
<td valign="top">Remote location</td>
|
||
|
|
<td valign="top"><i>Character value</i></td>
|
||
|
|
<td valign="top">Optional, Positional 1</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td valign="top"><a href="#RLSIFSLCK.OBJ"><b>OBJ</b></a></td>
|
||
|
|
<td valign="top">Object</td>
|
||
|
|
<td valign="top"><i>Path name</i></td>
|
||
|
|
<td valign="top">Optional, Positional 2</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<div> <a name="RLSIFSLCK.RMTLOCNAME"></a>
|
||
|
|
<h3>Remote location (RMTLOCNAME)</h3>
|
||
|
|
<p>Specifies the host name or internet address of a remote system whose NFS-related locks on local files are to be released.
|
||
|
|
</p>
|
||
|
|
<p>To be successful, the remote system name must be valid. The user can assign host names to an internet address with the Work with TCP/IP host table entries option on the Configure TCP/IP menu (CFGTCP) command. Also, a remote name server can be used to map remote system names to internet addresses. Use the Change remote name server option on the CFGTCP menu to specify a remote name server.
|
||
|
|
</p>
|
||
|
|
<p>Host names must follow these conventions:
|
||
|
|
</p>
|
||
|
|
<ul>
|
||
|
|
<li>The first character must be either A through Z or 0 through 9.
|
||
|
|
</li>
|
||
|
|
<li>The last character must be either A through Z or 0 through 9.
|
||
|
|
</li>
|
||
|
|
<li>Uppercase and lowercase characters are allowed, but no significance is attached to the case.
|
||
|
|
</li>
|
||
|
|
<li>Blanks ( ) are not allowed.
|
||
|
|
</li>
|
||
|
|
<li>The special characters, period (.) and minus (-), are allowed.
|
||
|
|
</li>
|
||
|
|
<li>Parts of the name separated by periods (.) cannot exceed 63 characters in length.
|
||
|
|
</li>
|
||
|
|
<li>Names must be from 1 to 255 characters in length.
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<dl>
|
||
|
|
<dt><b><i>'remote-location-name'</i></b></dt>
|
||
|
|
<dd>Specifies the host name or internet address of a remote system whose NFS-related locks on local files are to be released.
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<p>Either the RMTLOCNAME or <b>Object (OBJ)</b> parameter must be specified, but not both.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
<div> <a name="RLSIFSLCK.OBJ"></a>
|
||
|
|
<h3>Object (OBJ)</h3>
|
||
|
|
<p>Specifies the path name of an object on which all byte-range locks are to be released. This will release all locks on that object, regardless of the type of lock or the type of process that is holding them.
|
||
|
|
</p>
|
||
|
|
<dl>
|
||
|
|
<dt><b><i>'path-name'</i></b></dt>
|
||
|
|
<dd>Specifies the path name of the local object for which all locks are to be released.
|
||
|
|
<p>For more information on specifying path names, refer to "Object naming rules" in the CL concepts and reference topic in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter.
|
||
|
|
</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
<p>Either the <b>Remote location (RMTLOCNAME)</b> or OBJ parameter must be specified, but not both.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
<hr size="2" width="100%">
|
||
|
|
<div><h3><a name="RLSIFSLCK.COMMAND.EXAMPLES">Examples</a> </h3>
|
||
|
|
<p><b>Example 1: Releasing Locks for a Remote System</b>
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
<pre>
|
||
|
|
RLSIFSLCK RMTLOCNAME('rainbow1')
|
||
|
|
</pre>
|
||
|
|
</p>
|
||
|
|
<p>This command releases the NFS-related locks held on local files by the system named <i>rainbow1</i>.
|
||
|
|
</p>
|
||
|
|
<p><b>Example 2: Releasing Locks for a Local Object</b>
|
||
|
|
</p>
|
||
|
|
<p>
|
||
|
|
<pre>
|
||
|
|
RLSIFSLCK OBJ('/CustAccounts/May')
|
||
|
|
</pre>
|
||
|
|
</p>
|
||
|
|
<p>This command releases all byte-range locks held on the object <i>/CustAccounts/May</i>.
|
||
|
|
</p>
|
||
|
|
</div>
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
<hr size="2" width="100%">
|
||
|
|
<div><h3><a name="RLSIFSLCK.ERROR.MESSAGES">Error messages</a> </h3>
|
||
|
|
<p><b><u>*ESCAPE Messages</u></b>
|
||
|
|
</p>
|
||
|
|
<dl>
|
||
|
|
<dt><b>CPFA09C</b></dt>
|
||
|
|
<dd>Not authorized to object. Object is &1.
|
||
|
|
</dd>
|
||
|
|
<dt><b>CPFA0A9</b></dt>
|
||
|
|
<dd>Object not found. Object is &1.
|
||
|
|
</dd>
|
||
|
|
<dt><b>CPFA0B6</b></dt>
|
||
|
|
<dd>TOOBJ parameter is not allowed with a pattern in OBJ for CPY.
|
||
|
|
</dd>
|
||
|
|
<dt><b>CPFA1B8</b></dt>
|
||
|
|
<dd>*IOSYSCFG authority required to use &1.
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<table width="100%">
|
||
|
|
<tr><td align="right"><a href="#RLSIFSLCK.Top_Of_Page">Top</a></td></tr>
|
||
|
|
</table>
|
||
|
|
</body>
|
||
|
|
</html>
|