Model 204 coding guidelines - Revision history

JAL: misc formatting

2018-04-25T17:20:13Z

misc formatting

DCameron: /* Finding records efficiently */

2014-09-11T14:09:39Z

Finding records efficiently

← Older revision		Revision as of 14:09, 11 September 2014
Line 416:		Line 416:
	<td>Non-KEY, non-ORDERED</td> <td><ul><li>Table A for field code validation (during compilation)</li> <li>Table B direct file search</li></ul></td></tr>		<td>Non-KEY, non-ORDERED</td> <td><ul><li>Table A for field code validation (during compilation)</li> <li>Table B direct file search</li></ul></td></tr>
	<tr>		<tr>
	<td>KEY</td> <td><ul><li>Table A for field code validation (during compilation)</li>		<td>KEY</td> <td><ul><li><var>[[Table_A_(File_architecture)\|Table A]]</var> for field code validation (during compilation)</li>
	<li>Table C for information (hashed access)</li>		<li><var>[[Table_C_(File_architecture)\|Table C]]</var> for information (hashed access)</li>
	<li>If not single record entry Table D for list or bit map</li>		<li>If not single record entry <var>[[Table_D_(File_architecture)\|Table D]]</var> for list or bit map</li>
	</ul></td></tr>		</ul></td></tr>

DCameron: /* Finding records efficiently */

2014-09-11T14:01:01Z

Finding records efficiently

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

	<p>If you must search on a non-key field, try to pair the FIND with a Boolean AND using a key field as the other search criterion. The key field search is performed first, which means (ideally) that there are fewer records in the set requiring a Table B search. This helps minimize Table B access. You might also want to consider redefining fields so that they meet the more efficient search criteria. </p>		<p>If you must search on a non-key field, try to pair the FIND with a Boolean AND using a key field as the other search criterion. The key field search is performed first, which means (ideally) that there are fewer records in the set requiring a <var>[[Table_B_(File_architecture)\|Table B]]</var> search. This helps minimize Table B access. You might also want to consider redefining fields so that they meet the more efficient search criteria. </p>

	<p>In the following example, NAME is non-key and RECTYPE is key. The RECTYPE = DRIVER records are evaluated first using the KEY indices; NAME is then ANDed by performing a Table B search on each record in the RECTYPE = DRIVER set. </p>		<p>In the following example, NAME is non-key and RECTYPE is key. The RECTYPE = DRIVER records are evaluated first using the KEY indices; NAME is then ANDed by performing a Table B search on each record in the RECTYPE = DRIVER set. </p>

DCameron: /* Using %variables in IF statements */

2014-09-11T13:57:44Z

Using %variables in IF statements

← Older revision		Revision as of 13:57, 11 September 2014
Line 260:		Line 260:
	===Using %variables in IF statements===		===Using %variables in IF statements===

	<p>IF statement expressions are rendered more readable by using meaningful %variable names, label names, or $functions such as $ONEOF or $INDEX to describe the condition. For example, the sample IF statement in the previous section is clearer when written as: </p>		<p>IF statement expressions are rendered more readable by using meaningful %variable names, label names, or $functions such as <var>[[$ONEOF\|$ONEOF]]</var> or <var>[[$INDEX\|$INDEX]]</var> to describe the condition. For example, the sample IF statement in the previous section is clearer when written as: </p>

	<p class="code">IF NOT $ONEOF (%VALID.DATA, 'A/B/C/D','/) THEN...		<p class="code">IF NOT $ONEOF (%VALID.DATA, 'A/B/C/D','/) THEN...

DCameron: /* Evaluating IF statements */

2014-09-11T13:55:20Z

Evaluating IF statements

← Older revision		Revision as of 13:55, 11 September 2014
Line 253:		Line 253:
	<p>The condition following the IF statement is always evaluated to zero or nonzero. Therefore, it is more efficient to use the expression IF %N rather than IF %N NE 0 and, conversely, IF NOT %N rather than IF %N = 0. </p>		<p>The condition following the IF statement is always evaluated to zero or nonzero. Therefore, it is more efficient to use the expression IF %N rather than IF %N NE 0 and, conversely, IF NOT %N rather than IF %N = 0. </p>

	<p>If you are evaluating a number of not equal (or equal) comparisons against a known set of values, (that is, IF %A NE 'A' and %A NE 'B'...), then use the following syntax. This uses about half the CPU time as well as reducing the amount of needed NTBL, QTBL, and VTBL: </p>		<p>If you are evaluating a number of not equal (or equal) comparisons against a known set of values, (that is, IF %A NE 'A' and %A NE 'B'...), then use the following syntax. This uses about half the CPU time as well as reducing the amount of needed NTBL, <var>[[LQTBL_parameter\|QTBL]]</var>, and VTBL: </p>

	<p class="code">IF NOT $ONEOF (%A, 'A/B/C/D','/') THEN...		<p class="code">IF NOT $ONEOF (%A, 'A/B/C/D','/') THEN...

