CREATE command: Temporary group - Revision history

JDamon: /* Temporary group parameters */

2025-01-23T00:42:45Z

Temporary group parameters

← Older revision		Revision as of 00:42, 23 January 2025
Line 110:		Line 110:

	<tr> <th><var>UPDTFILE</var></th>		<tr> <th><var>UPDTFILE</var></th>
	<td>Group's update file. </td> </tr>		<td>Group's update file for the STORE RECORD statement. </td> </tr>

	<tr> <th><var>PROCFILE</var></th>		<tr> <th><var>PROCFILE</var></th>

JDamon: /* Temporary group parameters */

2025-01-17T02:44:01Z

Temporary group parameters

← Older revision		Revision as of 02:44, 17 January 2025
Line 120:		Line 120:

	<ul>		<ul>
	<li>The <var>UPDTFILE</var> parameter defines the group's update file. When a SOUL <var>Store Record</var> statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If <var>UPDTFILE</var> is not specified, no update file is assigned and any attempt to issue a STORE RECORD statement will fail with:		<li>The <var>UPDTFILE</var> parameter defines the group's update file for the STORE RECORD statement. When a SOUL <var>Store Record</var> statement is encountered in group context, and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group-update file. If <var>UPDTFILE</var> is not specified, no update file is assigned and any attempt to issue a STORE RECORD statement will fail with:
	<p class="code">M204.0203: "Store" requires update file</p code>		<p class="code">M204.0203: "Store" requires update file</p code>
	In that case, use the "IN FILE" or 'IN MEMBER" clause with STORE RECORD:		In that case, use the "IN FILE" or 'IN MEMBER" clause with STORE RECORD:

JDamon: /* Temporary group parameters */

2025-01-17T01:30:08Z

Temporary group parameters

← Older revision		Revision as of 01:30, 17 January 2025
Line 120:		Line 120:

	<ul>		<ul>
	<li>The <var>UPDTFILE</var> parameter defines the group's update file. When a SOUL <var>Store Record</var> statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If <var>UPDTFILE</var> is not specified, no update file is assigned. The [[$Update]] function provides a convenient method for manipulating the update file. </li>		<li>The <var>UPDTFILE</var> parameter defines the group's update file. When a SOUL <var>Store Record</var> statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If <var>UPDTFILE</var> is not specified, no update file is assigned and any attempt to issue a STORE RECORD statement will fail with:
			<p class="code">M204.0203: "Store" requires update file</p code>
			In that case, use the "IN FILE" or 'IN MEMBER" clause with STORE RECORD:
			<p class="code">IN FILE filename STORE RECORD
			IN GROUP groupname MEMBER %membername STORE RECORD
			</p code>

			The [[$Update]] function also provides a convenient method for manipulating the update file. </li>

	<li>The <var>PROCFILE</var> parameter defines the group's procedure file. All procedure-related commands and the <var>INCLUDE</var> statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned.		<li>The <var>PROCFILE</var> parameter defines the group's procedure file. All procedure-related commands and the <var>INCLUDE</var> statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned.

JAL: add link

2017-10-20T19:00:12Z

add link

