ECPRIV parameter: Difference between revisions
(Automatically generated page update) |
m (minor formatting) |
||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 11: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V5.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>Specifies who can issue privileged ECF statements. All | <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 | |||
<tr><th | <tr><th><var>0</var></th> | ||
<tr><th | <td>End-users can issue only <var>[[External Call Facility#External Call statement|External Call]]</var> statements; no other ECF statements are allowed.</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</var>. | |||
<p> | |||
In Model 204 version 7.6 and earlier, this bit does not exist, and <var>External Call</var> requests only run under the job's external-authorizer profile. As of Model 204 7.7, the default changes (introducing a backward incompatibility), and <var>External Call</var> requests run under the invoking user's external-authorizer profile, unless this 4 bit is on. </p> | |||
<p class="note"> | |||
<b>Note:</b> This bit is ignored for the [[External Call Facility#idcams|IDCAMS facility]], that is, the IDCAMS facility always runs under the invoking user's profile regardless of the <var>ECPRIV</var> setting. | |||
</p> | |||
<p> | |||
This bit only has an effect if Model 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]] | ||
Latest revision as of 18:01, 27 June 2017
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.
In Model 204 version 7.6 and earlier, this bit does not exist, and External Call requests only run under the job's external-authorizer profile. As of Model 204 7.7, the default changes (introducing a backward incompatibility), and External Call requests run under the invoking user's external-authorizer profile, unless this 4 bit is on. Note: This bit is ignored for the IDCAMS facility, that is, the IDCAMS facility always runs under the invoking user's profile regardless of the ECPRIV setting. 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.