Files, groups, and reference context - Revision history

SteveS at 17:36, 3 February 2026

2026-02-03T17:36:31Z

← Older revision		Revision as of 17:36, 3 February 2026
Line 802:		Line 802:
	<p>		<p>
	Duplicate groups do not require additional server table space or network traffic.</p>		Duplicate groups do not require additional server table space or network traffic.</p>

			<p class="note"><b>Note: Because of a design limitation, a duplicate ad hoc Group may not be recognized as a duplicate if the Permanent and Temporary Open Group Count is already at NGROUP.</b> </p>

	===Clearing lists===		===Clearing lists===

ELowell: /* Two ways to open files and groups */

2019-11-11T17:56:21Z

Two ways to open files and groups

← Older revision		Revision as of 17:56, 11 November 2019
Line 273:		Line 273:
	OPEN/OPENC can be used as either a command or statement to open <var class="product">Model 204</var> files and groups. </p>		OPEN/OPENC can be used as either a command or statement to open <var class="product">Model 204</var> files and groups. </p>
	<ul>		<ul>
	<li>For a discussion of OPEN/OPENC as a statement, see [[#OPEN or OPENC statement\|OPEN or OPENC statement]]. For a ~~discussiong~~ of error handling, see [[#Error handling\|Handling errors in file/group open statements]].</li>		<li>For a discussion of OPEN/OPENC as a statement, see [[#OPEN or OPENC statement\|OPEN or OPENC statement]]. For a discussion of error handling, see [[#Error handling\|Handling errors in file/group open statements]].</li>
	</li>		</li>
	<li>For a discussion of OPEN/OPENC as a command, see the [[List of Model 204 commands]].</li>		<li>For a discussion of OPEN/OPENC as a command, see the [[List of Model 204 commands]].</li>

ELowell: /* Two ways to open files and groups */

2019-11-11T17:52:07Z

Two ways to open files and groups

← Older revision		Revision as of 17:52, 11 November 2019
Line 273:		Line 273:
	OPEN/OPENC can be used as either a command or statement to open <var class="product">Model 204</var> files and groups. </p>		OPEN/OPENC can be used as either a command or statement to open <var class="product">Model 204</var> files and groups. </p>
	<ul>		<ul>
	<li>For a discussion of OPEN/OPENC as a statement~~, including error handling~~, see [[#OPEN or OPENC statement\|OPEN or OPENC statement]]. </li>		<li>For a discussion of OPEN/OPENC as a statement, see [[#OPEN or OPENC statement\|OPEN or OPENC statement]]. For a discussiong of error handling, see [[#Error handling\|Handling errors in file/group open statements]].</li>
	</li>		</li>
	<li>For a discussion of OPEN/OPENC as a command, see the [[List of Model 204 commands]].</li>		<li>For a discussion of OPEN/OPENC as a command, see the [[List of Model 204 commands]].</li>
Line 286:		Line 286:
	<p>		<p>
	When used as a statement, OPEN/OPENC opens a file or group but does not allow retrievals or other references to fields or data records for the file or group in the same request. It does not allow updates to a file to be deferred. As a statement, OPEN/OPENC must appear within the request (between the BEGIN and END statements). </p>		When used as a statement, OPEN/OPENC opens a file or group but does not allow retrievals or other references to fields or data records for the file or group in the same request. It does not allow updates to a file to be deferred. As a statement, OPEN/OPENC must appear within the request (between the BEGIN and END statements). </p>

	===Opening multiple files or groups===		===Opening multiple files or groups===
	<p>		<p>

Dme: /* Handling errors in file/group open statements */

2019-11-10T08:53:08Z

Handling errors in file/group open statements

← Older revision		Revision as of 08:53, 10 November 2019
Line 492:		Line 492:
	===<b id="filGrpOpenErr"></b><b id="Error handling"></b>Handling errors in file/group open statements===		===<b id="filGrpOpenErr"></b><b id="Error handling"></b>Handling errors in file/group open statements===
	<p>		<p>
	Error conditions encountered during the processing of the OPEN or OPENC statement generate <var class="product">Model 204</var> error messages that are not displayed on the terminal. The request should check for errors after the execution of each OPEN or OPENC statement by using the $Status function. The text of the most recently issued error message can then be retrieved by the $~~Errmsg~~ function. </p>		Error conditions encountered during the processing of the OPEN or OPENC statement generate <var class="product">Model 204</var> error messages that are not displayed on the terminal. The request should check for errors after the execution of each OPEN or OPENC statement by using the $Status function. The text of the most recently issued error message can then be retrieved by the <var>[[$ErrMsg]]</var> function. </p>
	<p>		<p>
	The values that can be returned by the $Status function for the OPEN or OPENC statement are listed in the following table: </p>		The values that can be returned by the $Status function for the OPEN or OPENC statement are listed in the following table: </p>

Dme: /* Error handling */

2019-11-10T07:47:00Z

Error handling

← Older revision		Revision as of 07:47, 10 November 2019
Line 490:		Line 490:
	</ul>		</ul>

	===Error handling===		===<b id="filGrpOpenErr"></b><b id="Error handling"></b>Handling errors in file/group open statements===
	<p>		<p>
	Error conditions encountered during the processing of the OPEN or OPENC statement generate <var class="product">Model 204</var> error messages that are not displayed on the terminal. The request should check for errors after the execution of each OPEN or OPENC statement by using the $Status function. The text of the most recently issued error message can then be retrieved by the $Errmsg function. </p>		Error conditions encountered during the processing of the OPEN or OPENC statement generate <var class="product">Model 204</var> error messages that are not displayed on the terminal. The request should check for errors after the execution of each OPEN or OPENC statement by using the $Status function. The text of the most recently issued error message can then be retrieved by the $Errmsg function. </p>

JAL: minor formatting

2018-08-08T18:29:38Z

minor formatting

← Older revision		Revision as of 18:29, 8 August 2018
Line 1,538:		Line 1,538:
	<p>		<p>
	Though updates like CHANGE lock a record, they alone do not prevent inconsistencies between the client's view of the record and the actual state of the record on the server. For unlocked record processing, you need to use <var>For Record Number</var>. </p>		Though updates like CHANGE lock a record, they alone do not prevent inconsistencies between the client's view of the record and the actual state of the record on the server. For unlocked record processing, you need to use <var>For Record Number</var>. </p>
	<p class="note"><b>Note:</b> Always lock a record before updating it. If an unlocked record set or list is being processed, use the <var>For Record Number</var> statement to lock the record, as shown below: </p>		<blockquote class="note">
			<p><b>Note:</b> Always lock a record before updating it. If an unlocked record set or list is being processed, use the <var>For Record Number</var> statement to lock the record, as shown below: </p>
	<p class="code">%X = $CURREC		<p class="code">%X = $CURREC
	FOR RECORD NUMBER %X		FOR RECORD NUMBER %X </p>
	</p>		</blockquote>
	<p>		<p>
	<var>For Record Number</var> locks, copies, and sends the record to the client when the <var>For Record Number</var> statement is executed. Using <var>For Record Number In <i>label</i></var> is not sufficient, as explained in [[#Using the For Record Number statement\|Using the For Record Number statement]]. </p>		<var>For Record Number</var> locks, copies, and sends the record to the client when the <var>For Record Number</var> statement is executed. Using <var>For Record Number In <i>label</i></var> is not sufficient, as explained in [[#Using the For Record Number statement\|Using the For Record Number statement]]. </p>
Line 1,678:		Line 1,679:
	==Using $functions with remote files==		==Using $functions with remote files==
	<p>		<p>
	Except for the following functions, all file-related $functions that applied to local files or groups ~~now~~ apply to remote files and scattered groups as well. </p>		Except for the following functions, all file-related $functions that applied to local files or groups apply to remote files and scattered groups as well. </p>
	<p class="code">$LSTPROC		<p class="code">$LSTPROC
	$RDPROC		$RDPROC
Line 1,701:		Line 1,702:
	===Using $CURFILE, $RLCFILE, $UPDATE, and $UPDFILE===		===Using $CURFILE, $RLCFILE, $UPDATE, and $UPDFILE===
	<p>		<p>
	The output of the $CURFILE, $RLCFILE, $UPDATE, and $UPDFILE functions issued in remote context is the remote file specification (filename AT location). Each of these functions returns the string:</p>		The output of the $CURFILE, $RLCFILE, $UPDATE, and $UPDFILE functions issued in remote context is the remote file specification (<var class="term">filename</var> At <var class="term">location</var>). Each of these functions returns the string:</p>
	<p class="syntax">filename AT location		<p class="syntax"><span class="term">filename</span> At <span class="term">location</span>
	</p>		</p>
	Where:		Where:
	<p>		<p>
	location is a name for the node where the remote file resides.</p>		<var class="term">location</var> is a name for the node where the remote file resides. </p>
	<p>		<p>
	You can use $SUBSTR to extract the name or the location. </p>		You can use $SUBSTR to extract the name or the location. </p>
Line 1,717:		Line 1,718:
	<p>		<p>
	The $ITSOPEN function indicates whether the current file or group is open. Its format is:</p>		The $ITSOPEN function indicates whether the current file or group is open. Its format is:</p>
	<p class="~~code~~">$ITSOPEN(name)		<p class="syntax">$ITSOPEN(<span class="term">name</span>)
	</p>		</p>
	<p>		<p>
	where name is a %variable or literal character string representing a file name, file synonym, or group name. This argument string can include the keywords AT, FILE, GROUP, PERM, or TEMP.</p>		where <var class="term">name</var> is a %variable or literal character string representing a file name, file synonym, or group name. This argument string can include the keywords AT, FILE, GROUP, PERM, or TEMP.</p>
	<p>		<p>
	$ITSOPEN can be issued in any context. It returns 1 if the file or group is open; it returns 0 if the file or group is closed. </p>		$ITSOPEN can be issued in any context. It returns 1 if the file or group is open; it returns 0 if the file or group is closed. </p>
Line 1,727:		Line 1,728:
	<p>		<p>
	The $ITSREMOTE function indicates whether the current file or group is remote or scattered. Its format is:</p>		The $ITSREMOTE function indicates whether the current file or group is remote or scattered. Its format is:</p>
	<p class="code">$ITSREMOTE(name)		<p class="code">$ITSREMOTE(<span class="term">name</span>)
	</p>		</p>
	<p>		<p>
	where name is a %variable or literal character string representing a file name, file synonym, or group name. This argument string can include the keywords AT, FILE, GROUP, PERM, or TEMP.</p>		where <var class="term">name</var> is a %variable or literal character string representing a file name, file synonym, or group name. This argument string can include the keywords AT, FILE, GROUP, PERM, or TEMP.</p>
	<p>		<p>
	$ITSREMOTE can be issued in any context. It returns 1 if the context is remote file or scattered group; it returns 0 if the context is local. </p>		$ITSREMOTE can be issued in any context. It returns 1 if the context is remote file or scattered group; it returns 0 if the context is local. </p>
Line 1,758:		Line 1,759:
	</tr>		</tr>

	<tr><td>		<tr><td> <p class="codeInTable">$GRMLOC(<i>index</i> [,<i>groupname</i>]) </p></td>
	<p class="codeInTable">$GRMLOC(index [,groupname])
	</p></td>
	<td><p>Location of the missing (unavailable) group member identified by the index parameter. </p></td>		<td><p>Location of the missing (unavailable) group member identified by the index parameter. </p></td>
	</tr>		</tr>

	<tr><td>		<tr><td> <p class="codeInTable">$GRMNAME(index [,groupname])
	<p class="codeInTable">$GRMNAME(index [,groupname])
	</p></td>		</p></td>
	<td><p>Name of the missing (unavailable) group member represented by the index parameter. </p></td>		<td><p>Name of the missing (unavailable) group member represented by the index parameter. </p></td>
	</tr>		</tr>

	<tr><td>		<tr><td> <p class="codeInTable">$GRNLEFT[(groupname)]
	<p class="codeInTable">$GRNLEFT[(groupname)]
	</p></td>		</p></td>
	<td><p>Number of remaining available optional group members that can fail before the MAXFAIL parameter value (CREATE GROUP command) is exceeded. (MAXFAIL specifies the maximum number of optional members that might be unavailable.) </p></td>		<td><p>Number of remaining available optional group members that can fail before the MAXFAIL parameter value (CREATE GROUP command) is exceeded. (MAXFAIL specifies the maximum number of optional members that might be unavailable.) </p></td>
	</tr>		</tr>

	<tr><td>		<tr><td> <p class="codeInTable">$GRNMISS[(groupname)]
	<p class="codeInTable">$GRNMISS[(groupname)]
	</p></td>		</p></td>
	<td><p>Number of optional group members that are unavailable to the request. </p></td>		<td><p>Number of optional group members that are unavailable to the request. </p></td>
Line 1,794:		Line 1,790:
	<th>Returns...</th>		<th>Returns...</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>[[$MisGrup]]</td>		<td>[[$MisGrup]]</td>
	<td>String containing the name of the group, if the error that invoked the ON unit occurred in group context. Otherwise, it returns the null string. </td>		<td>String containing the name of the group, if the error that invoked the ON unit occurred in group context. Otherwise, it returns the null string. </td>
	</tr>		</tr>

	<tr>		<tr>
	<td>$MisLoc(index) </td>		<td>$MisLoc(index) </td>
	<td>String containing the location of the unavailable file indicated by the index parameter. </td>		<td>String containing the location of the unavailable file indicated by the index parameter. </td>
	</tr>		</tr>

	<tr>		<tr>
	<td>$MisName(index) </td>		<td>$MisName(index) </td>
	<td>Name of the unavailable file identified by the index parameter. </td>		<td>Name of the unavailable file identified by the index parameter. </td>
	</tr>		</tr>

	<tr>		<tr>
	<td>[[$MisNum]]</td>		<td>[[$MisNum]]</td>
	<td>Number of files in the group that are newly unavailable (that have become unavailable since the last time the ON MISSING unit was invoked). </td>		<td>Number of files in the group that are newly unavailable (that have become unavailable since the last time the ON MISSING unit was invoked). </td>
	</tr>		</tr>

	<tr>		<tr>
	<td>[[$MisStmt]]</td>		<td>[[$MisStmt]]</td>

JAL: mixed case for For Each Record

2018-04-27T18:12:31Z

mixed case for For Each Record

Show changes

JAL: mixed case for For Record Number

2018-04-26T22:00:22Z

mixed case for For Record Number

Show changes

ELowell: /* Using LOCATION$ */

2017-12-06T22:45:50Z

Using LOCATION$

← Older revision		Revision as of 22:45, 6 December 2017
Line 1,496:		Line 1,496:
	The location referred to by LOCATION$ is the location name used in file synonyms and remote file specifications —		The location referred to by LOCATION$ is the location name used in file synonyms and remote file specifications —
	the symbolic name specified in the DESTINATION parameter of a client DEFINE PROCESS command		the symbolic name specified in the DESTINATION parameter of a client DEFINE PROCESS command
	(described in ~~the~~		(described in [[PQO: Defining a PQO network]]). </p>
	~~<var class="book">Rocket Parallel Query Option/204 User's Guide</var>~~). </p>
	<p>		<p>
	Valid LOCATION$ argument formats are: </p>		Valid LOCATION$ argument formats are: </p>
Line 1,511:		Line 1,510:
	<p>		<p>
	If an optional member of a scattered group is unavailable, no records are found for that file and processing continues. </p>		If an optional member of a scattered group is unavailable, no records are found for that file and processing continues. </p>

	==Using update statements with remote files==		==Using update statements with remote files==
	<p>		<p>

ELowell: /* Example */

2017-12-06T22:41:51Z

Example

← Older revision		Revision as of 22:41, 6 December 2017
Line 1,166:		Line 1,166:
	The server sends records from the found set to the user's node, one page of records at a time. Only records in the found set are transmitted.</p>		The server sends records from the found set to the user's node, one page of records at a time. Only records in the found set are transmitted.</p>
	<p>		<p>
	~~[[#Referencing remote files in requests\|Referencing remote files in requests]]~~ shows remote file references using a file synonym. As an alternative, if no DEFINE FILE command is issued on the client system, you can reference the remote file using a remote file specification (AT clause). </p>		The previous example shows remote file references using a file synonym. As an alternative, if no DEFINE FILE command is issued on the client system, you can reference the remote file using a remote file specification (AT clause). </p>
	<p>		<p>
	For example, instead of OPEN CARS, you use:</p>		For example, instead of OPEN CARS, you use:</p>
Line 1,176:		Line 1,176:
	</p>		</p>
	<p>		<p>
	See ~~the <var class="book">Rocket Parallel Query Option/204 User's Guide</var>~~ for additional information.</p>		See [[PQO: Remote files and scattered groups]] for additional information.</p>

	===Request continuation is not supported===		===Request continuation is not supported===
	<p>		<p>