Commands Included in a Procedure
A Dialogue Manager procedure must reside in a Procedure
Library. For details on stored procedure libraries and stored procedure
execution order, see Introducing Stored Procedures.
With the EXEC command, a Dialogue Manager procedure is called
by the API function call EDARPC or by another Dialogue Manager procedure,
or issued by a client application. This is illustrated below.
In addition to Dialogue Manager commands (described later), include
the following in a procedure:
- SQL statements
allowed by the server platform.
- Server commands,
for example, CALLPGM, EXEC, and END. For details on CALLPGM and
EXEC when used to call a program, see Calling a Program as a Stored Procedure. This chapter discusses the use of EXEC to call
another Dialogue Manager procedure.
- Commands allowed
in a server profile, such as SET SQLENGINE and SET EXORDER. For
details on the profile and its allowable commands, see the Server Administration
for UNIX, Windows, OpenVMS, IBM i, and z/OS manual.
- Commands that
enable portions of a procedure to be executed on a target server. See The -REMOTE Commands for
details on the syntax and use of those commands. Also see the Server
Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual
for commands that connect to a target server, such as SQL EDA SET
SERVER.
- The ON TABLE
HOLD command, which holds an answer set in a temporary file on a
server. See ON TABLE HOLD for
details on syntax and use.
- The ON TABLE
PCHOLD command, which sends an answer set to a client application.
See ON TABLE PCHOLD for
details on the syntax and use.
- The CALLIMS
function.
- Platform-specific
commands (for example, DYNAM in MVS). For details, see Platform-Specific Commands and Features.