← Older revision		Revision as of 19:00, 20 October 2017
Line 131:		Line 131:

	<li>The <var>BLDGFT</var> parameter, if <code>YES</code> (the default), directs <var class="product">Model 204</var> to maintain certain information about the group in an internal field table. The option to specify depends upon how long you expect to use the group. If the group is only to satisfy a few short requests, specify <code>NO</code>.</li>		<li>The <var>BLDGFT</var> parameter, if <code>YES</code> (the default), directs <var class="product">Model 204</var> to maintain certain information about the group in an internal field table. The option to specify depends upon how long you expect to use the group. If the group is only to satisfy a few short requests, specify <code>NO</code>.</li>
			</ul>

			==See also==
			<ul>
			<li>[[CREATE command: Permanent group]] </li>
	</ul>		</ul>

	[[Category: User commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: minor formatting

2017-10-18T20:42:25Z

minor formatting

← Older revision		Revision as of 20:42, 18 October 2017
Line 27:		Line 27:
	The group name can contain any alphanumeric characters except those in the following table: </p>		The group name can contain any alphanumeric characters except those in the following table: </p>
	<table>		<table>
	<tr class="head"> <th>Character name </th> <th>Keyboard symbol</th> </tr>		<tr class="head"> <th>Character name </th>
			<th>Keyboard symbol</th> </tr>

	<tr> <th><var>Asterisk</var></th> <td>( * )</td> </tr>		<tr> <th><var>Asterisk</var></th>
			<td>( * )</td> </tr>

	<tr> <th><var>Equal sign </var></th> <td>( = )</td> </tr>		<tr> <th><var>Equal sign </var></th>
			<td>( = )</td> </tr>

	<tr> <th><var>Left parenthesis </var></th> <td>( ( )</td> </tr>		<tr> <th><var>Left parenthesis </var></th>
			<td>( ( )</td> </tr>

	<tr> <th><var>Minus sign</var></th> <td>( - )</td> </tr>		<tr> <th><var>Minus sign</var></th>
			<td>( - )</td> </tr>

	<tr> <th><var>Plus sign </var></th> <td>( + )</td> </tr>		<tr> <th><var>Plus sign </var></th>
			<td>( + )</td> </tr>

	<tr> <th><var>Right parenthesis </var></th> <td>( ) )</td> </tr>		<tr> <th><var>Right parenthesis </var></th>
			<td>( ) )</td> </tr>

	<tr> <th><var>Semicolon</var></th> <td>( ; )</td> </tr>		<tr> <th><var>Semicolon</var></th>
			<td>( ; )</td> </tr>

	<tr> <th><var>Single quote </var></th> <td>( ' ) </td> </tr>		<tr> <th><var>Single quote </var></th>
			<td>( ' ) </td> </tr>

	<tr> <th><var>Slash </var></th> <td>( / )</td> </tr>		<tr> <th><var>Slash </var></th>
			<td>( / )</td> </tr>

	<tr> <th><var>Space </var></th> <td></td> </tr>		<tr> <th><var>Space </var></th>
			<td></td> </tr>
	</table>		</table>
	</td></tr>		</td></tr>
Line 75:		Line 86:

	==Example==		==Example==
	<p class="code"><b>CREATE GROUP REGION FROM DELAWARE, -		<p class="code"><b>CREATE GROUP REGION FROM DELAWARE, MARYLAND, VIRGINIA </b>
	MARYLAND, VIRGINIA </b>
	<b></b>*** M204.0825: READING GROUP PARAMETERS		<b></b>*** M204.0825: READING GROUP PARAMETERS
	<b>PARAMETER PROCFILE = VIRGINIA		<b>PARAMETER PROCFILE = VIRGINIA
Line 100:		Line 110:

	<tr> <th><var>UPDTFILE</var></th>		<tr> <th><var>UPDTFILE</var></th>
	<td>Group's update file. </td> </tr>		<td>Group's update file. </td> </tr>

	<tr> <th><var>PROCFILE</var></th>		<tr> <th><var>PROCFILE</var></th>
	<td>Group's procedure file, or specifies that the group can contain multiple procedure files. </td> </tr>		<td>Group's procedure file, or specifies that the group can contain multiple procedure files. </td> </tr>

	<tr> <th><var>BLDGFT</var></th>		<tr> <th><var>BLDGFT</var></th>

JAL: link repair

2017-08-07T16:12:08Z

link repair

← Older revision		Revision as of 16:12, 7 August 2017
Line 110:		Line 110:

	<ul>		<ul>
	<li>The <var>[[UPDTFILE ~~parameter\|UPDTFILE]]~~</var> parameter defines the group's update file. When a SOUL <var>Store Record</var> statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If <var>UPDTFILE</var> is not specified, no update file is assigned. The [[$Update]] function provides a convenient method for manipulating the update file. </li>		<li>The <var>UPDTFILE</var> parameter defines the group's update file. When a SOUL <var>Store Record</var> statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If <var>UPDTFILE</var> is not specified, no update file is assigned. The [[$Update]] function provides a convenient method for manipulating the update file. </li>

	<li>The <var>[[PROCFILE ~~parameter\|PROCFILE]]~~</var> parameter defines the group's procedure file. All procedure-related commands and the <var>INCLUDE</var> statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned.		<li>The <var>PROCFILE</var> parameter defines the group's procedure file. All procedure-related commands and the <var>INCLUDE</var> statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned.
	<p>		<p>
	You can also use <var>PROCFILE</var> to specify multiple procedure files for a group. If a group contains multiple procedure files, then the <var>INCLUDE</var> statement searches the entire group for the procedure to be included. The search proceeds in order from the first file defined in the <var>CREATE GROUP</var> command to the last. </p>		You can also use <var>PROCFILE</var> to specify multiple procedure files for a group. If a group contains multiple procedure files, then the <var>INCLUDE</var> statement searches the entire group for the procedure to be included. The search proceeds in order from the first file defined in the <var>CREATE GROUP</var> command to the last. </p>
Line 120:		Line 120:
	For more information, see [[Application Subsystem development#Multiple procedure files\|multiple procedure files]]. </p></li>		For more information, see [[Application Subsystem development#Multiple procedure files\|multiple procedure files]]. </p></li>

	<li>The <var>[[BLDGFT ~~parameter\|BLDGFT]]~~</var> parameter, if <code>YES</code> (the default), directs <var class="product">Model 204</var> to maintain certain information about the group in an internal field table. The option to specify depends upon how long you expect to use the group. If the group is only to satisfy a few short requests, specify <code>NO</code>.</li>		<li>The <var>BLDGFT</var> parameter, if <code>YES</code> (the default), directs <var class="product">Model 204</var> to maintain certain information about the group in an internal field table. The option to specify depends upon how long you expect to use the group. If the group is only to satisfy a few short requests, specify <code>NO</code>.</li>
	</ul>		</ul>

	[[Category: User commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell at 16:14, 22 March 2017

2017-03-22T16:14:44Z

← Older revision		Revision as of 16:14, 22 March 2017
Line 123:		Line 123:
	</ul>		</ul>

	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: /* Temporary group parameters */ remove caption

2017-02-23T21:47:06Z

Temporary group parameters: remove caption

← Older revision		Revision as of 21:47, 23 February 2017
Line 96:		Line 96:
	The [[#Example\|CREATE GROUP REGION example]] above shows how group parameters can be specified. The <var class="product">Model 204</var> temporary group parameters that can be set in the <var>CREATE</var> command's parameter list are shown in the table below:		The [[#Example\|CREATE GROUP REGION example]] above shows how group parameters can be specified. The <var class="product">Model 204</var> temporary group parameters that can be set in the <var>CREATE</var> command's parameter list are shown in the table below:
	<table>		<table>
	~~<caption>Parameters for CREATE TEMP GROUP</caption>~~

	<tr class="head"> <th>Parameter</th>		<tr class="head"> <th>Parameter</th>
	<th>Defines...</th> </tr>		<th>Defines...</th> </tr>

JAL: misc cleanup

2017-02-23T21:39:03Z

misc cleanup

Show changes

Mlarocca at 15:36, 31 July 2014

2014-07-31T15:36:57Z

← Older revision		Revision as of 15:36, 31 July 2014
Line 103:		Line 103:
	<ul>		<ul>
	<li>		<li>
	The UPDTFILE parameter defines the group's update file. When a User Language STORE RECORD statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If UPDTFILE is not specified, no update file is assigned. The [[$~~UPDATE~~]] function provides a convenient method for manipulating the update file. </li>		The UPDTFILE parameter defines the group's update file. When a User Language STORE RECORD statement is encountered and <var class="product">Model 204</var> cannot determine a file context, the record is stored in the group update file. If UPDTFILE is not specified, no update file is assigned. The [[$Update]] function provides a convenient method for manipulating the update file. </li>

	<li>The PROCFILE parameter defines the group's procedure file. All procedure-related commands and the INCLUDE statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned. You can also use PROCFILE to specify multiple procedure files for a group. If a group contains multiple procedure files, then the INCLUDE statement searches the entire group for the procedure to be included. The search proceeds in order from the first file defined in the CREATE GROUP command to the last.		<li>The PROCFILE parameter defines the group's procedure file. All procedure-related commands and the INCLUDE statement operate on this file if no other file context is established. If this parameter is omitted, no procedure file is assigned. You can also use PROCFILE to specify multiple procedure files for a group. If a group contains multiple procedure files, then the INCLUDE statement searches the entire group for the procedure to be included. The search proceeds in order from the first file defined in the CREATE GROUP command to the last.