OpenEdge Data Management: DataServer for Microsoft SQL Server

RDBMS Stored Procedure Details
3–20
Example 3–11 accesses the stored procedure pcust twice; procedure handles (through the
PROC–HANDLE function) identify the different results from your data source.
/* Procedure handles */
DEFINE VARIABLE handle1 AS INTEGER NO-UNDO.
DEFINE VARIABLE handle2 AS INTEGER NO-UNDO.
RUN STORED-PROCEDURE pcust handle1 = PROC-HANDLE (20, output 0, output 0).
RUN STORED-PROCEDURE pcust handle2 = PROC-HANDLE (20, output 0, output 0).
FOR EACH pcust_orders WHERE PROC-HANDLE = handle1:
DISPLAY pcust_orders.
END.
FOR EACH pcust_states WHERE PROC-HANDLE = handle1:
DISPLAY pcust_states.
END.
FOR EACH pcust_orders WHERE PROC-HANDLE = handle2:
DISPLAY pcust_orders.
END.
FOR EACH pcust_states WHERE PROC-HANDLE = handle2:
DISPLAY pcust_states.
END.
CLOSE STORED-PROC pcust WHERE PROC-HANDLE = handle1.
CLOSE STORED-PROC pcust WHERE PROC-HANDLE = handle2.
Example 3–11: Procedure handles
The results look the same as in the first two examples. However, because you are running a
stored procedure twice, ABL uses the procedure handles to identify the different instances. If
you have more than one stored procedure open simultaneously in your application, you must
explicitly define procedure handles for each.
Example 3–12 shows how to use standard OpenEdge syntax to join the results from a stored
procedure with other tables in the database.
/* Join with procedure results */
RUN STORED-PROC pcust (20, output 0, output 0).
FOR EACH pcust_orders, EACH orderline
WHERE pcust_orders.ordernum EQ orderline.ordernum:
DISPLAY orderline.ordernum orderline.itemnum.
END.
FOR EACH pcust_states:
DISPLAY pcust_states.
END.
CLOSE STORED-PROC pcust.
Example 3–12: Joining stored procedure results with other database tables
Example 3–12 joins the order information returned from the stored procedure with the
orderline information in the same database.