Data Build Manual
File and DEFINE Names
Understanding Data Build Files
099331 Tandem Computers Incorporated 2–7
For disk input in the BUILD DDL (F2) step, Data Build uses the IN Data Files
prefix you specify as follows:
Data Build looks for all of the input files on the conversion project subvolume
or on another subvolume, if a qualified subvolume prefix, that is subvol.X,
was specified.
DEFINE names are not used.
In this example, Data Build looks for files X01, X02, ... on the conversion
project subvolume until it does not find the next Xnn file.
For this example, files X01 through X03 exist.
For disk input, in the RUN (F5) step Data Build uses the IN Data Files prefix you
specify as follows:
DEFINE names, constructed from the IN Data Files Prefix, are used.
For each input file the actual file name (prefix plus suffix) must be the same as
the DEFINE name. It must be on the same subvolume that was used for the F2
step above.
For tape input, see the subsection, “Tape Input,” for more information.
As in the second example where the output is to SQL, the DEFINE name for each
Output data File (Table) is the same as the 01 level record name in the associated
Source Record Descriptions File, for example. ORG for the first output file.
Note that the 01 level record name is created by Data Build from the table name in the
IXF Table (T) Record for each input file. In order to create the DEFINEs in the
DEFINES and PATHCNFG files, you need to know the table names used when the IXF
data tape was created.
If the table names are not known, the names can be found in the Source Record
Descriptions Files after the BUILD DDL (F2) step. To find the table names, you can do
the following:
1. Exit Data Build after the BUILD DDL (F2).
2. Find the 01 record names in the Source Record Descriptions files.
3. Add DEFINEs for these names to the DEFINES and PATHCNFG files.
4. OBEY DEFINES.
5. OBEY XSTART (to restart the Data Build Pathway system with the updated
PATHCNFG information).
6. OBEY XRUN (to restart Data Build).
7. Repeat the F2 step. This is necessary for Data Build to create the NonStop SQL
tables which failed in the previous F2 step because the correct table DEFINE s
were not specified.