OPENC command - Revision history

ELowell: /* Syntax */

2017-04-14T23:14:41Z

Syntax

← Older revision		Revision as of 23:14, 14 April 2017
Line 37:		Line 37:
	<td>The name (one to eight characters in the form TAPE<var class="term">xxxx</var>) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.		<td>The name (one to eight characters in the form TAPE<var class="term">xxxx</var>) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.
	<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>		<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>
	<p>For information about opening remote files in deferred update mode, see ~~the <var class="book">Rocket Parallel Query Option/204 User's Guide~~.~~</var>~~ </p>		<p>For information about opening remote files in deferred update mode, see [[PQO: Remote files and scattered groups]].</p>
	</td>		</td>
	</tr>		</tr>

ELowell at 16:28, 22 March 2017

2017-03-22T16:28:13Z

← Older revision		Revision as of 16:28, 22 March 2017
Line 66:		Line 66:
	<p>Like the OPEN command, you can use OPENC to open a file or a permanent or temporary group. Unlike OPEN, however, OPENC preserves the previous default file or group.</p>		<p>Like the OPEN command, you can use OPENC to open a file or a permanent or temporary group. Unlike OPEN, however, OPENC preserves the previous default file or group.</p>
	<p>The syntax and use of the OPENC command is identical to that described for the OPEN command.</p>		<p>The syntax and use of the OPENC command is identical to that described for the OPEN command.</p>
	[[Category: ~~General user~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Syntax */

2013-06-27T19:13:16Z

Syntax

← Older revision		Revision as of 19:13, 27 June 2013
Line 35:		Line 35:
	<tr>		<tr>
	<th><var class="term">defupdt1</var></th>		<th><var class="term">defupdt1</var></th>
	<td>The name (one to eight characters in the form ~~TAPExxxx~~) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.		<td>The name (one to eight characters in the form TAPE<var class="term">xxxx</var>) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.
	<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>		<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>
	<p>For information about opening remote files in deferred update mode, see the <var class="book">Rocket Parallel Query Option/204 User's Guide.</var> </p>		<p>For information about opening remote files in deferred update mode, see the <var class="book">Rocket Parallel Query Option/204 User's Guide.</var> </p>
Line 43:		Line 43:
	<tr>		<tr>
	<th><var class="term">defupdt2</var></th>		<th><var class="term">defupdt2</var></th>
	<td>The name (one to eight characters in the form ~~TAPExxxx~~) of the variable-length deferred update data set. If you specify this option, deferred updates to ORDERED fields are written to this data set.		<td>The name (one to eight characters in the form TAPE<var class="term">xxxx</var>) of the variable-length deferred update data set. If you specify this option, deferred updates to ORDERED fields are written to this data set.
	<p>All index updates are written to <var class="term">defupdt2</var> if <var class="term">defupdt1</var> is not specified. If <var class="term">defupdt2</var> is not specified, updates to ORDERED fields are not deferred.</p>		<p>All index updates are written to <var class="term">defupdt2</var> if <var class="term">defupdt1</var> is not specified. If <var class="term">defupdt2</var> is not specified, updates to ORDERED fields are not deferred.</p>
	</td>		</td>

ELowell: /* Syntax */

2013-06-27T19:10:39Z

Syntax

← Older revision		Revision as of 19:10, 27 June 2013
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax">OPENC {[FILE] filename [AT location]		<p class="syntax">OPENC {[FILE] filename [AT <var class="term">location</var>]
	[[,defupdt1] [,defupdt2]]		[[,<var class="term">defupdt1</var>] [,<var class="term">defupdt2</var>]]
	\| [PERM \| TEMP] [GROUP] groupname}		\| [PERM \| TEMP] [GROUP] <var class="term">groupname</var>}
	</p>		</p>

	<b>Where:</b>		<b>Where:</b>
			<table>
			<tr>
			<th><var class="term">filename</var></th>
			<td>The name of the <var class="product">Model 204</var> file to be opened.</td>
			</tr>

			<tr>
			<th>location</th>
			<td>
	<ul>		<ul>
	<li>		<li>
	~~<p>filename is~~ the name of the ~~<var class~~=~~"product">Model 204</var>~~ file ~~to be opened~~.~~</p>~~		For Parallel Query Option/204 files, the symbolic name (as many as eight characters) that refers to the location of the node on which the remote file resides. An unquoted equal sign (=) specifies that the file is local.
	</li>		</li>

	<li>		<li>
	~~<p>location</p>~~		If remote, must match a symbolic destination name specified in the DESTINATION parameter of the relevant local client DEFINE PROCESS command.
	~~<ul>~~
	~~<li>~~
	<p>For Parallel Query Option/204 files, is the symbolic name (as many as eight characters) that refers to the location of the node on which the remote file resides. An unquoted equal sign (=) specifies that the file is local.</p>
	~~</li>~~

	~~<li>~~
	~~<p>~~If remote, must match a symbolic destination name specified in the DESTINATION parameter of the relevant local client DEFINE PROCESS command.~~</p>~~
	~~</li>~~
	~~</ul>~~
	~~</li>~~

	~~<li>~~
	<p>defupdt1 is the name (one to eight characters in the form TAPExxxx) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.</p>
	</li>		</li>
	</ul>		</ul>
			</td>
			</tr>

			<tr>
			<th><var class="term">defupdt1</var></th>
			<td>The name (one to eight characters in the form TAPExxxx) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.
	<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>		<p>Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. </p>
	<p>For information about opening remote files in deferred update mode, see the <var>Parallel Query Option/204 User's Guide.</var> </p>		<p>For information about opening remote files in deferred update mode, see the <var class="book">Rocket Parallel Query Option/204 User's Guide.</var> </p>
	<~~table~~>		</td>
			</tr>

	<tr>		<tr>
	<th>defupdt2</th>		<th><var class="term">defupdt2</var></th>
	<td> ~~is the~~ name (one to eight characters in the form TAPExxxx) of the variable-length deferred update data set. If you specify this option, deferred updates to ORDERED fields are written to this data set.		<td>The name (one to eight characters in the form TAPExxxx) of the variable-length deferred update data set. If you specify this option, deferred updates to ORDERED fields are written to this data set.
	<p>All index updates are written to defupdt2 if defupdt1 is not specified. If defupdt2 is not specified, updates to ORDERED fields are not deferred.</p>		<p>All index updates are written to <var class="term">defupdt2</var> if <var class="term">defupdt1</var> is not specified. If <var class="term">defupdt2</var> is not specified, updates to ORDERED fields are not deferred.</p>
	</td>		</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>groupname</th>		<th>groupname</th>
	<td> ~~is the~~ name of the <var class="product">Model 204</var> file group to be opened.</td>		<td>The name of the <var class="product">Model 204</var> file group to be opened.</td>
	</tr>		</tr>

