RunSubsystemErrorProcedure (System property) - Revision history

ELowell at 19:40, 3 September 2015

2015-09-03T19:40:47Z

← Older revision		Revision as of 19:40, 3 September 2015
Line 1:		Line 1:
	{{Template:System:RunSubsystemErrorProcedure subtitle}}		{{Template:System:RunSubsystemErrorProcedure subtitle}}

	This property allows a [[FACTDEB parameter\|FACTDEB procedure]] to determine if the subsystem error procedure is about to be run and possibly also prevent that procedure from being run.		This property allows a [[FACTDEB parameter\|FACTDEB procedure]] to determine if the subsystem error procedure is about to be run and possibly also prevent that procedure from being run.
	==Syntax==		==Syntax==

JALWiccan: Automatically generated page update

2014-02-16T00:26:58Z

Automatically generated page update

← Older revision		Revision as of 00:26, 16 February 2014
Line 8:		Line 8:
	<tr><th>%boolean</th><td><var>Boolean</var> value that indicates whether running the subsystem error procedure or whether running the [[FACTDEB parameter\|FACTDEB procedure]] before running the subsystem error procedure.</td></tr>		<tr><th>%boolean</th><td><var>Boolean</var> value that indicates whether running the subsystem error procedure or whether running the [[FACTDEB parameter\|FACTDEB procedure]] before running the subsystem error procedure.</td></tr>

	<tr><th><var>%(System)</var></th>		<tr><th><var class="nobr">%(System)</var></th>
	<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>		<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>
	</table>		</table>
Line 16:		Line 16:
	<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>		<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>
	<li>This method is most useful in a [[FACTDEB parameter\|FACTDEB procedure]]. It can be used to determine if the subsystem error procedure is about to be driven and to prevent that from happening (by setting the property to False).</li>		<li>This method is most useful in a [[FACTDEB parameter\|FACTDEB procedure]]. It can be used to determine if the subsystem error procedure is about to be driven and to prevent that from happening (by setting the property to False).</li>
	<li>The reason for this method is because APSY does not set the subsystem communications global to the error procedure's name before invoking it. So, when a FACTDEB procedure is invoked, that procedure would have no deterministic way of knowing that an error has occurred and that the error procedure is about to be invoked. In fact, in general, a FACTDEB procedure should always check the <var>%(system):runSubsystemErrorProcedure</var> property before checking the value of the communications global (next procedure global).</li>		<li>The reason for this method is because APSY does not set the subsystem communications global to the error procedure's name before invoking it. So, when a FACTDEB procedure is invoked, that procedure would have no deterministic way of knowing that an error has occurred and that the error procedure is about to be invoked. In fact, in general, a FACTDEB procedure should always check the <var class="nobr">%(system):runSubsystemErrorProcedure</var> property before checking the value of the communications global (next procedure global).</li>
	</ul>		</ul>
	==Examples==		==Examples==
	The following code, presumably in a FACTDEB procedure, checks the <var>%(system):runSubsystemErrorProcedure</var> porperty and, if set, simply stops, allowing the error procedure to be run:		The following code, presumably in a FACTDEB procedure, checks the <var class="nobr">%(system):runSubsystemErrorProcedure</var> porperty and, if set, simply stops, allowing the error procedure to be run:
	<p class="code">if %(system):runSubsystemErrorProcedure then		<p class="code">if %(system):runSubsystemErrorProcedure then
	stop		stop

JAL: /* Syntax terms */

2014-02-16T00:24:18Z

Syntax terms

← Older revision		Revision as of 00:24, 16 February 2014
Line 7:		Line 7:
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%boolean</th><td><var>Boolean</var> value that indicates whether running the subsystem error procedure or whether running the [[FACTDEB parameter\|FACTDEB procedure]] before running the subsystem error procedure.</td></tr>		<tr><th>%boolean</th><td><var>Boolean</var> value that indicates whether running the subsystem error procedure or whether running the [[FACTDEB parameter\|FACTDEB procedure]] before running the subsystem error procedure.</td></tr>
	<tr><th ~~nowrap="true"~~><var>%(System)</var></th>
			<tr><th><var>%(System)</var></th>
	<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>		<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>
	</table>		</table>

Alex: /* Usage notes= */

2012-11-20T21:03:23Z

Usage notes=

← Older revision		Revision as of 21:03, 20 November 2012
Line 11:		Line 11:
	</table>		</table>

	=Usage notes==		==Usage notes==
	<ul>		<ul>
	<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>		<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>

Alex at 21:03, 20 November 2012

2012-11-20T21:03:09Z

← Older revision		Revision as of 21:03, 20 November 2012
Line 1:		Line 1:
	{{Template:System:RunSubsystemErrorProcedure subtitle}}		{{Template:System:RunSubsystemErrorProcedure subtitle}}

	This ~~page is~~ [[~~under construction~~]].		This property allows a [[FACTDEB parameter\|FACTDEB procedure]] to determine if the subsystem error procedure is about to be run and possibly also prevent that procedure from being run.
	==Syntax==		==Syntax==
	{{Template:System:RunSubsystemErrorProcedure syntax}}		{{Template:System:RunSubsystemErrorProcedure syntax}}
