ECPRIV parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
Line 21: Line 21:
<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 align="right"><var>1 </var></th><td>Any <var>[[Application_Subsystem_development|APSY]]</var> user can issue privileged ECF statements.</td></tr>
<tr><th align="right"><var>2 </var></th><td>Any non-APSY user can issue privileged ECF statements.</td></tr>
<tr><th align="right"><var>2 </var></th><td>Any non-APSY user can issue privileged ECF statements.</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>
</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 16:38, 9 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
0End-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.
4Run under the job's external authorizer profile rather than the use 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 would always 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.