Line 54:		Line 57:
	<p>A comma is required if a deferred update data set is specified. If the comma is omitted, the data set is ignored and no message is generated.</p>		<p>A comma is required if a deferred update data set is specified. If the comma is omitted, the data set is ignored and no message is generated.</p>
	<p>If neither FILE nor GROUP is specified, <var class="product">Model 204</var> searches for a temporary group, followed by a permanent group, followed by a file. If neither TEMP nor PERM is specified, <var class="product">Model 204</var> assumes a temporary group.</p>		<p>If neither FILE nor GROUP is specified, <var class="product">Model 204</var> searches for a temporary group, followed by a permanent group, followed by a file. If neither TEMP nor PERM is specified, <var class="product">Model 204</var> assumes a temporary group.</p>

	==Example==		==Example==
	<p class="code">OPENC FILE CENSUS		<p class="code">OPENC FILE CENSUS

Alex: Automatically generated page update

2013-02-28T01:05:17Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>Any user
<dt>Function
<dd>Opens a <var class="product">Model 204</var> file or a temporary or permanent group, preserving the previous default file or group
</dl>
==Syntax==
OPENC {[FILE] filename [AT location]
[[,defupdt1] [,defupdt2]]
| [PERM | TEMP] [GROUP] groupname}


Where:
<ul>
<li>
filename is the name of the <var class="product">Model 204</var> file to be opened.
</li>

<li>
location
<ul>
<li>
For Parallel Query Option/204 files, is the symbolic name (as many as eight characters) that refers to the location of the node on which the remote file resides. An unquoted equal sign (=) specifies that the file is local.
</li>

<li>
If remote, must match a symbolic destination name specified in the DESTINATION parameter of the relevant local client DEFINE PROCESS command.
</li>
</ul>
</li>

<li>
defupdt1 is the name (one to eight characters in the form TAPExxxx) of the fixed-length deferred update data set. If you specify this option, deferred updates to the hashed index (KEY and NUMERIC RANGE fields) are written to this data set.
</li>
</ul>
Deferred updates are updates to the <var class="product">Model 204</var> file that are saved and applied all at the same time. 
For information about opening remote files in deferred update mode, see the <var>Parallel Query Option/204 User's Guide.</var> 
<table>
<tr>
<th>defupdt2</th>
<td> is the name (one to eight characters in the form TAPExxxx) of the variable-length deferred update data set. If you specify this option, deferred updates to ORDERED fields are written to this data set.
All index updates are written to defupdt2 if defupdt1 is not specified. If defupdt2 is not specified, updates to ORDERED fields are not deferred.
</td>
</tr>

<tr>
<th>groupname</th>
<td> is the name of the <var class="product">Model 204</var> file group to be opened.</td>
</tr>

</table>
===Syntax notes===
A comma is required if a deferred update data set is specified. If the comma is omitted, the data set is ignored and no message is generated.
If neither FILE nor GROUP is specified, <var class="product">Model 204</var> searches for a temporary group, followed by a permanent group, followed by a file. If neither TEMP nor PERM is specified, <var class="product">Model 204</var> assumes a temporary group.
==Example==
OPENC FILE CENSUS
OPENC WEEK
OPENC PERM GROUP GDATA

==Usage notes==
Like the OPEN command, you can use OPENC to open a file or a permanent or temporary group. Unlike OPEN, however, OPENC preserves the previous default file or group.
The syntax and use of the OPENC command is identical to that described for the OPEN command.
[[Category: General user commands]]
[[Category:Commands]]