ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/addautle.htm

249 lines
11 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Add Authorization List Entry (ADDAUTLE)</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="ADDAUTLE.Top_Of_Page"></a>
<h2>Add Authorization List Entry (ADDAUTLE)</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="#ADDAUTLE.PARAMETERS.TABLE">Parameters</a><br>
<a href="#ADDAUTLE.COMMAND.EXAMPLES">Examples</a><br>
<a href="#ADDAUTLE.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="ADDAUTLE"></a>
<p>The Add Authorization List Entry (ADDAUTLE) command allows the user to add entries to an authorization list. An entry consists of a user's name and the authorities associated with that user on the authorization list. Both the authorization list and the user profile must exist. If the specified user is already on the list, a message is issued and the user's authorities on the list are not changed.
</p>
<p>The users who can use this command to add users to an authorization list are: the owner of the authorization list, a user with authorization list management (*AUTLMGT) authority on the authorization list, or a user with all object (*ALLOBJ) special authority.
</p>
<p>When the ADDAUTLE command is used to add a user to an authorization list, the user must specify the name of the authorization list, a list of authorized users, and a list of authorities specified for the list. Each user on the list is given the authorities specified on the command.
</p>
<p><b>Restrictions:</b>
</p>
<ul>
<li>Authorization list management (*AUTLMGT) authority allows a user to manage the authorization list and, therefore, to manage the authorities for all objects secured by the list.
</li>
<li>Only the owner of the list or a user with all object (*ALLOBJ) special authority can add a user with authorization list management (*AUTLMGT) authority.
</li>
<li>A user with *AUTLMGT authority can add users and give specific authorities only to the *AUTLMGT level.
</li>
</ul>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="ADDAUTLE.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="#ADDAUTLE.AUTL"><b>AUTL</b></a></td>
<td valign="top">Authorization list</td>
<td valign="top"><i>Generic name, name</i></td>
<td valign="top">Required, Positional 1</td>
</tr>
<tr>
<td valign="top"><a href="#ADDAUTLE.USER"><b>USER</b></a></td>
<td valign="top">User</td>
<td valign="top">Values (up to 50 repetitions): <i>Name</i></td>
<td valign="top">Required, Positional 2</td>
</tr>
<tr>
<td valign="top"><a href="#ADDAUTLE.AUT"><b>AUT</b></a></td>
<td valign="top">Authority</td>
<td valign="top">Single values: *EXCLUDE<br>Other values (up to 11 repetitions): <b><u>*CHANGE</u></b>, *ALL, *USE, *OBJALTER, *OBJEXIST, *OBJMGT, *OBJOPR, *OBJREF, *ADD, *DLT, *EXECUTE, *READ, *UPD, *AUTLMGT</td>
<td valign="top">Optional, Positional 3</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="ADDAUTLE.AUTL"></a>
<h3>Authorization list (AUTL)</h3>
<p>Specifies the authorization list to which the users are to be added. The authorization list must already exist.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>generic-name</i></b></dt>
<dd>Specify the generic name of the authorization lists to be changed.
<p>A generic name is a character string of one or more characters followed by an asterisk (*); for example ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name.
</p>
</dd>
</dl>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the authorization list to which the user profile name is added.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDAUTLE.USER"></a>
<h3>User (USER)</h3>
<p>Specifies one or more users to be added to the authorization list. Up to 50 user profile names can be specified. If a user profile name is already on the authorization list, a message is issued and the user's authorities are not changed.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the user profile to be added to the authorization list.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDAUTLE.AUT"></a>
<h3>Authority (AUT)</h3>
<p>Specifies the authority to be given to the users specified for the <b>User (USER)</b> parameter. Users must have *AUTLMGT authority to manage the authorization list.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*EXCLUDE</b></dt>
<dd>The user cannot access the object.
</dd>
</dl>
<p><b>Other values (up to 11 repetitions)</b>
</p>
<dl>
<dt><b><u>*CHANGE</u></b></dt>
<dd>The user can perform all operations on the object except those limited to the owner or controlled by object existence (*OBJEXIST) and object management (*OBJMGT) authorities. The user can change and perform basic functions on the object. *CHANGE authority provides object operational (*OBJOPR) authority and all data authority. If the object is an authorization list, the user cannot add, change, or remove users.
</dd>
</dl>
<dl>
<dt><b>*ALL</b></dt>
<dd>The user can perform all operations except those limited to the owner or controlled by authorization list management (*AUTLMGT) authority. The user can control the object's existence, specify the security for the object, change the object, and perform basic functions on the object. The user also can change ownership of the object.
</dd>
</dl>
<dl>
<dt><b>*USE</b></dt>
<dd>The user can perform basic operations on the object, such as running a program or reading a file. The user cannot change the object. Use (*USE) authority provides object operational (*OBJOPR), read (*READ), and execute (*EXECUTE) authorities.
</dd>
</dl>
<dl>
<dt><b>*AUTLMGT</b></dt>
<dd>Authorization list management authority provides the authority to add users to the authorization list, to change users' authorities on the authorization list, to remove user names from the authorization list, or to remove users from the authorization list, to rename an authorization list, or to create a duplicate authorization list.
</dd>
<dt><b>*OBJALTER</b></dt>
<dd>Object alter authority provides the authority needed to alter the attributes of an object. If the user has this authority on a database file, the user can add and remove triggers, add and remove referential and unique constraints, and change the attributes of the database file. If the user has this authority on an SQL package, the user can change the attributes of the SQL package. This authority is currently only used for database files and SQL packages.
</dd>
<dt><b>*OBJEXIST</b></dt>
<dd>Object existence authority provides the authority to control the object's existence and ownership. These authorities are necessary for users who want to delete an object, free storage for an object, perform save and restore operations for an object, or transfer ownership of an object. A user with special save system (*SAVSYS) authority does not need existence authority to save or restore objects. Object existence authority is required to create an object that has an existing authority holder.
</dd>
<dt><b>*OBJMGT</b></dt>
<dd>Object management authority provides the authority to The security for the object, move or rename the object, and add members to database files.
</dd>
<dt><b>*OBJOPR</b></dt>
<dd>Object operational authority provides authority to look at the description of an object and to use the object as determined by the user's data authority to the object.
</dd>
<dt><b>*OBJREF</b></dt>
<dd>Object reference authority provides the authority needed to reference an object from another object such that operations on that object may be restricted by the other object. If the user has this authority on a physical file, the user can add referential constraints in which the physical file is the parent. This authority is currently only used for database files.
</dd>
</dl>
<p><b>Data authorities</b>
</p>
<dl>
<dt><b>*ADD</b></dt>
<dd>Add authority provides the authority to add entries to an object (for example, job entries to an queue or records to a file).
</dd>
</dl>
<dl>
<dt><b>*DLT</b></dt>
<dd>Delete authority allows the user to remove entries from an object (for example, remove messages from a message queue or records from a file.)
</dd>
<dt><b>*EXECUTE</b></dt>
<dd>Execute authority provides the authority needed to run a program or locate an object in a library or directory.
</dd>
<dt><b>*READ</b></dt>
<dd>Read authority provides the authority needed to show the contents of an object.
</dd>
<dt><b>*UPD</b></dt>
<dd>Update authority provides the authority to change the entries in an object.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDAUTLE.COMMAND.EXAMPLES">Examples</a> </h3>
<p>
<pre>
ADDAUTLE AUTL(PAYROLL) USER(TOM) AUT(*ALL *AUTLMGT)
</pre>
</p>
<p>This command adds user TOM to the PAYROLL authorization list and gives him all authority to the objects secured by the authorization list. TOM also has authority to manage the authorization list.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDAUTLE.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF22AA</b></dt>
<dd>Only *AUTLMGT authority can be specified with *ALL authority.
</dd>
<dt><b>CPF22AB</b></dt>
<dd>Only *AUTLMGT can be specified with *CHANGE authority.
</dd>
<dt><b>CPF22AC</b></dt>
<dd>Only *AUTLMGT authority can be specified with *USE authority.
</dd>
<dt><b>CPF2253</b></dt>
<dd>No objects found for &amp;1 in library &amp;2.
</dd>
<dt><b>CPF2280</b></dt>
<dd>*PUBLIC is always on authorization list, cannot be added.
</dd>
<dt><b>CPF2281</b></dt>
<dd>The users specified do not exist on the system.
</dd>
<dt><b>CPF2282</b></dt>
<dd>&amp;1 errors adding users, &amp;2 authorization lists processed.
</dd>
<dt><b>CPF2283</b></dt>
<dd>Authorization list &amp;1 does not exist.
</dd>
<dt><b>CPF2284</b></dt>
<dd>Not authorized to change authorization list &amp;1.
</dd>
<dt><b>CPF2289</b></dt>
<dd>Unable to allocate authorization list &amp;1.
</dd>
<dt><b>CPF2290</b></dt>
<dd>*EXCLUDE cannot be specified with another authority.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDAUTLE.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>