Procedures - Revision history

JAL: /* Processing */ add link

2018-01-02T22:38:02Z

Processing: add link

← Older revision		Revision as of 22:38, 2 January 2018
Line 419:		Line 419:
	====Processing====		====Processing====
	<p>		<p>
	When <var class="product">Model 204</var> encounters an INCLUDE command, it reads the lines stored in the procedure and executes each system control command in the procedure. Any ~~User Language~~ requests in the procedure are compiled and executed.</p>		When <var class="product">Model 204</var> encounters an <var>INCLUDE</var> command, it reads the lines stored in the procedure and executes each system control command in the procedure. Any SOUL requests in the procedure are compiled and executed.</p>
	<p>		<p>
	The following commands cannot be issued from within a procedure:</p>		The following commands cannot be issued from within a procedure:</p>
	<ul>		<ul>
	<li>CREATEG</li>		<li>CREATEG</li>
	~~</li>~~
	<li>EOD</li>		<li>EOD</li>
	~~</li>~~
	<li>EOJ</li>		<li>EOJ</li>
	~~</li>~~
	<li>FILELOAD</li>		<li>FILELOAD</li>
	~~</li>~~
	<li>FLOD</li>		<li>FLOD</li>
	~~</li>~~
	<li>LOGWHO</li>		<li>LOGWHO</li>
	~~</li>~~
	<li>REGENERATE</li>		<li>REGENERATE</li>
	~~</li>~~
	<li>RENAME PROCEDURE</li>		<li>RENAME PROCEDURE</li>
	~~</li>~~
	<li>REORGANIZE</li>		<li>REORGANIZE</li>
	~~</li>~~
	<li>RESTART</li>		<li>RESTART</li>
	~~</li>~~
	<li>Z </li>		<li>Z </li>
	~~</li>~~
	</ul>		</ul>
	<p>		<p>
	Responses to dummy strings and $READ prompts can be specified as part of the INCLUDE command or statement, as described in [[#Dummy strings in procedures\|Dummy strings in procedures]]. </p>		Responses to dummy strings and <var>$READ</var> prompts can be specified as part of the <var>INCLUDE</var> command or statement, as described in [[#Dummy strings in procedures\|Dummy strings in procedures]]. </p>

	====Example====		====Example====
	<p>		<p>

JAL: /* Procedure aliases and security */ typo

2018-01-02T21:54:47Z

Procedure aliases and security: typo

← Older revision		Revision as of 21:54, 2 January 2018
Line 185:		Line 185:
	===Procedure aliases and security===		===Procedure aliases and security===
	<p>		<p>
	The <var>[[PROCEDURE command\|PROCEDURE]]</var> command also has options with which you can assign an alias to the procedure name or secure the procedure by assigning it to a procedure class.		The <var>[[PROCEDURE command\|PROCEDURE]]</var> command also has options with which you can assign an alias to the procedure name or secure the procedure by assigning it to a procedure class. </p>

	===Creating procedures with the Full Screen Editor===		===Creating procedures with the Full Screen Editor===
	<p>		<p>

Dme: /* Dummy strings */

2017-05-01T10:34:15Z

Dummy strings

← Older revision		Revision as of 10:34, 1 May 2017
Line 39:		Line 39:
	Procedures can themselves contain INCLUDE commands or statements, creating nested procedures. You can nest procedures up to four levels deep. Thus procedure A can include procedure B; procedure B can include procedure C; procedure C can include procedure D; and procedure D can include procedure E; but procedure E cannot include other procedures. See [[#Executing and defining procedures within procedures\|Executing and defining procedures within procedures]] a detailed discussion of procedure nesting. </p>		Procedures can themselves contain INCLUDE commands or statements, creating nested procedures. You can nest procedures up to four levels deep. Thus procedure A can include procedure B; procedure B can include procedure C; procedure C can include procedure D; and procedure D can include procedure E; but procedure E cannot include other procedures. See [[#Executing and defining procedures within procedures\|Executing and defining procedures within procedures]] a detailed discussion of procedure nesting. </p>

	===Dummy strings===		===<b id="Dummy strings"></b>Dummy strings===
			<!-- The id="Dummy strings" is because this section is pinned in a redirect page, which helps in searching-->
	<p>		<p>
	Dummy strings allow you to temporarily change certain statements within a procedure each time it is included.</p>		Dummy strings allow you to temporarily change certain statements within a procedure each time it is included.</p>

	===Opening non-Model 204 data sets from within procedures===		===Opening non-Model 204 data sets from within procedures===
	<p>		<p>

JAL: link repair

2017-04-07T21:36:03Z

link repair

← Older revision		Revision as of 21:36, 7 April 2017
Line 531:		Line 531:
	<p>		<p>
	The procedures in a file are not automatically available to all users. They might be available only for certain users or for certain operations. Procedure access and manipulation are protected by file-level and procedure-level security. This section provides a brief description of the two layers of procedure protection.		The procedures in a file are not automatically available to all users. They might be available only for certain users or for certain operations. Procedure access and manipulation are protected by file-level and procedure-level security. This section provides a brief description of the two layers of procedure protection.
	For a complete discussion of file and procedure security, see [[~~Security~~]]. </p>		For a complete discussion of file and procedure security, see [[Model 204 security features]]. </p>

	===Procedure protection===		===Procedure protection===
Line 576:		Line 576:
	<p>		<p>
	For more information about		For more information about
	<var class="product">Model 204</var> security features, see [[~~Security~~]].		<var class="product">Model 204</var> security features, see [[Model 204 security features]].
	</p>		</p>

JALWiccan: Automatically generated page update

2017-04-07T21:27:04Z

Automatically generated page update

← Older revision		Revision as of 21:27, 7 April 2017
Line 549:		Line 549:
	The access rights for your user class can also later be modified for some or all procedures if the file manager secures file procedures. </p>		The access rights for your user class can also later be modified for some or all procedures if the file manager secures file procedures. </p>
	<p>		<p>
	See the note on the following page for more information about the effect on privilege determination of modifications to access rights. For more information about file privileges, see [[~~Security~~#File privileges\|File privileges]]. </p>		See the note on the following page for more information about the effect on privilege determination of modifications to access rights. For more information about file privileges, see [[Model 204 security features#File privileges\|File privileges]]. </p>

	====Gaining procedure access====		====Gaining procedure access====

JAL: misc cleanup

2016-12-06T15:53:28Z

misc cleanup

Show changes

JDamon: /* Specifying dummy string responses in the INCLUDE command */

2016-12-04T19:31:11Z

Specifying dummy string responses in the INCLUDE command

← Older revision		Revision as of 19:31, 4 December 2016
Line 1,024:		Line 1,024:
	<p class="code">INCLUDE TEST, 100340		<p class="code">INCLUDE TEST, 100340
	</p>		</p>

	<p>		<p>
	~~Therefore~~, the INCL.RPT: statement in procedure TEST could be written:</p>		In this case, the INCL.RPT: statement in procedure TEST could be written as one line:</p>
	<p class="code">INCL.RPT: INCLUDE REPT, FULLNAME AND DRIVER ID, POLICY NO AND STATE		<p class="code">INCL.RPT: INCLUDE REPT, FULLNAME AND DRIVER ID, POLICY NO AND STATE
	</p>		</p>

JDamon: /* Specifying dummy string responses in the INCLUDE command */

2016-12-02T18:30:42Z

Specifying dummy string responses in the INCLUDE command

← Older revision		Revision as of 18:30, 2 December 2016
Line 1,025:		Line 1,025:
	</p>		</p>
	<p>		<p>
	Therefore, the INCL.RPT statement in procedure TEST could be written:</p>		Therefore, the INCL.RPT: statement in procedure TEST could be written:</p>
	<p class="code">INCL.RPT: INCLUDE REPT, FULLNAME AND DRIVER ID, POLICY NO AND STATE		<p class="code">INCL.RPT: INCLUDE REPT, FULLNAME AND DRIVER ID, POLICY NO AND STATE
	</p>		</p>

JDamon: INCL.RPT:INCLUDE ... needed a blank

2016-12-02T18:29:32Z

INCL.RPT:INCLUDE ... needed a blank

← Older revision		Revision as of 18:29, 2 December 2016
Line 1,025:		Line 1,025:
	</p>		</p>
	<p>		<p>
	Therefore, the INCL.~~REPT~~ statement in procedure TEST could be written:</p>		Therefore, the INCL.RPT statement in procedure TEST could be written:</p>
	<p class="code">INCL.RPT:INCLUDE REPT,FULLNAME AND DRIVER ID,POLICY NO AND STATE		<p class="code">INCL.RPT: INCLUDE REPT, FULLNAME AND DRIVER ID, POLICY NO AND STATE
	</p>		</p>

	==Using ?$ and ?& dummy strings==		==Using ?$ and ?& dummy strings==

JDamon: added this label - INCL.RPT: INCLUDE REPT

2016-12-02T18:23:41Z

added this label - INCL.RPT: INCLUDE REPT

← Older revision		Revision as of 18:23, 2 December 2016
Line 997:		Line 997:
	POLICY NO = ??ENTER.POLICY.NO		POLICY NO = ??ENTER.POLICY.NO
	END FIND		END FIND
	INCLUDE REPT		INCL.RPT: INCLUDE REPT
	FULLNAME AND DRIVER ID		FULLNAME AND DRIVER ID
	POLICY NO AND STATE		POLICY NO AND STATE
Line 1,014:		Line 1,014:
	<p>		<p>
	Assume that the user includes the procedure TEST from his/her terminal. The user is prompted with ??ENTER.POLICY.NO and enters a valid policy number. When procedure REPT is included from procedure TEST, the user is not prompted. <var class="product">Model 204</var> automatically substitutes FULLNAME AND DRIVER ID for ??REPORT.1 and POLICY NO AND STATE for ??REPORT.2.</p>		Assume that the user includes the procedure TEST from his/her terminal. The user is prompted with ??ENTER.POLICY.NO and enters a valid policy number. When procedure REPT is included from procedure TEST, the user is not prompted. <var class="product">Model 204</var> automatically substitutes FULLNAME AND DRIVER ID for ??REPORT.1 and POLICY NO AND STATE for ??REPORT.2.</p>

	====User parameters====		====User parameters====
	<p>		<p>