Data Definition Language (DDL) Reference Manual (G06.24+)

Running the DDL Compiler
Data Definition Language (DDL) Reference Manual—426798-002
3-5
Completion Code Processing
•
If a dictionary exists on the default subvolume, open the dictionary for update
access and delete all the dictionary objects it contains; otherwise, create a
dictionary on the current default volume and subvolume.
•
Issue a prompt (!) for input from the terminal.
•
Parse the DEFINITION statement as it is entered, ending with END.
•
Compile the DEFINITION statement and write production comments to the
terminal.
•
Exit from DDL, returning to the command interpreter.
The last example writes file creation commands to a FUP file from a record in an
existing dictionary:
63> DDL
!?DICT $data.sales
!?FUP fupsrc !
!OUTPUT RECORD customer.
!EXIT
These commands start a DDL process and instruct DDL to perform the following
operations:
•
Issue a prompt (!) for input from the terminal.
•
Open a dictionary on the volume $DATA and the subvolume SALES.
•
Open the file FUPSRC, clearing any contents from the file.
•
Retrieve the record CUSTOMER from the dictionary and write the appropriate FUP
file creation commands for this record to FUPSRC.
•
Exit from DDL, returning to the command interpreter.
Completion Code Processing
When the DDL compiler terminates its operation, it returns a completion code to the
command interpreter that indicates the outcome of the DDL run. The completion code
is one of the following:
The completion code is accessible in the TACL variable _COMPLETION.
Code Meaning
0 Normal termination. If warnings but no errors occurred, and the ?NOWARN
command was in effect, any warnings that did occur were suppressed
1 One or more warnings were reported, but no errors occurred.
2 One or more errors were reported (regardless of whether any warnings were
reported).
3 The DDL compiler stopped before processing all input because the number of
errors reached the limit specified in the ?ERRORS command.