Data Build Manual

File and DEFINE Names
Understanding Data Build Files
099331 Tandem Computers Incorporated 2–5
Figure 2-2. Non-IXF Disk Input to SQL-LOAD File-Naming Example
-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
---------- ----------
-- see info re 1st file --
| |
V V
|-DEFINE =X01,.....,FILE $vol.svolx.aaa
IN: X ->| DEFINE =X02,.....,FILE $vol.svoly.bbb
Data |-DEFINE =X03,.....,FILE $vol.svolz.ccc
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 __________ 4 __________
( 5 __________ 6 __________
The Source Record Descriptions files, the DDL Record Description files and the input
data files are named the same as in the first example. For the first input file to be
converted, these files have names ending with suffix 01; that is RDE01, DD01 and X01.
The DEFINE name for each output data file is different than in the first example; it
must be the same as the 01 level record name in the associated Source Record
Descriptions file, that is =ORG for the first output table, =STAFF for the second and
=PROJ for the third. The user specified the 01 level record name when the Source
Record Descriptions file was built. The actual table name can be any valid name on
any volume or system.
Note The OUT Data Files specification on the CONFIGURE (F1, Conversion Environment) screen must be
filled in but is not used; it can be set to DUMMY as shown or another appropriate name of your choice.
DEFINEs for DUMMYnn, or the name you specify, are not needed in the DEFINES or PATHCNFG files.