Line 11:		Line 11:
	</table>		</table>

	==Usage notes==		=Usage notes==
	<ul>		<ul>

	<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>		<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>

	<li>This method is most useful in a [[FACTDEB parameter\|FACTDEB procedure]]. It can be used to determine if the subsystem error procedure is about to be driven and to prevent that from happening (by setting the property to False).</li>		<li>This method is most useful in a [[FACTDEB parameter\|FACTDEB procedure]]. It can be used to determine if the subsystem error procedure is about to be driven and to prevent that from happening (by setting the property to False).</li>

	<li>The reason for this method is because APSY does not set the subsystem communications global to the error procedure's name before invoking it. So, when a FACTDEB procedure is invoked, that procedure would have no deterministic way of knowing that an error has occurred and that the error procedure is about to be invoked. In fact, in general, a FACTDEB procedure should always check the <var>%(system):runSubsystemErrorProcedure</var> property before checking the value of the communications global (next procedure global).</li>		<li>The reason for this method is because APSY does not set the subsystem communications global to the error procedure's name before invoking it. So, when a FACTDEB procedure is invoked, that procedure would have no deterministic way of knowing that an error has occurred and that the error procedure is about to be invoked. In fact, in general, a FACTDEB procedure should always check the <var>%(system):runSubsystemErrorProcedure</var> property before checking the value of the communications global (next procedure global).</li>

	</ul>		</ul>

	==Examples==		==Examples==
	The following code, presumably in a FACTDEB procedure, checks the <var>%(system):runSubsystemErrorProcedure</var> porperty and, if set, simply stops, allowing the error procedure to be run:		The following code, presumably in a FACTDEB procedure, checks the <var>%(system):runSubsystemErrorProcedure</var> porperty and, if set, simply stops, allowing the error procedure to be run:

	<p class="code">if %(system):runSubsystemErrorProcedure then		<p class="code">if %(system):runSubsystemErrorProcedure then
	stop		stop
	end if		end if
	</p>		</p>

	==See also==		==See also==
	{{Template:System:RunSubsystemErrorProcedure footer}}		{{Template:System:RunSubsystemErrorProcedure footer}}

Alex: /* Examples */

2012-11-20T21:01:35Z

Examples

← Older revision		Revision as of 21:01, 20 November 2012
Line 26:		Line 26:

	<p class="code">if %(system):runSubsystemErrorProcedure then		<p class="code">if %(system):runSubsystemErrorProcedure then

	stop		stop
			end if
	</p>		</p>

	==See also==		==See also==
	{{Template:System:RunSubsystemErrorProcedure footer}}		{{Template:System:RunSubsystemErrorProcedure footer}}

Alex: /* Examples */

2012-11-20T21:01:21Z

Examples

← Older revision		Revision as of 21:01, 20 November 2012
Line 23:		Line 23:

	==Examples==		==Examples==
			The following code, presumably in a FACTDEB procedure, checks the <var>%(system):runSubsystemErrorProcedure</var> porperty and, if set, simply stops, allowing the error procedure to be run:

			<p class="code">if %(system):runSubsystemErrorProcedure then

			stop

			</p>

	==See also==		==See also==
	{{Template:System:RunSubsystemErrorProcedure footer}}		{{Template:System:RunSubsystemErrorProcedure footer}}

Alex: /* Usage notes */

2012-11-20T20:59:30Z

Usage notes

← Older revision		Revision as of 20:59, 20 November 2012
Line 12:		Line 12:

	==Usage notes==		==Usage notes==
			<ul>

			<li>While a settable property, this property can never be set to <var>False</var>. This is because the only way the property can become False is when an error in a subsystem procedure would cause the subsystem error procedure to be drive.</li>

			<li>This method is most useful in a [[FACTDEB parameter\|FACTDEB procedure]]. It can be used to determine if the subsystem error procedure is about to be driven and to prevent that from happening (by setting the property to False).</li>

			<li>The reason for this method is because APSY does not set the subsystem communications global to the error procedure's name before invoking it. So, when a FACTDEB procedure is invoked, that procedure would have no deterministic way of knowing that an error has occurred and that the error procedure is about to be invoked. In fact, in general, a FACTDEB procedure should always check the <var>%(system):runSubsystemErrorProcedure</var> property before checking the value of the communications global (next procedure global).</li>

			</ul>

	==Examples==		==Examples==
	==See also==		==See also==
	{{Template:System:RunSubsystemErrorProcedure footer}}		{{Template:System:RunSubsystemErrorProcedure footer}}

Alex: /* Syntax terms */

2012-11-20T20:51:38Z

Syntax terms

← Older revision		Revision as of 20:51, 20 November 2012
Line 6:		Line 6:
	===Syntax terms===		===Syntax terms===
	<table class="syntaxTable">		<table class="syntaxTable">
	<tr><th>%boolean</th><td><var>Boolean</var> value</td></tr>		<tr><th>%boolean</th><td><var>Boolean</var> value that indicates whether running the subsystem error procedure or whether running the [[FACTDEB parameter\|FACTDEB procedure]] before running the subsystem error procedure.</td></tr>
	<tr><th nowrap="true"><var>%(System)</var></th>		<tr><th nowrap="true"><var>%(System)</var></th>
	<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>		<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>
	</table>		</table>

	==Usage notes==		==Usage notes==
	==Examples==		==Examples==
	==See also==		==See also==
	{{Template:System:RunSubsystemErrorProcedure footer}}		{{Template:System:RunSubsystemErrorProcedure footer}}

Wiccan: Automatically generated page update

2012-11-20T20:49:08Z

Automatically generated page update

New page

{{Template:System:RunSubsystemErrorProcedure subtitle}}

This page is [[under construction]].
==Syntax==
{{Template:System:RunSubsystemErrorProcedure syntax}}
===Syntax terms===
<table class="syntaxTable">
<tr><th>%boolean</th><td><var>Boolean</var> value</td></tr>
<tr><th nowrap="true"><var>%(System)</var></th>
<td>The class name in parentheses denotes a shared method. <var>RunSubsystemErrorProcedure</var> can also be invoked via a <var>System</var> object variable, which may be <var>Null</var>.</td></tr>
</table>
==Usage notes==
==Examples==
==See also==
{{Template:System:RunSubsystemErrorProcedure footer}}