MSIR.0975 - Revision history

DCameron at 15:26, 20 June 2018

2018-06-20T15:26:12Z

← Older revision		Revision as of 15:26, 20 June 2018
Line 1:		Line 1:
	{{Template:MSIR.0975 skeleton}}		{{Template:MSIR.0975 skeleton}}
			<!--Test SOUL.DNC.004.QA in QASHR exercises at least some MSIR.0975 cases. PDS-6626 -->
	<p>		<p>
	A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. The following examples are among the texts that might be displayed with this message:		A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. The following examples are among the texts that might be displayed with this message:

JAL: add `'s`

2018-06-07T21:52:10Z

add <var>'s

← Older revision		Revision as of 21:52, 7 June 2018
Line 1:		Line 1:
	{{Template:MSIR.0975 skeleton}}		{{Template:MSIR.0975 skeleton}}
	<p>		<p>
	A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. The following examples are ~~amongst~~ the texts that might be displayed with this message:		A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. The following examples are among the texts that might be displayed with this message:
	</p>		</p>
	<ul>		<ul>
	<li>The <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:		<li>The <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:
	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block</p></li>		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block </p></li>
	<li> A Catch statement specifies a base class followed by its extension class, which ~~isn't~~ allowed. The Catch statement can specify a base class, ~~and~~ extension class, or extension followed by the base class being extended, but not base followed by extension. In this case the following ~~messages~~ is produced:
	<p class="code>MSIR.0975: CATCH invalid -- extension class after base class</p></li>		<li>A <var>Catch</var> statement specifies a base class followed by its extension class, which is not allowed. The <var>Catch</var> statement can specify a base class, an extension class, or an extension followed by the base class being extended, but it must not specify a base followed by an extension. In this latter case, the following message is produced:
	<li>The only valid syntactical words that can follow an exception class name on a Catch statement are 'To', to specify the object to which a caught exception is being saved, and 'And' to introduce an additional exception class to catch. Any other words ~~will be~~ rejected with the following message:		<p class="code>MSIR.0975: CATCH invalid -- extension class after base class </p></li>
	<p class="code>MSIR.0975: CATCH invalid -- invalid word after class name</p></li>
	<li>The Catch statement specifies a To clause to save the exception to an object, but the object variable name is missing. In this case the following message is produced:		<li>The only valid syntactical words that can follow an exception class name on a <var>Catch</var> statement are <var>To</var> (to specify the object to which a caught exception is being saved) and <var>And</var> (to introduce an additional exception class to catch). Any other words are rejected with the following message:
			<p class="code>MSIR.0975: CATCH invalid -- invalid word after class name </p></li>

			<li>The <var>Catch</var> statement specifies a <var>To</var> clause to save the exception to an object, but the object variable name is missing. In this case the following message is produced:
	<p class="code>MSIR.0975: CATCH invalid -- target object variable missing</p></li>		<p class="code>MSIR.0975: CATCH invalid -- target object variable missing</p></li>
	</ul>		</ul>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 13:56, 7 June 2018

2018-06-07T13:56:04Z

← Older revision		Revision as of 13:56, 7 June 2018
Line 10:		Line 10:
	<li>The only valid syntactical words that can follow an exception class name on a Catch statement are 'To', to specify the object to which a caught exception is being saved, and 'And' to introduce an additional exception class to catch. Any other words will be rejected with the following message:		<li>The only valid syntactical words that can follow an exception class name on a Catch statement are 'To', to specify the object to which a caught exception is being saved, and 'And' to introduce an additional exception class to catch. Any other words will be rejected with the following message:
	<p class="code>MSIR.0975: CATCH invalid -- invalid word after class name</p></li>		<p class="code>MSIR.0975: CATCH invalid -- invalid word after class name</p></li>
			<li>The Catch statement specifies a To clause to save the exception to an object, but the object variable name is missing. In this case the following message is produced:
			<p class="code>MSIR.0975: CATCH invalid -- target object variable missing</p></li>
	</ul>		</ul>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 13:42, 7 June 2018

2018-06-07T13:42:12Z

