SQL/MX 3.x Query Guide (H06.22+, J06.11+)

SQL/MX Operators
HP NonStop SQL/MX Query Guide—640323-001
7-7
CURSOR_DELETE Operator
The following is an example of the CALL operator:
create procedure u300populateA (
in table_name char(20)
)
external name 'TEST300.populateA' language java parameter style
java
external path 'W:/regress/udr' modifies sql data;
prepare TestQuery36 from
call u300populateA('customer');
DESCRIPTION
fragment_id ............ 0
parent_frag ............ (none)
fragment_type .......... master
parameter_modes ........ I
routine_name ........... CAT.SCH.U300POPULATEA
routine_label .......... \DMR11.$DATA04.ZSDJG12X.WF32X300
sql_access_mode ........ MODIFIES SQL DATA
external_name .......... populateA
external_path .......... ./
external_file .......... TEST300
signature .............. (Ljava/lang/String;)V
language ............... Java
runtime_options ........ OFF
runtime_option_delimite ' '
max_result_sets ........ 0
input_values ........... cast('customer' AS CHAR(20) CHARACTER
SET ISO88591)
CURSOR_DELETE Operator
DAM Unique Group
The CURSOR_DELETE operator describes a portion of an execution plan that works
on one row only. The CURSOR_DELETE operation is performed by first retrieving
rows from the table and then deleting each row that is required. This operation differs
from SUBSET_DELETE, in which the read and delete are performed in a combined
operation.
The CURSOR_DELETE operator has no child nodes. The description field for this
operator contains:
Token Followed by ... Data Type
fragment_id A sequential number assigned to the fragment.
0 is always the master executor and 1 is
reserved for the EXPLAIN plan. Numbers 2 to n
will be ESP or DAM fragments.
integer
parent_frag The fragment_id for the parent of the current
fragment. The value is (none) for the master
executor.
integer