DBCSV Sample output

The following shows a run of DBCSV on a database called "JF01":

:run DBCSV.PUB.ALLEGRO

Welcome to DBCSV     (version 20030205)

Copyright (c) 2001  Allegro Consultants, Inc.
Author: Stan Sieler (sieler@allegro.com)

For help, type: HELP

DBCSV: cdf jf01.testdb all  /tmp/foo  header

Set #   1 : DIST-M
   # in-use entries: 5
   wrote 6 lines to /tmp/foo.DIST_M.csv

Set #   2 : AR-TRAN
   # in-use entries: 85
   wrote 86 lines to /tmp/foo.AR_TRAN.csv

wrote 24 lines to /tmp/foo

DBCSV:

The above run produced one CSV file for each of the five datasets. The last dataset, AR_TRAN, produced the following CSV file:

"DIST-ID","SV-MON-TRNS-DT","TRNS-TYPE","TRNS-NUM","TTL-AMT","TTL-AMT-CN","TTL-SV", "TTL-REB-AMT", "TTL-REB-AMT-CN", "ENT-DT", "ENT-BY", "COMMENT", "TTL-KAN-SV"
"00196090", "20010520010523", "P8", 00262885, -000000042195,  000000000009,  000000000000,  000000000000,  000000000000, 20010523, "MARY", "SECRET1",  00000000000 
"00196090", "20010520010523", "IN", 00262885,  000000042195,  000000000009,  000000101750,  000000020355,  000000000005, 20010523, "MARY", "SECRET2",  00000000000
...

Note that the first line contains the field names because the HEADER option was requested. (The names in the header line do not align with the following values because sometimes the width of an item name has no correlation to the item field width.)

The leading zeros on some of the numbers are an indication that the numbers were in packed decimal format ... i.e., the zeroes were actually stored in the IMAGE dataset. They can be optionally suppressed from the output.

If the STRIP0 and NOBLANKOK options had been specified, the above output would be:

"DIST-ID", "SV-MON-TRNS-DT", "TRNS-TYPE", "TRNS-NUM", "TTL-AMT", "TTL-AMT-CN", "TTL-SV", "TTL-REB-AMT", "TTL-REB-AMT-CN", "ENT-DT", "ENT-BY", "COMMENT", "TTL-KAN-SV" 
"00196090","20010520010523","P8",262885,-4219,0,0,0,0,20010523,"MARY","SECRET1",0
"00196090","20010520010523","IN",262885,4219,0,10175,2035,0,20010523,"MARY","SECRET2",0
...

If the files are FTP'd (binary, not ASCII) from the HP 3000, they could be imported into Microsoft Excel by clicking on <Data> <Get External Data> <Import Text File>. Note: we have seen Windows FTP client inject extraneous <return> characters into files that are FTP'd from the HP 3000 with the ASCII option.