ECPRIV parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (misc formatting)
Line 15: Line 15:


==Description==
==Description==
<p>Specifies who can issue privileged ECF statements. All EXTERNAL statements, except EXTERNAL CALL, are privileged.</p>
<p>
Specifies who can issue privileged [[External Call Facility|ECF]] statements. All <var>External</var> statements, except <var>External Call</var>, are privileged.
</p>
<table>
<table>
<tr><th>Value </th><th> Means</th></tr>
<tr class="head"><th>Value </th><th> Means</th></tr>
<tr><th align="right"><var>0</var></th><td>End-users can issue only EXTERNAL CALL statements; no other ECF statements are allowed.</td></tr>
 
<tr><th align="right"><var>1 </var></th><td>Any <var>[[Application_Subsystem_development|APSY]]</var> user can issue privileged ECF statements.</td></tr>
<tr><th><var>0</var></th>
<tr><th align="right"><var>2 </var></th><td>Any non-APSY user can issue privileged ECF statements.</td></tr>
<td>End-users can issue only <var>External Call</var> statements; no other ECF statements are allowed.</td></tr>
<tr><th align="right"><var>4</var></th><td>Run under the job's external authorizer profile rather than the use that invoked an <var>[[External Call Facility#External Call statement|EXTERNAL CALL]]</var>. This bit only has an effect under Model 204 7.7 and later. Before Model 204 7.7, <var>EXTERNAL CALL</var> requests would always run under the job's authorization profile. As of, Model 204 7.7, <var>EXTERNAL CALL</var> requests run under the invoking user's authorizer profile unless the <var>ECPRIV</var> 4 bit is set. This bit only has an effect if Model 204 is using an external authorizer such as ACF2, RACF, or Top/Secret.</td></tr>
 
<tr><th><var>1 </var></th>
<td>Any [[Application Subsystem development|APSY]] user can issue privileged ECF statements.</td></tr>
 
<tr><th><var>2 </var></th>
<td>Any non-APSY user can issue privileged ECF statements.</td></tr>
 
<tr><th><var>4</var></th>
<td>Run under the job's external authorizer profile rather than that of the user that invoked an <var>[[External Call Facility#External Call statement|External Call]]</var>.  
<p>
This bit only has an effect under Model&nbsp;204 7.7 and later. Before Model&nbsp;204 7.7, <var>External Call</var> requests run under the job's authorization profile. As of Model&nbsp;204 7.7, <var>External Call</var> requests run under the invoking user's authorizer profile, unless the <var>ECPRIV</var> 4 bit is set. </p>
<p>
This bit only has an effect if Model&nbsp;204 is using an external authorizer such as ACF2, RACF, or Top/Secret.</p></td></tr>
</table>
</table>
<p>You can select multiple options by summing the values pertaining to each desired option.</p>
<p>
You can select multiple options by summing the values pertaining to each desired option.</p>
 
[[Category:System parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Revision as of 01:25, 10 August 2016

ECF privileges

Summary

Default value
0
Parameter type
System
Where set
On User 0's parameter line
Related products
All
Introduced
Model 204 V5.1

Description

Specifies who can issue privileged ECF statements. All External statements, except External Call, are privileged.

Value Means
0 End-users can issue only External Call statements; no other ECF statements are allowed.
1 Any APSY user can issue privileged ECF statements.
2 Any non-APSY user can issue privileged ECF statements.
4 Run under the job's external authorizer profile rather than that of the user that invoked an External Call.

This bit only has an effect under Model 204 7.7 and later. Before Model 204 7.7, External Call requests run under the job's authorization profile. As of Model 204 7.7, External Call requests run under the invoking user's authorizer profile, unless the ECPRIV 4 bit is set.

This bit only has an effect if Model 204 is using an external authorizer such as ACF2, RACF, or Top/Secret.

You can select multiple options by summing the values pertaining to each desired option.