DML statements in Parallel Query Option/204: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
<p>Parallel Query Option/204 data manipulation language (DML) consists of most, but not all, User Language statements and conditions. This | ==Parallel Query Option/204 DML== | ||
<p>Listed below, in separate sections, are the Parallel Query Option/204 retrieval statements, retrieval conditions, and update statements. A discussion of IN clauses and field names in DML statements follows the listings.</p> | <p> | ||
Parallel Query Option/204 data manipulation language (DML) consists of most, but not all, User Language statements and conditions. This page lists the statements and conditions that comprise Parallel Query Option/204 DML, and discusses certain restrictions on the use of some User Language commands, statements, and functions.</p> | |||
<p> | |||
<p class="code">CLEAR LIST | Listed below, in separate sections, are the Parallel Query Option/204 retrieval statements, retrieval conditions, and update statements. A discussion of IN clauses and field names in DML statements follows the listings.</p> | ||
COMMIT RELEASE | |||
COUNT OCCURRENCES OF | ===DML statements and retrieval conditions=== | ||
COUNT RECORDS | |||
====Retrieval statements==== | |||
<p class="code">CLEAR LIST | |||
COMMIT RELEASE | |||
COUNT OCCURRENCES OF | |||
COUNT RECORDS | |||
DECLARE LIST | DECLARE LIST | ||
FIND RECORDS | FIND RECORDS | ||
FIND ALL RECORDS | FIND ALL RECORDS | ||
FIND ALL VALUES | FIND ALL VALUES | ||
FIND AND PRINT COUNT | FIND AND PRINT COUNT | ||
FOR EACH OCCURRENCE | FOR EACH OCCURRENCE | ||
FOR EACH RECORD | FOR EACH RECORD | ||
FOR EACH VALUE | FOR EACH VALUE | ||
FOR k RECORDS | FOR k RECORDS | ||
FOR k VALUES | FOR k VALUES | ||
FOR RECORD NUMBER | FOR RECORD NUMBER | ||
NOTE fieldname | NOTE fieldname | ||
OPEN | OPEN | ||
OPENC | OPENC | ||
PLACE RECORD ON LIST | PLACE RECORD ON LIST | ||
PLACE RECORDS ON LIST | PLACE RECORDS ON LIST | ||
PRINT ALL INFORMATION | PRINT ALL INFORMATION | ||
RELEASE ALL RECORDS | RELEASE ALL RECORDS | ||
RELEASE RECORDS | RELEASE RECORDS | ||
REMOVE RECORD FROM LIST | REMOVE RECORD FROM LIST | ||
REMOVE RECORDS FROM LIST | REMOVE RECORDS FROM LIST | ||
SORT RECORD KEYS | SORT RECORD KEYS | ||
SORT RECORDS | SORT RECORDS | ||
SORT VALUES | SORT VALUES | ||
</p> | </p> | ||
====Retrieval conditions==== | |||
<p class="code">FIND$ | <p class="code">FIND$ | ||
FILE$ | FILE$ | ||
| Line 40: | Line 46: | ||
POINT$ | POINT$ | ||
SFGE$ | SFGE$ | ||
SFL$ | SFL$ | ||
</p> | </p> | ||
====Update statements==== | |||
<p class="code">ADD | <p class="code">ADD | ||
BACKOUT | BACKOUT | ||
| Line 56: | Line 63: | ||
UPDATE RECORD | UPDATE RECORD | ||
</p> | </p> | ||
<p>A remote file specification (using either the AT clause or a file synonym) is syntactically valid in the IN FILE clause of supported DML statements in remote context. </p> | ===Using IN clauses=== | ||
<p>Also, you can use the following IN clause variations to refer to a remote file if you are in scattered group context: </p> | <p> | ||
<p class="code">IN GROUP groupname MEMBER | A remote file specification (using either the AT clause or a file synonym) is syntactically valid in the IN FILE clause of supported DML statements in remote context. </p> | ||
IN $CURFILE | <p> | ||
IN $UPDATE | Also, you can use the following IN clause variations to refer to a remote file if you are in scattered group context: </p> | ||
<p class="code">IN GROUP <i>groupname</i> MEMBER | |||
IN $CURFILE | |||
IN $UPDATE | |||
</p> | </p> | ||
<p>Fields in remote context can be used in the same ways as fields in local context including the VALUE IN phrase, which refers to a label on a FOR EACH RECORD IN ORDER statement. </p> | ===Using field names in expressions=== | ||
<p> | |||
<p>The <var class="product">Model 204</var> commands, User Language statements, and $functions that are not supported in remote context for Parallel Query Option/204 processing are listed in this section.</p> | Fields in remote context can be used in the same ways as fields in local context including the VALUE IN phrase, which refers to a label on a FOR EACH RECORD IN ORDER statement. </p> | ||
<p>Some of the <var class="product">Model 204</var> commands that specify a file name, or that operate on a default file or on a file specified in an IN clause, are not supported in remote context for Parallel Query Option/204 processing. </p> | ==Restricted commands and $functions== | ||
<p>The following commands cannot be used in reference to a remote file. See [[Files, groups, and reference context#Using Model 204 file and group commands|Using Model 204 file and group commands]] for a description of the commands that can be used to reference files in remote context:</p> | <p> | ||
<p>ASSIGN (specifying a procedure alias) | The <var class="product">Model 204</var> commands, User Language statements, and $functions that are not supported in remote context for Parallel Query Option/204 processing are listed in this section.</p> | ||
===Restricted Model 204 commands=== | |||
<p> | |||
Some of the <var class="product">Model 204</var> commands that specify a file name, or that operate on a default file or on a file specified in an IN clause, are not supported in remote context for Parallel Query Option/204 processing. </p> | |||
<p> | |||
The following commands cannot be used in reference to a remote file. See [[Files, groups, and reference context#Using Model 204 file and group commands|Using Model 204 file and group commands]] for a description of the commands that can be used to reference files in remote context:</p> | |||
<p class="code">ASSIGN (specifying a procedure alias) | |||
BROADCAST FILE | BROADCAST FILE | ||
CREATE FILE | CREATE FILE | ||
| Line 105: | Line 122: | ||
TRANSFORM | TRANSFORM | ||
Z</p> | Z</p> | ||
<p>The following $functions cannot be used in reference to a remote file:</p> | ===Restricted $functions=== | ||
<p>$LSTPROC | <p> | ||
The following $functions cannot be used in reference to a remote file:</p> | |||
<p class="code">$LSTPROC | |||
$RDPROC</p> | $RDPROC</p> | ||
<p>If either of these $functions is used in reference to a remote file, <var class="product">Model 204</var> displays an error message. </p> | <p> | ||
If either of these $functions is used in reference to a remote file, <var class="product">Model 204</var> displays an error message. </p> | |||
[[Category:SOUL]] | [[Category:SOUL]] | ||
Revision as of 20:22, 17 January 2014
Parallel Query Option/204 DML
Parallel Query Option/204 data manipulation language (DML) consists of most, but not all, User Language statements and conditions. This page lists the statements and conditions that comprise Parallel Query Option/204 DML, and discusses certain restrictions on the use of some User Language commands, statements, and functions.
Listed below, in separate sections, are the Parallel Query Option/204 retrieval statements, retrieval conditions, and update statements. A discussion of IN clauses and field names in DML statements follows the listings.
DML statements and retrieval conditions
Retrieval statements
CLEAR LIST COMMIT RELEASE COUNT OCCURRENCES OF COUNT RECORDS DECLARE LIST FIND RECORDS FIND ALL RECORDS FIND ALL VALUES FIND AND PRINT COUNT FOR EACH OCCURRENCE FOR EACH RECORD FOR EACH VALUE FOR k RECORDS FOR k VALUES FOR RECORD NUMBER NOTE fieldname OPEN OPENC PLACE RECORD ON LIST PLACE RECORDS ON LIST PRINT ALL INFORMATION RELEASE ALL RECORDS RELEASE RECORDS REMOVE RECORD FROM LIST REMOVE RECORDS FROM LIST SORT RECORD KEYS SORT RECORDS SORT VALUES
Retrieval conditions
FIND$ FILE$ LIST$ LOCATION$ POINT$ SFGE$ SFL$
Update statements
ADD BACKOUT CHANGE COMMIT DELETE DELETE EACH DELETE RECORD DELETE RECORDS FILE RECORDS INSERT STORE RECORD UPDATE RECORD
Using IN clauses
A remote file specification (using either the AT clause or a file synonym) is syntactically valid in the IN FILE clause of supported DML statements in remote context.
Also, you can use the following IN clause variations to refer to a remote file if you are in scattered group context:
IN GROUP groupname MEMBER IN $CURFILE IN $UPDATE
Using field names in expressions
Fields in remote context can be used in the same ways as fields in local context including the VALUE IN phrase, which refers to a label on a FOR EACH RECORD IN ORDER statement.
Restricted commands and $functions
The Model 204 commands, User Language statements, and $functions that are not supported in remote context for Parallel Query Option/204 processing are listed in this section.
Restricted Model 204 commands
Some of the Model 204 commands that specify a file name, or that operate on a default file or on a file specified in an IN clause, are not supported in remote context for Parallel Query Option/204 processing.
The following commands cannot be used in reference to a remote file. See Using Model 204 file and group commands for a description of the commands that can be used to reference files in remote context:
ASSIGN (specifying a procedure alias) BROADCAST FILE CREATE FILE DEASSIGN DECREASE DEFINE FIELD DELETE FIELD DELETE PROCEDURE DESECURE DESECURE PROCEDURE DISPLAY FILE DISPLAY LIST DISPLAY PROCEDURE DUMP EDIT ENQCTL FILELOAD FLOD INCLUDE INCREASE INITIALIZE PROCEDURE REDEFINE FIELD REGENERATE RENAME FIELD RENAME PROCEDURE REORGANIZE RESET (file parameters) RESTORE SECURE SECURE PROCEDURE TABLEB TABLEC TRANSFORM Z
Restricted $functions
The following $functions cannot be used in reference to a remote file:
$LSTPROC $RDPROC
If either of these $functions is used in reference to a remote file, Model 204 displays an error message.