Data Build Manual

Conversion Environment Menu
Data Build Reference
099331 Tandem Computers Incorporated 7–7
Note QMF can format and extract data from DB2 databases in either QMF or IXF format; however, Data Build
cannot convert data in QMF format.
Option 4 This field specifies whether your input is on tape or is in CSV file format.
Option Meaning
Blank Disk input, not in CSV format.
=TAPE Tape input
CSV=* CSV file format. You should replace the asterisk (*) with the delimiter used in
your file (for example, if your delimiter is a comma, specify CSV=,). If you specify
CSV for Option 4, you must specify ASCII for Option 3.
TAPE Input
Specifies that the input data is on tape.
CSV Input
Specifies that the input is in CSV file format. You must specify ASCII in Option 3 if
your input is in CSV file format. A delimited ASCII file is a stream of ASCII characters
consisting of cell (field or column) values ordered by row and then by column. Rows
in the data stream are separated by a row delimiter, which can be a CR/LF sequence, a
separator character (such as a comma), or an end of record. Within a row, individual
field or column values are separated by the specified CSV separator character, which
may be any value other than a space or a period. There can also be a character string
delimiter, a single or double quote; this is most often used to surround a value that
contains column separators.
Data Build can convert the file to SQL-LOAD, SQL-INSERT, or ENSCRIBE (blank).
Data Build accepts CSV input with the following guidelines:
CSV input must be on disk; CSV data on tape is not allowed.
There is no default delimiter. You must specify the CSV delimiter in Option 4. For
example, if the delimiter is a comma (,), you would specify the following:
CSV=,
The end of the last field value in a record is delimited by one of the following:
Carriage return line feed
Delimiter character
End-of-record
Continuation lines are not supported.
Input must be in display format in an entry sequenced file, an EDIT file, or an
unstructured file.