> Hello,

> It sounds like a simple task- but in reality it is'nt:

> Various sources provide us with data in the popular DELimited file format
> and we want to import this data to tables on DB2 for OS/390 by means of DB2
> Connect (V6.1). The DB2 Connect IMPORT Utility supports only IXF format for
> remote (DRDA) databases, while the DB2 Connect LOAD Utility does not support
> DRDA Databases at all (and in turn, the DB2 for OS/390 LOAD Utility does not
> support DEL files...).

> > Hello,

> > It sounds like a simple task- but in reality it is'nt:

> > Various sources provide us with data in the popular DELimited file
format
> > and we want to import this data to tables on DB2 for OS/390 by means of
DB2
> > Connect (V6.1). The DB2 Connect IMPORT Utility supports only IXF format
for
> > remote (DRDA) databases, while the DB2 Connect LOAD Utility does not
support
> > DRDA Databases at all (and in turn, the DB2 for OS/390 LOAD Utility does
not
> > support DEL files...).

> Why not set up a 'transit' database on an NT workstation or suchlike
> and import into this one, then write a VB program to get the data out
> of the 'transit' database and insert it into the production database?

> I haven't used replication myself, but replication from the 'transit'
> database to the production database  might be a possibility as well.

> Okay, follow this through.
> Use comma delimited exports from you favorite applications
> FTP the file to the mainframe to get the character conversion
> Have your freindly mainframe DBA code a set of control cards for the
> table(s) you want, skipping the comma position between feilds
> example xxx,yyy,zzz = feild1 (1,3), feild2 (5,7), feild3 (9,11), etc
> load your tables using the mainframe load utility

> This scenario can be a pain in the butt. It also works very well. All of the
> steps involved can be automated so it very end-user proof :)

> Robert Jans
> DB2 for OS/390 DBA

> > > Hello,

> > > It sounds like a simple task- but in reality it is'nt:

> > > Various sources provide us with data in the popular DELimited file
> format
> > > and we want to import this data to tables on DB2 for OS/390 by means of
> DB2
> > > Connect (V6.1). The DB2 Connect IMPORT Utility supports only IXF format
> for
> > > remote (DRDA) databases, while the DB2 Connect LOAD Utility does not
> support
> > > DRDA Databases at all (and in turn, the DB2 for OS/390 LOAD Utility does
> not
> > > support DEL files...).

> > Why not set up a 'transit' database on an NT workstation or suchlike
> > and import into this one, then write a VB program to get the data out
> > of the 'transit' database and insert it into the production database?

> > I haven't used replication myself, but replication from the 'transit'
> > database to the production database  might be a possibility as well.

> Hi Robert,
>     comma delimited fields are normally variable in length. As

>     field1,field..........2,field3,
>     field......1, field.................2, field...3

>     But you could write a simple Rexx proc to pad them out to be fixed
length.

> Bill

> > Okay, follow this through.
> > Use comma delimited exports from you favorite applications
> > FTP the file to the mainframe to get the character conversion
> > Have your freindly mainframe DBA code a set of control cards for the
> > table(s) you want, skipping the comma position between feilds
> > example xxx,yyy,zzz = feild1 (1,3), feild2 (5,7), feild3 (9,11), etc
> > load your tables using the mainframe load utility

> > This scenario can be a pain in the butt. It also works very well. All of
the
> > steps involved can be automated so it very end-user proof :)

> > Robert Jans
> > DB2 for OS/390 DBA

> > > > Hello,

> > > > It sounds like a simple task- but in reality it is'nt:

> > > > Various sources provide us with data in the popular DELimited file
> > format
> > > > and we want to import this data to tables on DB2 for OS/390 by means
of
> > DB2
> > > > Connect (V6.1). The DB2 Connect IMPORT Utility supports only IXF
format
> > for
> > > > remote (DRDA) databases, while the DB2 Connect LOAD Utility does not
> > support
> > > > DRDA Databases at all (and in turn, the DB2 for OS/390 LOAD Utility
does
> > not
> > > > support DEL files...).

> > > Why not set up a 'transit' database on an NT workstation or suchlike
> > > and import into this one, then write a VB program to get the data out
> > > of the 'transit' database and insert it into the production database?

> > > I haven't used replication myself, but replication from the 'transit'
> > > database to the production database  might be a possibility as well.