SECURE PROCEDURE NAME command - Revision history

JAL: minor formatting

2017-09-28T20:24:37Z

minor formatting

← Older revision		Revision as of 20:24, 28 September 2017
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>

	~~<b>~~Where:~~</b>~~		Where:
	<table>		<table>
	<tr>		<tr>
	<th>procname</th>		<th>procname</th>
	<td> ~~is the~~ name of an existing procedure to be secured.</td>		<td>The name of an existing procedure to be secured.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>pclass</th>		<th>pclass</th>
	<td> ~~is the~~ number of the procedure class to be assigned to the procedure(s). The number must be in the range 1 to 255.</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~~\|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures~~]]. 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>
	<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 ~~User Language~~ 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, SECURE PROCEDURE NAME is included in that update unit. See [[~~File_integrity_and_recovery~~#~~Update_units_and_transactions~~\|update units]] for more information.</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>
			<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]]

ELowell: /* Syntax */

2017-04-12T20:17:09Z

Syntax

← Older revision		Revision as of 20:17, 12 April 2017
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax">SECURE [<b>~~PRO~~</b>~~CEDURE~~] NAME=<i>procname</i>		<p class="syntax">SECURE [<b>PROC</b>EDURE] NAME=<i>procname</i>
	[<i>,procname</i>]... PCLASS=<i>pclass</i>		[<i>,procname</i>]... PCLASS=<i>pclass</i>
	</p>		</p>
Line 27:		Line 27:
	<p>Commas are required.</p>		<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>		<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==
	<p class="code">SECURE PROCEDURE NAME = PAY PCLASS = 7		<p class="code">SECURE PROCEDURE NAME = PAY PCLASS = 7

ELowell at 22:40, 11 December 2013

2013-12-11T22:40:49Z

← Older revision		Revision as of 22:40, 11 December 2013
Line 34:		Line 34:
	<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\|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures]]. 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>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\|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures]]. 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>If any of the procedures specified in the command are currently secured, their old procedure classes are changed to the new one. </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>
	<p>When it processes SECURE PROCEDURE NAME, <var class="product">Model 204</var> ends any current User Language 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, SECURE PROCEDURE NAME is included in that update unit. See [[~~File_Integrity_and_Recovery~~#Update_units_and_transactions\|update units]] for more information.</p>		<p>When it processes SECURE PROCEDURE NAME, <var class="product">Model 204</var> ends any current User Language 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, SECURE PROCEDURE NAME 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]]

ELowell: /* Usage notes */

2013-10-22T18:18:31Z

Usage notes

← Older revision		Revision as of 18:18, 22 October 2013
Line 34:		Line 34:
	<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\|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures]]. 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>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\|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures]]. 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>If any of the procedures specified in the command are currently secured, their old procedure classes are changed to the new one. </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>
	<p>When it processes SECURE PROCEDURE NAME, <var class="product">Model 204</var> ends any current User Language 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, SECURE PROCEDURE NAME is included in that update unit. ~~For~~ more information ~~about <var class="product">Model 204</var> update units, see the <var class="product">Model 204</var> File Manager's Guide~~.</p>		<p>When it processes SECURE PROCEDURE NAME, <var class="product">Model 204</var> ends any current User Language 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, SECURE PROCEDURE NAME 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]]

Alex: Automatically generated page update

2013-02-28T01:05:25Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>File manager
<dt>Function
<dd>Secures a procedure
</dl>
==Syntax==
SECURE [PROCEDURE] NAME=procname
[,procname]... PCLASS=pclass


Where:
<table>
<tr>
<th>procname</th>
<td> is the name of an existing procedure to be secured.</td>
</tr>

<tr>
<th>pclass</th>
<td> is 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>

</table>
===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|SECURE PROCEDURE ACCESS: Defining user privileges for secured procedures]]. 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, <var class="product">Model 204</var> ends any current User Language 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, SECURE PROCEDURE NAME is included in that update unit. For more information about <var class="product">Model 204</var> update units, see the <var class="product">Model 204</var> File Manager's Guide.
[[Category: File manager commands]]
[[Category:Commands]]