Data Build Manual

DDL Input and Output (F2)
Running Data Build
099331 Tandem Computers Incorporated 4–11
Location of System Software
Names the location of the system software files. You enter these locations at the
Project Utility screen.
If a location other than EDIT is wrong, do not change it here. Instead, run the
Project utility and recreate the data conversion project subvolume with the right
settings. When Data Build creates a new conversion project subvolume, many
files are affected, and changing these locations does not automatically update the
affected files.
Specifying TEDIT Instead of
EDIT
When you ran the Project utility, you specified the location of the EDIT program. Data
Build requires EDIT (not TEDIT) to set up the conversion project subvolume. TEDIT
cannot be specified until you are running Data Build. Then, F10 on the Data Build
Main Menu screen invokes EDIT, the default, to allow editing and return to the Data
Build environment. To use TEDIT for F10 instead of EDIT, change the EDIT: line to
the location of TEDIT.
DDL Input and Output
(F2)
In step F2, Data Build takes the source records descriptions and builds input for the
Tandem DDL compiler. The purpose of this step is to make sure that the source record
descriptions, the input to the DDL, and the output generated by those source record
descriptions are accurate.
To build the DDL data definitions and run the DDL compiler:
1. Press F2 at the Main Menu.
2. When the process finishes, press any key to return to the Main Menu.
3. Press F12 to run Peruse. Check spooler locations #BLDDDL and #DDL for errors
or warnings. Correct any errors before going to the next step.
4. Exit Peruse to return to Data Build.
The DDL record descriptions files are created from the source record descriptions. The
IN section in each DDL record descriptions file describes each input field (in
alphanumeric format) along with the conversion commands. The OUT section
describes each output field as it will appear when converted.
Suppose the data input file being converted has 12 fields, and you need to add a field
to the converted (output) file. To account for the new field, you must modify the DDL
record descriptions file. Appendix C, “Describing Various Data Types,” provides
examples of how to describe data types for the DDL. When you make changes to the
file, you cannot rerun the DDL compiler in Data Build. Instead, you should manually
run ZZDDLIN through the DDL compiler.