Model 204 naming conventions - Revision history

ELowell: /* Model 204 file names */

2016-09-26T20:35:30Z

Model 204 file names

← Older revision		Revision as of 20:35, 26 September 2016
Line 9:		Line 9:
	<li>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </li>		<li>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </li>
	<li>Filenames cannot begin with a number, nor with any of the following:		<li>Filenames cannot begin with a number, nor with any of the following:
	<p class="code">CCA		<p class="code">CCA (except for [[System requirements for Application Subsystems#Creating CCASYS\|CCASYS]])
	SYS		SYS
	OUT		OUT
	TAPE </p>		TAPE </p>
	~~The only exception is [[System requirements for Application Subsystems#Creating CCASYS\|CCASYS]].~~
	</li>		</li>
	<li>Filenames can either describe the file content or conform to local file-naming standards. For example:		<li>Filenames can either describe the file content or conform to local file-naming standards. For example:

ELowell: /* Model 204 file names */

2016-09-26T20:23:25Z

Model 204 file names

← Older revision		Revision as of 20:23, 26 September 2016
Line 8:		Line 8:
	<li>File names cannot be <var>FILE</var> or <var>GROUP</var>.</li>		<li>File names cannot be <var>FILE</var> or <var>GROUP</var>.</li>
	<li>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </li>		<li>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </li>
	<li>Filenames cannot begin with a number~~.</li>~~		<li>Filenames cannot begin with a number, nor with any of the following:
	~~<li>Filenames cannot begin~~ with any of the following:
	<p class="code">CCA		<p class="code">CCA
	SYS		SYS
	OUT		OUT
	TAPE </p>		TAPE </p>
	The only exception is ~~CCASYS: it can be created in a single user run with the <var>~~[[~~SYSOPT parameter~~\|~~SYSOPT~~]]~~</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for APSY~~.		The only exception is [[System requirements for Application Subsystems#Creating CCASYS\|CCASYS]].
	</li>		</li>
	<li>Filenames can either describe the file content or conform to local file-naming standards. For example:		<li>Filenames can either describe the file content or conform to local file-naming standards. For example:

ELowell: /* Model 204 file names */

2016-09-26T20:09:44Z

Model 204 file names

← Older revision		Revision as of 20:09, 26 September 2016
Line 3:		Line 3:

	==Model 204 file names==		==Model 204 file names==
	~~<p>~~
	~~File names are limited to 8 characters (7 for DOS systems).</p>~~
	~~<p>Filenames cannot be <var>FILE</var> or <var>GROUP</var> and cannot start with <code>CCA</code>, <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number.</p>~~
	<p>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. They must begin with an uppercase letter (A-Z) or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </p>

	<p>The Model 204 restrictions are as follows: </p>		<p>The Model 204 restrictions are as follows: </p>

	<ul>		<ul>
	<li>~~A filename~~ cannot begin with any of the following:		<li>File names are limited to 8 characters (7 for DOS systems).</li>
			<li>File names cannot be <var>FILE</var> or <var>GROUP</var>.</li>
			<li>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </li>
			<li>Filenames cannot begin with a number.</li>
			<li>Filenames cannot begin with any of the following:
	<p class="code">CCA		<p class="code">CCA
	SYS		SYS
	OUT		OUT
	TAPE </p>		TAPE </p>
			The only exception is CCASYS: it can be created in a single user run with the <var>[[SYSOPT parameter\|SYSOPT]]</var> X’01’ bit turned off to prevent Model 204 from opening CCASYS to make it available for APSY.
	</li>		</li>

	~~<li>A filename must contain only alphanumeric characters (A-Z, 0-9).~~
	~~</li>~~

	<li>Filenames can either describe the file content or conform to local file-naming standards. For example:		<li>Filenames can either describe the file content or conform to local file-naming standards. For example:
	<p class="code">EMPLOYE		<p class="code">EMPLOYE

ELowell: /* Model 204 file names */

2016-09-26T17:42:48Z

Model 204 file names

← Older revision		Revision as of 17:42, 26 September 2016
Line 5:		Line 5:
	<p>		<p>
	File names are limited to 8 characters (7 for DOS systems).</p>		File names are limited to 8 characters (7 for DOS systems).</p>
			<p>Filenames cannot be <var>FILE</var> or <var>GROUP</var> and cannot start with <code>CCA</code>, <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number.</p>
	<p>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. They must begin with an uppercase letter (A-Z) or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </p>		<p>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. They must begin with an uppercase letter (A-Z) or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </p>

ELowell: /* Model 204 file names */

2016-09-26T17:11:07Z

Model 204 file names

← Older revision		Revision as of 17:11, 26 September 2016
Line 4:		Line 4:
	==Model 204 file names==		==Model 204 file names==
	<p>		<p>
	File names are limited to 8 characters (7 for DOS systems) ~~and~~ must begin with a letter (A-Z). </p>		File names are limited to 8 characters (7 for DOS systems).</p>
			<p>File names can contain uppercase letters, numeric digits, or the characters @, #, or $. They must begin with an uppercase letter (A-Z) or the characters @, #, or $. (The character $ is displayed differently in some countries, often as £). </p>

	<p>The Model 204 restrictions are as follows: </p>		<p>The Model 204 restrictions are as follows: </p>

JAL: /* Statement labels */ add link

2015-07-02T20:14:36Z

Statement labels: add link

← Older revision		Revision as of 20:14, 2 July 2015
Line 317:		Line 317:
	==Statement labels==		==Statement labels==
	<p>		<p>
	Limit statement labels to 20 characters and use them wisely. Use statement labels rather than line numbers in new applications. </p>		Limit [[Request composition rules#Statement labels\|statement labels]] to twenty characters, and use them wisely. Use statement labels rather than line numbers in new applications. </p>

	<p>However, do not try to modify a numbered application to include a mixture of statement numbers and statement labels. If you mix statement labels and statement numbers, or incorrectly modify an application, you might cause Model 204 to branch incorrectly. </p>		<p>However, do not try to modify a numbered application to include a mixture of statement numbers and statement labels. If you mix statement labels and statement numbers, or incorrectly modify an application, you might cause Model 204 to branch incorrectly. </p>

	<p>To restrict the use of statement numbers at your site, set <var>[[FOPT parameter\|FOPT]]</var> to X’80'. </p>		<p>To restrict the use of statement numbers at your site, set <var>[[FOPT parameter\|FOPT]]</var> to X’80'. </p>
Line 326:		Line 326:

	<ul>		<ul>
	<li>		<li>Start with an alphabetic character (A-Z) </li>
	~~start~~ with an alphabetic character (A-Z)
	</li>

	<li>		<li>Contain only A-Z, 0-9, period (<tt>.</tt>), or underscore (<tt>_</tt>) </li>
	~~contain~~ only A-Z, 0-9, period (<tt>.</tt>), or underscore (<tt>_</tt>)
	</li>

	<li>		<li>End with a colon and space (<tt>: </tt>) </li>
	~~end~~ with a colon and space (<tt>: </tt>)
	</li>
	</ul>		</ul>

Line 352:		Line 346:

	<table>		<table>
			<tr class="head"><th>Label</th><th>Statement</th></tr>

	<tr>		<tr>
	<td>FD.WELL.NAME: </td> <td>FIND RECORDS </td>		<td>FD.WELL.NAME: </td> <td>FIND RECORDS </td>
Line 384:		Line 380:
	<ul>		<ul>

	<li>FIND statements (except FIND ALL VALUES)		<li><var>FIND</var> statements (except <var>FIND ALL VALUES</var>) </li>
	</li>

	<li>FOR loops		<li><var>FOR</var> loops </li>
	</li>

	<li>STORE		<li><var>STORE</var> </li>
	</li>

	<li>ON		<li><var>ON</var> </li>
	</li>

	<li>Subroutines		<li>Subroutines </li>
	</li>
	</ul>		</ul>

JAL: more conversion cleanup

2015-06-30T17:00:08Z

more conversion cleanup

Show changes

DCameron: /* Statement labels */

2014-09-11T14:51:36Z

Statement labels

← Older revision		Revision as of 14:51, 11 September 2014
Line 376:		Line 376:

	<li>		<li>
	A statement that follows a FIND or STORE statement and does not have an END statement. However, ~~Technical Support strongly recommends using~~ an END statement ~~instead~~.		A statement that follows a FIND or STORE statement and does not have an END statement. However, the coding of an END statement is preferrable in this situation.
	</li>		</li>
	</ul>		</ul>

DCameron: /* Statement labels */

2014-09-11T14:45:07Z

Statement labels

← Older revision		Revision as of 14:45, 11 September 2014
Line 348:		Line 348:
	</p>		</p>

	<p>Use consistent names throughout a procedure~~. Technical Support recommends using~~ standard prefixes for all applications such as FD. for FIND statements, CT. for COUNT statements, and so on. For example: </p>		<p>Use consistent names throughout a procedure, with standard prefixes for all applications such as FD. for FIND statements, CT. for COUNT statements, and so on. For example: </p>

	<table>		<table>

DCameron: /* Statement labels */

2014-09-11T14:42:41Z

Statement labels

← Older revision		Revision as of 14:42, 11 September 2014
Line 320:		Line 320:
	<p>However, do not try to modify a numbered application to include a mixture of statement numbers and statement labels. If you mix statement labels and statement numbers, or incorrectly modify an application, you might cause Model 204 to branch incorrectly. </p>		<p>However, do not try to modify a numbered application to include a mixture of statement numbers and statement labels. If you mix statement labels and statement numbers, or incorrectly modify an application, you might cause Model 204 to branch incorrectly. </p>

	<p>To restrict the use of statement numbers at your site, set <var>[[FOPT_parameter\|FOPT]]</var> to X’80'~~. For more information on FOPT, see the [[#Category:Model 204 files\|Rocket Model 204 File Management wiki pages]]~~. </p>		<p>To restrict the use of statement numbers at your site, set <var>[[FOPT_parameter\|FOPT]]</var> to X’80'. </p>

	<p>Statement labels must: </p>		<p>Statement labels must: </p>