$RdProc - Revision history

Mlarocca: /* Status settings */

2014-07-29T19:21:09Z

Status settings

← Older revision		Revision as of 19:21, 29 July 2014
Line 130:		Line 130:
	==Status settings==		==Status settings==
	<p>		<p>
	Possible return (<var>$~~STATUS~~</var>) settings are summarized in this table: </p>		Possible return (<var>$Status</var>) settings are summarized in this table: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 149:		Line 149:
	<tr>		<tr>
	<td align="right">2</td>		<td align="right">2</td>
	<td>Error occurred (see [[#$~~STATUSD~~ setting\|$~~STATUSD~~ settings]])</td>		<td>Error occurred (see [[#$StatusD setting\|$StatusD settings]])</td>
	</tr>		</tr>
	</table>		</table>
	<p>		<p>
	If the completion status is 2 and indicates that an error occurred or that the EOP was read, the procedure is automatically closed. A subsequent $RDPROC CLOSE call is unnecessary and returns this message: </p>		If the completion status is 2 and indicates that an error occurred or that the EOP was read, the procedure is automatically closed. A subsequent $RDPROC CLOSE call is unnecessary and returns this message: </p>
	<p class="code">$~~STATUS~~=2 / $~~STATUSD~~=11 (invalid ctlid value)		<p class="code">$Status=2 / $StatusD=11 (invalid ctlid value)
	</p>		</p>

	====$~~STATUSD~~ setting====		====$StatusD setting====
	<p>		<p>
	The <var>$~~STATUSD~~</var> setting can be one of the settings summarized in the following table:</p>		The <var>$StatusD</var> setting can be one of the settings summarized in the following table:</p>
	<table>		<table>
	<tr class="head">		<tr class="head">

Mlarocca: /* Syntax for reading a line from a procedure */

2014-07-29T19:19:27Z

Syntax for reading a line from a procedure

← Older revision		Revision as of 19:19, 29 July 2014
Line 97:		Line 97:
	Where:</p>		Where:</p>
	<ul>		<ul>
	<li><var class="term">text</var> is the next line of the procedure. (<var class="term">text</var> is set to null when end-of-procedure is reached; however, since procedure lines can be null, always check <var>[[$~~STATUS~~]]</var> to determine end-of-procedure.)</li>		<li><var class="term">text</var> is the next line of the procedure. (<var class="term">text</var> is set to null when end-of-procedure is reached; however, since procedure lines can be null, always check <var>[[$Status]]</var> to determine end-of-procedure.)</li>

	<li><var class="term">ctlid</var> is the integer ID of an internally maintained control ID that is assigned during OPEN processing.</li>		<li><var class="term">ctlid</var> is the integer ID of an internally maintained control ID that is assigned during OPEN processing.</li>

Mlarocca: Mlarocca moved page $RDPROC to $RdProc: Lower case change

2014-07-29T14:15:04Z

Mlarocca moved page $RDPROC to $RdProc: Lower case change

← Older revision	Revision as of 14:15, 29 July 2014
(No difference)

JAL at 23:18, 10 July 2014

2014-07-10T23:18:52Z

← Older revision		Revision as of 23:18, 10 July 2014
Line 2:		Line 2:

	<p>		<p>
	The $RDPROC function sequentially retrieves the lines of a procedure that is stored in a <var class="product">Model 204</var> file. The lines of the procedure can reside in a file or in a group (one or multiple procedure files). Multiple procedure files are searched in the order in which they appear in the <var>[[~~DEFINE~~ GROUP command\|~~DEFINE~~ GROUP]]</var> command.</p>		The $RDPROC function sequentially retrieves the lines of a procedure that is stored in a <var class="product">Model 204</var> file. The lines of the procedure can reside in a file or in a group (one or multiple procedure files). Multiple procedure files are searched in the order in which they appear in the <var>[[Managing file groups#CREATE GROUP command and the types of groups\|CREATE GROUP]]</var> command.</p>
	<p>		<p>
	You can also read temporary procedures, which do not reside in an input file. In this case, you specify the procedure number, for example, 0, -1, or -2, in place of the procedure name. </p>		You can also read temporary procedures, which do not reside in an input file. In this case, you specify the procedure number, for example, 0, -1, or -2, in place of the procedure name. </p>

JAL at 15:41, 12 June 2014

2014-06-12T15:41:11Z

@@ Line 2: / Line 2: @@
 <p>
-The $RDPROC function sequentially retrieves the lines of a [[SOUL]] procedure that is stored in a <var class="product">Model&nbsp;204</var> file. The lines of the SOUL procedure can reside in a file or in a group (one or multiple procedure files). Multiple procedure files are searched in the order in which they appear in the <var>[[DEFINE GROUP command|DEFINE GROUP]]</var> command.</p>
+The $RDPROC function sequentially retrieves the lines of a procedure that is stored in a <var class="product">Model&nbsp;204</var> file. The lines of the procedure can reside in a file or in a group (one or multiple procedure files). Multiple procedure files are searched in the order in which they appear in the <var>[[DEFINE GROUP command|DEFINE GROUP]]</var> command.</p>
 <p>
-You can also read temporary procedures, which do not necessarily reside in an input file. In this case, you specify the procedure number, for example, 0, -1, or -2, in place of the procedure name. </p>
+You can also read temporary procedures, which do not reside in an input file. In this case, you specify the procedure number, for example, 0, -1, or -2, in place of the procedure name. </p>
 <p>
 <var>$RDPROC</var> applies to local files only; it is not valid in remote context.</p>
@@ Line 43: / Line 43: @@
 The <var>$RDPROC</var> function uses 336 bytes of STBL and 8 bytes per <var>$RDPROC</var> level. You can nest <var>$RDPROC</var> up to the value of the MAXINCL parameter, plus one.</p>
-====Syntax for locating and locking a procedure====
+===Syntax for locating and locking a procedure===
 <p>The format for the <var>$RDPROC</var> function to locate and lock a procedure is:</p>
 <p class="syntax"><span class="term">ctlid</span> = $RDPROC('OPEN', <span class="term">fgname</span>, <span class="term">procname</span>)
@@ Line 63: / Line 63: @@
 <p class="note"><b>Note:</b> With $RDPROC, you can open up to six procedures concurrently. </p>
-====Syntax for reading a line from a procedure====
+====$RDPROC and temporary procedures====
 <p>
 The format for the <var>$RDPROC</var> function to read a line from a procedure is:</p>
@@ Line 76: / Line 102: @@
 </ul>
-====Syntax for closing and unlocking a procedure====
+===Syntax for closing and unlocking a procedure===
 <p>
 The format for the <var>$RDPROC</var> function to close and unlock a procedure is:</p>
@@ Line 89: / Line 115: @@
 </ul>
-====Syntax for reading a line end from a procedure====
+===Syntax for reading a line end from a procedure===
 <p>
 The format for the <var>$RDPROC</var> function to read a line-end character from a procedure is:</p>
@@ Line 195: / Line 221: @@
 </table>
-==Examples==
+==Example==
 <p class="code">BEGIN
 DECLARE %PROC   IS STRING LEN 50
@@ Line 246: / Line 272: @@
 END
 </p>
 [[Category:SOUL $functions]]

JAL at 20:11, 11 June 2014

2014-06-11T20:11:27Z

Show changes

Dme at 19:16, 11 June 2014

2014-06-11T19:16:47Z

← Older revision		Revision as of 19:16, 11 June 2014
Line 1:		Line 1:
	<p class="warn"><b>Note: </b>Many $functions have been deprecated in favor of Object Oriented methods. The OO equivalent for $RDPROC, recommended for manipulating procedure text, is <var>[[AppendOpenProcedure (Stringlist function)\|~~appendOpenProcedure~~]]</var>.</p>		<p class="warn"><b>Note: </b>Many $functions have been deprecated in favor of Object Oriented methods. The OO equivalent for $RDPROC, recommended for manipulating procedure text, is <var>[[AppendOpenProcedure (Stringlist function)\|AppendOpenProcedure]]</var>.</p>

	<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>		<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>

Dme at 19:15, 11 June 2014

2014-06-11T19:15:55Z

← Older revision		Revision as of 19:15, 11 June 2014
Line 1:		Line 1:
	<p class="warn"><b>Note: </b>Many $functions have been deprecated in favor of Object Oriented methods. The OO equivalent for $RDPROC, recommended for manipulating procedure text, is <var>[[~~appendOpenProcedure~~ (Stringlist function)\|appendOpenProcedure]]</var>.</p>		<p class="warn"><b>Note: </b>Many $functions have been deprecated in favor of Object Oriented methods. The OO equivalent for $RDPROC, recommended for manipulating procedure text, is <var>[[AppendOpenProcedure (Stringlist function)\|appendOpenProcedure]]</var>.</p>

	<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>		<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>

Mlarocca at 19:09, 11 June 2014

2014-06-11T19:09:48Z

← Older revision		Revision as of 19:09, 11 June 2014
Line 1:		Line 1:
			<p class="warn"><b>Note: </b>Many $functions have been deprecated in favor of Object Oriented methods. The OO equivalent for $RDPROC, recommended for manipulating procedure text, is <var>[[appendOpenProcedure (Stringlist function)\|appendOpenProcedure]]</var>.</p>

	<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>		<p>The $RDPROC function sequentially retrieves the lines of a User Language procedure that is stored in a <var class="product">Model 204</var> file. The lines of the User Language procedure can reside in a file or in a group. A group can contain a single procedure file or multiple procedure files. Multiple procedure files are searched in the order in which they appear in the DEFINE GROUP command.</p>
	<p>You can also read temporary procedures by specifying the procedure number, for example, 0, -1, or -2, in place of the procedure name. An input file is not required.</p>		<p>You can also read temporary procedures by specifying the procedure number, for example, 0, -1, or -2, in place of the procedure name. An input file is not required.</p>

Mlarocca at 17:56, 11 June 2014

2014-06-11T17:56:26Z

← Older revision		Revision as of 17:56, 11 June 2014
Line 52:		Line 52:
	<p>where:</p>		<p>where:</p>
	<ul>		<ul>
	<li>text is the next line of the procedure (null ~~if end~~-of-~~procedure~~ is reached). </li>		<li>text is the next line of the procedure. (text is set to null when End-Of-Procedure is reached; however, since procedure lines can be null, always check $STATUS to determine EOP)</li>
	</li>		</li>
	<li>ctlid is the integer ID of an internally maintained control ID that is assigned during OPEN processing.</li>		<li>ctlid is the integer ID of an internally maintained control ID that is assigned during OPEN processing.</li>