SQL/MX Comparison Guide for SQL/MP Users

Embedded SQL
HP NonStop SQL/MX Comparison Guide for SQL/MP Users—523735-003
4-5
EXECUTE Statement
EXECUTE Statement
In NonStop SQL/MX, input data is supplied by the USING clause that specifies either a
list of host variables or an SQL descriptor area. Output data is provided by the INTO
clause that specifies either a list of host variables or an SQL descriptor area. See
Descriptor Area.
NonStop SQL/MP implements the RETURNING clause for output data. NonStop
SQL/MX does not provide a RETURNING clause.
In both NonStop SQL/MX and NonStop SQL/MP, if you perform a PREPARE and an
EXECUTE of an SQL UPDATE, INSERT or DELETE statement on a non-audited table,
NonStop SQL/MX does not close the table and will not release record and table locks.
You can use FUP LISTLOCKS to check if locks are kept on that table by your MXCI
session after completion of the EXECUTE statement, then manually execute an
FREE RESOURCES No
INCLUDE STRUCTURES No See Descriptor Area
, Diagnostics Area,
Statistics Area
.
INCLUDE SQLCA No See Diagnostics Area
.
INCLUDE SQLDA No See Descriptor Area
.
INCLUDE SQLSA No See Statistics Area
.
INSERT Changed No RETURNING clause in NonStop
SQL/MX. See INSERT Statement
on
page 3-14.
INVOKE Changed No FORMAT clause in NonStop SQL/MX.
See INVOKE Directive
.
OPEN Changed NonStop SQL/MX uses an SQL descriptor
area, as defined by ANSI SQL:1999. See
Descriptor Area
.
Positioned DELETE Yes
Positioned UPDATE Changed NonStop SQL/MX allows this statement to be
dynamic.
PREPARE Yes SQL/MX FROM clause does not allow
quoted strings.
RELEASE No
SELECT INTO Changed See SELECT Statement
.
WHENEVER Changed Usage changes. See WHENEVER
Declarative.
Positioned DELETE Yes
Table 4-1. Embedded SQL Statements
SQL/MP Embedded SQL
Statements and Directives
Implemented
in NonStop
SQL/MX? Comments