The following diagrams illustrate the syntax for initiating DASDL compilations through WFL:

DASDL Compilation through WFL

── <compilation statement>; ─┬───────────────────────────────┬─────────►
                             └─<compiler task equation list>─┘
►─┬───────────────────────────────┬────────────────────────────────────┤
  └─<compiler data specification>─┘

<compilation statement>

── COMPILE ─┬─────┬─<database name>── WITH DASDL ──────────────────────►
            └─ * ─┘

►─┬────────────────────┬─┬─────────────────┬─┬──────────────┬──────────┤
  └─ ON <family name> ─┘ └─ [ <task id> ] ─┘ ├─ GO ─────────┤
                                             ├─ LIBRARY ────┤
                                             ├─ LIBRARY GO ─┤
                                             └─ SYNTAX ─────┘

<compiler task equation list>

  ┌◄───────────────────────────────────────────────┐
──┴─ COMPILER ─┬─<task attribute assignment>─┬─ ; ─┴───────────────────┤
               └─<file equation>─────────────┘

<compiler data specification>

── COMPILER ─┬─ DATA ───┬─┬─────────────┬──────────────────────────────►
             └─ EBCDIC ─┘ └─<file name>─┘

►─<DASDL description of database>──────────────────────────────────────┤

Explanation

The database name is an identifier. Like all identifiers, the database name can contain from 1 to 17 letters, digits, and hyphens. The first character must be a letter; the last character must not be a hyphen. The database name is used to form the titles of the description file, tailored database software, and database files.

Depending on the option specified in the compilation statement, the DASDL compiler checks the input for proper syntax, generates description and control files, and automatically compiles the tailored database software. The DMCONTROL and ZIP compiler control options can be used to override the option specified in the compilation statement.

Effect of WFL Statements on DASDL Compilation explains the effects of using different WFL statements.

If an asterisk (*) precedes the database name in the compilation statement, the DASDL compiler places the description file and tailored database software under the system directory.

The following examples illustrate valid WFL syntax for initiating DASDL compilations.

Example 1

The following WFL job compiles the DASDL description for syntax only. During the compilation, the DASDL compiler checks the syntax of the source input. No description file, control file, or database software are generated even if the input is error free.

<i>BEGIN JOB
   COMPILE DBNAME WITH DASDL SYNTAX;
   COMPILER DATA
     .
     . DASDL description of database
     .
<i>END JOB

Example 2

The following WFL job compiles the card and disk input.

During the compilation the DASDL compiler checks the source input for valid syntax, and if no errors are found, produces both the description and control files. The database software is not compiled.

The COMPILER FILE statements label-equate the titles of the TAPE and NEWTAPE files. The PRIORITY statement causes the DASDL compiler to run at priority 60 rather than the default priority. The SET MERGE statement instructs the DASDL compiler to use both the CARD and TAPE files as input. The DASDL compiler uses the TAPE file titled DBNAME/OLDSOURCE as input, and modifies it using the card images following the COMPILER DATA statement. Because the LIST option is set, all source input is listed on the line printer. The SET NEW option causes the production of an updated symbolic file titled DBNAME/NEWSOURCE. Both the printer and new symbolic files are resequenced as a result of the SEQ option.

<i>BEGIN JOB
   COMPILE DBNAME WITH DASDL;
   COMPILER FILE TAPE(TITLE = DBNAME/OLDSOURCE);
   COMPILER FILE NEWTAPE(TITLE = DBNAME/NEWSOURCE);
   COMPILER PRIORITY = 60;
   COMPILER DATA
   $ SET MERGE
   $ SET LIST
   $ SET NEW SEQ 100 + 100
     .
     .  Modifications to DASDL description of database
     .
<i>END JOB

Example 3

The following WFL job uses the DASDL library to compile disk input only.

The DASDL compiler reads the disk file DBNAME/SOURCE and checks it for valid syntax. If no errors are detected, description and control files are produced, and tailored database software is compiled.

<i>BEGIN JOB
   COMPILE DBNAME WITH DASDL LIBRARY;
   COMPILER FILE CARD(KIND=DISK, TITLE = DBNAME/SOURCE);
<i>END JOB