OpenEdge Data Management: DataServer for Microsoft SQL Server

Retrieving return codes
Interfacing with RDBMS stored procedures
You can create a stored procedure that provides return code information. For example,
it might indicate whether the stored procedure was successful or whether it
encountered an error condition.
Example 4 shows how ABL code runs the stored procedure pcust. It uses the
PROC–STATUS function and the CLOSE STORED–PROC statement to retrieve the return
code and assign the value to the variable stat. The meaning of this return code is
defined by the underlying data source.
/* Return status */
DEFINE VARIABLE handle1 AS INTEGER NO-UNDO.
DEFINE VARIABLE stat AS INTEGER NO-UNDO.
RUN STORED-PROCEDURE pcust handle1 = PROC-HANDLE (20, output 0, output 0).
CLOSE STORED-PROC pcust stat = PROC-STATUS WHERE PROC-HANDLE = handle1.
IF stat = 0 THEN
DISPLAY “procedure succeeded”.
Example 4: Return status example
Retrieving output parameter values
When you call a stored procedure, you can specify the ordered list of positional
parameters or you can name them individually. To retrieve output parameter values
from a stored procedure, request them with the keyword OUTPUT or INPUT–OUTPUT
when you execute the procedure. When you run a stored procedure in a DataServer
application, the parameters are supplied and passed using OpenEdge data types.
Example 5, an ABL procedure, uses the second option for passing parameters—it
passes them by name with the PARAM option.
/* Parameters by name */
RUN STORED-PROC pcust (PARAM num = 20, OUTPUT PARAM states = 0,
OUTPUT PARAM orders = 0).
CLOSE STORED-PROC pcust.
DISPLAY pcust.orders pcust.states.
Example 5: Passing parameters by name using the PARAM option
When you use PARAM to specify parameter names, you do not have to specify all
parameters for the stored procedure. Instead, you can include only those parameters
you want to use, in any order you choose. If the stored procedure names a default value
for the parameter, you do not have to name that parameter at run time. However, you
must explicitly name parameters that do not have defaults or name them when you
want to pass values that are different from the default.
OpenEdge Data Management: DataServer for Microsoft SQL Server 135