ECPRIV parameter - Revision history

JAL: minor formatting

2017-06-27T18:01:17Z

minor formatting

← Older revision		Revision as of 18:01, 27 June 2017
Line 34:		Line 34:
	<p>		<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>		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>		<p class="note">
	Note ~~that 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.		<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>
	<p>		<p>

Alex: /* Description */

2017-06-27T06:10:32Z

Description

← Older revision		Revision as of 06:10, 27 June 2017
Line 31:		Line 31:

	<tr><th><var>4</var></th>		<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>.		<td>Run under the job's external-authorizer profile rather than that of the user that invoked an <var>External Call</var>.
	<p>		<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>		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>
			Note that 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>		<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>		This bit only has an effect if Model 204 is using an external authorizer such as ACF2, RACF, or Top/Secret.</p></td></tr>

ELowell: /* Description */

2016-09-28T22:01:33Z

Description

← Older revision		Revision as of 22:01, 28 September 2016
Line 33:		Line 33:
	<td>Run under the job's external-authorizer profile rather than that of the user that invoked an <var>External Call</var>.		<td>Run under the job's external-authorizer profile rather than that of the user that invoked an <var>External Call</var>.
	<p>		<p>
	~~Before~~ Model 204 7.7, this bit ~~did~~ 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>		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>		<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>		This bit only has an effect if Model 204 is using an external authorizer such as ACF2, RACF, or Top/Secret.</p></td></tr>

JAL: wordsmithing

2016-09-02T21:36:20Z

wordsmithing

← Older revision		Revision as of 21:36, 2 September 2016
Line 22:		Line 22:

	<tr><th><var>0</var></th>		<tr><th><var>0</var></th>
	<td>End-users can issue only <var>External Call</var> statements; no other ECF statements are allowed.</td></tr>		<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>		<tr><th><var>1 </var></th>
Line 31:		Line 31:

	<tr><th><var>4</var></th>		<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>.		<td>Run under the job's external-authorizer profile rather than that of the user that invoked an <var>External Call</var>.
	<p>		<p>
	~~This bit only has an effect under Model 204 7.7 and later.~~ Before Model 204 7.7, <var>External Call</var> requests 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~~. </p>		Before Model 204 7.7, this bit did 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>		<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>		This bit only has an effect if Model 204 is using an external authorizer such as ACF2, RACF, or Top/Secret.</p></td></tr>

JAL: misc formatting

2016-08-10T01:25:39Z

misc formatting

← Older revision		Revision as of 01:25, 10 August 2016
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 204 7.7 and later. Before Model 204 7.7, <var>External Call</var> requests 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. </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]]

Alex: /* Description */

2016-08-09T16:38:13Z

Description

← Older revision		Revision as of 16:38, 9 August 2016
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]]

DCameron: /* Description */

2014-10-16T15:52:03Z

Description

← Older revision		Revision as of 15:52, 16 October 2014
Line 19:		Line 19:
	<tr><th>Value </th><th> Means</th></tr>		<tr><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>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 APSY 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>
	</table>		</table>

DCameron: /* Summary */

2014-10-16T15:49:53Z

Summary

← Older revision		Revision as of 15:49, 16 October 2014
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> ~~or earlier~~		<dd><var class="product">Model 204 V5.1</var>
	</dl>		</dl>

	==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 ECF statements. All EXTERNAL statements, except EXTERNAL CALL, are privileged.</p>

DmeWiccan: Automatically generated page update

2013-08-27T16:26:24Z

Automatically generated page update

← Older revision		Revision as of 16:26, 27 August 2013
Line 1:		Line 1:
			{{Template:ECPRIV parameter subtitle}}
	==Summary==		==Summary==
	<dl>		<dl>

DmeWiccan: Automatically generated page update

2013-04-23T01:50:56Z

Automatically generated page update

← Older revision		Revision as of 01:50, 23 April 2013
Line 21:		Line 21:
	</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]]