← Older revision		Revision as of 13:42, 7 June 2018
Line 8:		Line 8:
	<li> A Catch statement specifies a base class followed by its extension class, which isn't allowed. The Catch statement can specify a base class, and extension class, or extension followed by the base class being extended, but not base followed by extension. In this case the following messages is produced:		<li> A Catch statement specifies a base class followed by its extension class, which isn't allowed. The Catch statement can specify a base class, and extension class, or extension followed by the base class being extended, but not base followed by extension. In this case the following messages is produced:
	<p class="code>MSIR.0975: CATCH invalid -- extension class after base class</p></li>		<p class="code>MSIR.0975: CATCH invalid -- extension class after base class</p></li>
			<li>The only valid syntactical words that can follow an exception class name on a Catch statement are 'To', to specify the object to which a caught exception is being saved, and 'And' to introduce an additional exception class to catch. Any other words will be rejected with the following message:
			<p class="code>MSIR.0975: CATCH invalid -- invalid word after class name</p></li>
	</ul>		</ul>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 15:55, 6 June 2018

2018-06-06T15:55:44Z

← Older revision		Revision as of 15:55, 6 June 2018
Line 6:		Line 6:
	<li>The <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:		<li>The <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:
	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block</p></li>		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block</p></li>
			<li> A Catch statement specifies a base class followed by its extension class, which isn't allowed. The Catch statement can specify a base class, and extension class, or extension followed by the base class being extended, but not base followed by extension. In this case the following messages is produced:
			<p class="code>MSIR.0975: CATCH invalid -- extension class after base class</p></li>
	</ul>		</ul>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 14:47, 31 May 2018

2018-05-31T14:47:38Z

← Older revision		Revision as of 14:47, 31 May 2018
Line 1:		Line 1:
	{{Template:MSIR.0975 skeleton}}		{{Template:MSIR.0975 skeleton}}
	<p>		<p>
	A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. ~~One possibility is~~ that ~~the <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must~~ be~~, in which case the following~~ message ~~is produced~~:		A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. The following examples are amongst the texts that might be displayed with this message:
	</p>		</p>
	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block		<ul>
	</p>		<li>The <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:
			<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block</p></li>
			</ul>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

ELowell at 17:11, 24 May 2018

2018-05-24T17:11:15Z

← Older revision		Revision as of 17:11, 24 May 2018
Line 1:		Line 1:
	{{Template:MSIR.0975 skeleton}}		{{Template:MSIR.0975 skeleton}}
	<p>		<p>
	A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. One possibility is that the <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must, in which case the following message if produced:		A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. One possibility is that the <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must be, in which case the following message is produced:
	</p>		</p>
	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block
	</p>		</p>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

JAL: add link

2018-05-24T17:04:26Z

add link

← Older revision		Revision as of 17:04, 24 May 2018
Line 1:		Line 1:
	{{Template:MSIR.0975 skeleton}}		{{Template:MSIR.0975 skeleton}}
	<p>		<p>
	A Catch statement or block ~~has been~~ coded in an invalid context. One possibility is that the ~~catch~~ statement or block ~~isn't coded~~ within a valid Try block, as it must, in which case the following message if produced		A <var>[[Exceptions#Try and Catch\|Catch]]</var> statement or block was coded in an invalid context. One possibility is that the <var>Catch</var> statement or block is not located within a valid <var>Try</var> block, as it must, in which case the following message if produced:
	</p>		</p>

	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block
	</p>		</p>

	~~<p>~~
	~~<b>Response:</b>~~
	~~</p>~~
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 15:03, 24 May 2018

2018-05-24T15:03:44Z

← Older revision		Revision as of 15:03, 24 May 2018
Line 6:		Line 6:
	<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block
	</p>		</p>
	~~</p>~~
	<p>		<p>
	<b>Response:</b>		<b>Response:</b>
	</p>		</p>
	{{Template:MSIR.0975 footer}}		{{Template:MSIR.0975 footer}}

DCameron at 15:03, 24 May 2018

2018-05-24T15:03:12Z

← Older revision		Revision as of 15:03, 24 May 2018
Line 4:		Line 4:
	</p>		</p>

	<p class="code>		<p class="code>MSIR.0975: CATCH invalid -- not inside a Try block
	MSIR.0975: CATCH invalid -- not inside a Try block
	</p>		</p>
	</p>		</p>

MSIR.0975 - Revision history

DCameron at 15:26, 20 June 2018

JAL: add 's

DCameron at 13:56, 7 June 2018

DCameron at 13:42, 7 June 2018

DCameron at 15:55, 6 June 2018

DCameron at 14:47, 31 May 2018

ELowell at 17:11, 24 May 2018

JAL: add link

DCameron at 15:03, 24 May 2018

DCameron at 15:03, 24 May 2018

JAL: add `'s`