Data Build Manual

File and DEFINE Names
Understanding Data Build Files
2–4 099331 Tandem Computers Incorporated
These files can reside on any subvolume if a qualified subvolume prefix is specified,
for example. subvol.DD. The default is normally the Conversion Project Subvolume.
Data Files IN
The prefix of X plus a suffix specifies a DEFINE name. In this example, the three
Enscribe input files have DEFINE names of =X01, =X02 and =X03. For each input file
the actual filename may be any valid name on any volume or system.
A qualified filename, which optionally includes a subvolume, volume and system
name, can be specified. The default is normally the Conversion Project Subvolume.
The BUILD DDL (F2) step makes an unnecessary check for a BASEnn file, where BASE
is the user specified prefix and nn is any number from 00 to 99. If a BASEnn file is not
found on the conversion project subvolume or on a specified subvolume, the error
message is issued:
ERROR - Cannot Locate Data Input Files
Data Build does not use this file in the F2 Step. If the file has been defined to a
different name, this error message can be ignored or, to prevent this message, a
dummy file can be created to satisfy this check.
Data Files OUT
The prefix of CNVRT plus a suffix specifies a DEFINE name. In this example the three
Enscribe output files have DEFINE names of =CNVRT01, =CNVRT02 and =CNVRT03.
For each output file the actual filename may be any valid name on any volume or
system.
Non-IXF Disk Input to
NonStop SQL
In Figure 2-2, Option 1 is set to SQL-LOAD for a conversion to NonStop SQL (file
naming for SQL-INSERT is the same as for SQL-LOAD). File naming is a little
different from the conversion to Enscribe shown in Figure 2-1.