export from DB2/390 as del

[robert]

looked at this archive and what docs i can find,
but it seems that the only way to get text export
from 390 onto a windoze machine is to use AQT on a
table by table basis (or some other database editor).

the 390 guys here have an unload utility that's wrapped
in JCL and such, but when the files get to win2k,
there's lots of unreadable hash; certainly not a csv
file. i'm guessing it's really ixf.

what i expected to be able to do is write a script with
one export statement per table. this does work in UDB.

thanks,
robert

[Bill]

Robert,

If you can use an ASC file (fixed record format), you can use the CLP and
redirect the output to a flat file:

db2 -x "select * from os-390.table" > outfile.asc

The -x option suppresses the header and trailer data that would normally be
displayed by the CLP.

"robert" <gn*****@rcn.com> wrote in message
news:da**************************@posting.google.c om...

looked at this archive and what docs i can find,
but it seems that the only way to get text export
from 390 onto a windoze machine is to use AQT on a
table by table basis (or some other database editor).

the 390 guys here have an unload utility that's wrapped
in JCL and such, but when the files get to win2k,
there's lots of unreadable hash; certainly not a csv
file. i'm guessing it's really ixf.

what i expected to be able to do is write a script with
one export statement per table. this does work in UDB.

thanks,
robert