Data Build Manual

Where to Go Next
Running the Sample Programs
099331 Tandem Computers Incorporated 5-19
The samples have three Source Record Descriptions files: RECDEF01, RECDEF02, and
RECDEF03, which is one Source Record Descriptions file for each input file. The
following example is from RECDEF03, the source record descriptions for DEMO03:
01 DEMO03. <-- Output Table DEFINE Name
02 DEM3-DATE <-- Field Name PIC X(10) DATE.
02 DEM3-TIME PIC X(8) TIME.
02 DEM3-NUMBER PIC S9(4) COMP.
02 DEM3-DESCR PIC X(9). <-- Data Format
02 DEM3-TYPE PIC S9(4) COMP.
02 DEM3-VENDORID PIC S9(9) COMP.
02 DEM3-WHLSLRID PIC S9(9) COMP.
02 DEM3-PARTNO PIC S9(9) COMP.
02 DEM3-PRICE PIC S9(8)V9(2) COMP-3.
02 DEM3-CODE PIC X(2).
02 DEM3-COST PIC S9(9) COMP.
DEMO03, the COBOL85 group level record definition, corresponds to the NonStop
SQL table DEFINE name. The field names at the 02 level tell Data Build the field’s
data format in the source system input file.
The DEFINES File This subsection discusses the sample DEFINES file and explains its purpose.
DEFINES is an EDIT file that contains TACL DEFINE statements.
To look at the DEFINES file, do the following:
1. Make sure you are at the conversion project subvolume.
2. Use the editor to look at the DEFINES file.
In the DEFINES file, this ADD DEFINE names the NonStop SQL catalog and its
location:
ADD DEFINE =CAT,CLASS CATALOG,SUBVOL $CONVERT.SQLCAT
The NonStop SQL catalog name and location are taken from information you entered
in the Project Utility screen.
The following DEFINEs specify the input files:
DELETE DEFINE =DATAIN01
ADD DEFINE =DATAIN01, CLASS MAP, FILE $CONVERT.SUBVOL.DATAIN01
DELETE DEFINE =DATAIN02
ADD DEFINE =DATAIN02, CLASS MAP, FILE $CONVERT.SUBVOL.DATAIN02
DELETE DEFINE =DATAIN03
ADD DEFINE =DATAIN03, CLASS MAP, FILE $CONVERT.SUBVOL.DATAIN03
This tells Data Build where the data being converted is located. For sample input files
DATAIN01, DATAIN02, and DATAIN03 are located on every conversion project
subvolume.
The output files named in the DEFINES file are not used in this example. They are
included in the DEFINES file because the file is set up for all three sample conversions.
The output for this conversion will be loaded to NonStop SQL tables.