DCameron: /* Using commands */

2014-09-11T13:50:57Z

Using commands

← Older revision		Revision as of 13:50, 11 September 2014
Line 109:		Line 109:

	<li>		<li>
	Keep track of any system-level parameters that you set; that is, RESET MCPU, MBSCAN, ERMX. You can monitor system-level parameters from the audit trail.		Keep track of any system-level parameters that you set; that is, RESET <var>[[MCPU_parameter\|MCPU]]</var>, <var>[[MBSCAN_parameter\|MBSCAN]]</var>, <var>[[ERMX_parameter\|ERMX]]</var>. You can monitor system-level parameters from the audit trail.
	</li>		</li>

DCameron: /* Using commands */

2014-09-11T13:48:08Z

Using commands

← Older revision		Revision as of 13:48, 11 September 2014
Line 105:		Line 105:

	<li>		<li>
	Set <var>[[UTABLE_command\|UTABLE]]</var> parameters in the login procedure, especially if most procedures require the same general server size. Change individual procedures as needed, but be sure to reset the parameters. Use the TIME REQUEST command to obtain suggested values for table settings to help optimize the performance.		Set <var>[[UTABLE_command\|UTABLE]]</var> parameters in the login procedure, especially if most procedures require the same general server size. Change individual procedures as needed, but be sure to reset the parameters. Use the <var>[[TIME_command\|TIME REQUEST]]</var> command to obtain suggested values for table settings to help optimize the performance.
	</li>		</li>

DCameron: /* Using commands */

2014-09-11T13:46:21Z

Using commands

← Older revision		Revision as of 13:46, 11 September 2014
Line 105:		Line 105:

	<li>		<li>
	Set UTABLE parameters in the login procedure, especially if most procedures require the same general server size. Change individual procedures as needed, but be sure to reset the parameters. Use the TIME REQUEST command to obtain suggested values for table settings to help optimize the performance.		Set <var>[[UTABLE_command\|UTABLE]]</var> parameters in the login procedure, especially if most procedures require the same general server size. Change individual procedures as needed, but be sure to reset the parameters. Use the TIME REQUEST command to obtain suggested values for table settings to help optimize the performance.
	</li>		</li>

DCameron: /* Sample coding structure */

2014-09-11T13:42:56Z

Sample coding structure

← Older revision		Revision as of 13:42, 11 September 2014
Line 25:		Line 25:

	<tr>		<tr>
	<td>BEGIN</td>		<td><var>[[BEGIN_command\|BEGIN]]</var></td>
	<TD/>		<TD/>
	</tr>		</tr>

DCameron: /* Using dummy strings in subroutines */

2014-09-11T13:24:10Z

Using dummy strings in subroutines

← Older revision		Revision as of 13:24, 11 September 2014
Line 1,101:		Line 1,101:

	<p>For nonapplication subsystem facility subroutines that contain file or group-specific statements such as FOR EACH RECORD, FOR EACH VALUE, or FIND, but where the file or group can vary, use dummy strings on any line where the filename is needed.</p>		<p>For nonapplication subsystem facility subroutines that contain file or group-specific statements such as FOR EACH RECORD, FOR EACH VALUE, or FIND, but where the file or group can vary, use dummy strings on any line where the filename is needed.</p>
	<p>The following example shows mixed use of both ?? and ?& dummy strings to prompt for a filename and then use that file within the procedures. The use of dummy strings is governed by the <var>[[SUB_parameter\|SUB]]</var> and PROMPT parameters. See the [[#Category:SOUL\|Rocket Model 204 SOUL wiki pages]] and the [[#Category:Parameters\|Rocket Model 204 Parameter wiki pages]] for more information about using dummy strings in procedures ~~and for information about the SUB and PROMPT~~ parameters. </p>		<p>The following example shows mixed use of both ?? and ?& dummy strings to prompt for a filename and then use that file within the procedures. The use of dummy strings is governed by the <var>[[SUB_parameter\|SUB]]</var> and <var>[[PROMPT_parameter\|PROMPT]]</var> parameters. See the [[#Category:SOUL\|Rocket Model 204 SOUL wiki pages]] and the [[#Category:Parameters\|Rocket Model 204 Parameter wiki pages]] for more information about using dummy strings in procedures.PT parameters. </p>

	<p>This example consists of three procedures: SETNAME, which finds the filename; MAKELIST, which places the desired records on a list; and PRINT.REC, which prints the records. </p>		<p>This example consists of three procedures: SETNAME, which finds the filename; MAKELIST, which places the desired records on a list; and PRINT.REC, which prints the records. </p>