DML statements in Parallel Query Option/204: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
Line 9: Line 9:
   
   
====Retrieval statements====
====Retrieval statements====
<p class="code">CLEAR LIST
<p class="code">[[Lists#Clearing a list|CLEAR LIST]]
COMMIT RELEASE
COMMIT RELEASE
COUNT OCCURRENCES OF
COUNT OCCURRENCES OF
Line 38: Line 38:
SORT VALUES
SORT VALUES
</p>
</p>
 
====Retrieval conditions====
====Retrieval conditions====
<p class="code">FIND$
<p class="code">FIND$

Revision as of 23:33, 19 February 2016

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.