SECURE PROCEDURE NAME command: Difference between revisions
(→Syntax) |
m (minor formatting) |
||
| Line 6: | Line 6: | ||
<dd>Secures a procedure | <dd>Secures a procedure | ||
</dl> | </dl> | ||
==Syntax== | ==Syntax== | ||
<p class="syntax">SECURE [<b>PROC</b>EDURE] NAME=<i>procname</i> | <p class="syntax">SECURE [<b>PROC</b>EDURE] NAME=<i>procname</i> | ||
| Line 11: | Line 12: | ||
</p> | </p> | ||
Where: | |||
<table> | <table> | ||
<tr> | <tr> | ||
<th>procname</th> | <th>procname</th> | ||
<td> | <td>The name of an existing procedure to be secured.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<th>pclass</th> | <th>pclass</th> | ||
<td> | <td>The number of the procedure class to be assigned to the procedure(s). The number must be in the range 1 to 255.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
===Syntax notes=== | ===Syntax notes=== | ||
<p>Commas are required.</p> | <p> | ||
<p>When this command is issued, the password table should be updated by the system manager using LOGCTL with a password that has UCLASS associated with it.</p> | Commas are required.</p> | ||
<p> | |||
When this command is issued, the password table should be updated by the system manager using LOGCTL with a password that has UCLASS associated with it.</p> | |||
==Example== | ==Example== | ||
| Line 32: | Line 35: | ||
SECURE NAME = EMPLOY, PERSNEL PCLASS = 8 | SECURE NAME = EMPLOY, PERSNEL PCLASS = 8 | ||
</p> | </p> | ||
==Usage notes== | ==Usage notes== | ||
<p>The SECURE PROCEDURE command secures a procedure by assigning a class to it. Access to a secured procedure is limited to users whose user classes authorize them to access the procedure class specified for the procedure. The way in which user classes are mapped to procedure classes is discussed in [[SECURE PROCEDURE ACCESS command | <p> | ||
<p>If any of the procedures specified in the command are currently secured, their old procedure classes are changed to the new one. </p> | The <var>SECURE PROCEDURE</var> command secures a procedure by assigning a class to it. Access to a secured procedure is limited to users whose user classes authorize them to access the procedure class specified for the procedure. The way in which user classes are mapped to procedure classes is discussed in [[SECURE PROCEDURE ACCESS command]]. This mapping can be used to restrict access to procedures that perform sensitive operations such as updating personnel records or displaying salary data.</p> | ||
<p>When it processes SECURE PROCEDURE NAME, <var class="product">Model 204</var> ends any current | <p> | ||
If any of the procedures specified in the command are currently secured, their old procedure classes are changed to the new one. </p> | |||
<p> | |||
When it processes <var>SECURE PROCEDURE NAME</var>, <var class="product">Model 204</var> ends any current SOUL update unit and begins a non-backoutable update unit. If a <var class="product">Model 204</var> command non-backoutable update unit is in progress, <var>SECURE PROCEDURE NAME</var> is included in that update unit. See [[File integrity and recovery#Update units and transactions|update units]] for more information.</p> | |||
[[Category: File manager commands]] | [[Category: File manager commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 20:24, 28 September 2017
Summary
- Privileges
- File manager
- Function
- Secures a procedure
Syntax
SECURE [PROCEDURE] NAME=procname [,procname]... PCLASS=pclass
Where:
| procname | The name of an existing procedure to be secured. |
|---|---|
| pclass | The number of the procedure class to be assigned to the procedure(s). The number must be in the range 1 to 255. |
Syntax notes
Commas are required.
When this command is issued, the password table should be updated by the system manager using LOGCTL with a password that has UCLASS associated with it.
Example
SECURE PROCEDURE NAME = PAY PCLASS = 7 SECURE NAME = EMPLOY, PERSNEL PCLASS = 8
Usage notes
The SECURE PROCEDURE command secures a procedure by assigning a class to it. Access to a secured procedure is limited to users whose user classes authorize them to access the procedure class specified for the procedure. The way in which user classes are mapped to procedure classes is discussed in SECURE PROCEDURE ACCESS command. This mapping can be used to restrict access to procedures that perform sensitive operations such as updating personnel records or displaying salary data.
If any of the procedures specified in the command are currently secured, their old procedure classes are changed to the new one.
When it processes SECURE PROCEDURE NAME, Model 204 ends any current SOUL update unit and begins a non-backoutable update unit. If a Model 204 command non-backoutable update unit is in progress, SECURE PROCEDURE NAME is included in that update unit. See update units for more information.