EDT makes it possible to store sequences of statements in work files, cataloged files or library elements and execute these as required. Alongside statements, records may also be present which are then inserted in the current work file at the relevant current line number. Such sequences of statements and records are referred to under the umbrella term of EDT procedure.
EDT procedures are subdivided into @DO procedures and @INPUT procedures depending on their storage location and the statement used to start them.
@DO procedures
are stored in an EDT work file (
1..22),can only be executed as a whole,
permit the passing of parameters, nesting, (conditional) branches and loops and
are started with the EDT statement @DO.
@INPUT -procedures
are stored in a file,
can be executed as a whole or partially,
do not permit the passing of parameters, nesting, branches or loops,
can be started as an EDT start procedure when EDT starts or
can be started with the EDT statement @INPUT.
The following sections start by explaining the concepts which apply to all procedure types. These form the basic rules for the creation and execution of EDT procedures. This is followed by a discussion of the possibilities offered by the @INPUT procedures and by integrating EDT procedures in BS2000 system procedures. The EDT start procedure is explained as a special type of @INPUT procedure. Finally, the language tools which can only be used in combination with @DO procedures are described, namely branches, loops and parameters.