Data Build Manual

File and DEFINE Names
Understanding Data Build Files
2–6 099331 Tandem Computers Incorporated
IXF Disk Input to NonStop
SQL
In Figure 2-3, Option 1 is set to SQL-LOAD for a conversion to NonStop SQL and
Option 3 is set to IXF for IXF input (file naming for SQL-INSERT is the same as for
SQL-LOAD). File naming is a little different than for a non-IXF conversion to NonStop
SQL as described in the previous subsection.
Figure 2-3. IXF Disk Input to SQL-LOAD File-Naming Example
Data Build creates the
Source Record Description File
01 level name from IXF input
-actual file names-
| |
| V
| RDE03
V ----------
Source Record Desc Files: RDE --------------------------> | 01 PROJ
---------- RDE02
| DD03 ----------
---------- | 01 STAFF
DDL Record Desc Files: DD -------> | DD02 RDE01
---------- ----------
| DD01 | 01 ORG
---------- ----------
--same name for ALL files--
| |
V V
|-DEFINE =X01,......,FILE $vol.svol.X01
IN: X ->| DEFINE =X02,......,FILE $vol.svol.X02
Data |-DEFINE =X03,......,FILE $vol.svol.X03
name from 01 level in
Source Record Descriptions File
|
Files |
OUT: dummy V
DEFINE =ORG,......,FILE $vol.svola.ab
DEFINE =STAFF,....,FILE $vol.svolb.cd
DEFINE =PROJ,.....,FILE $vol.svolc.ef
( OPTIONS: 1 SQL-LOAD__ 2 __________
( 3 IXF_______ 4 __________
( 5 __________ 6 __________
Data in IXF format contains self describing context. For IXF input, you do not provide
Source Record Descriptions files. Early in the BUILD DDL (F2) step, Data Build reads
the IXF Table and Column records, which precede the actual data, in each input file.
Data Build uses this information to create an associated Source Record Descriptions
File for each input file.