Don't waste your time trying to load that file using the load utility. It
simply doesn't work. In DB2 V8 for z/OS you will be able to load ascii
delimited files, but that's another story. Besides, even an ftp would solve
the problem for ixf files have thetable definition sitting on top of the
data.
This is what I would do:
- load the ixf file into a table on a DB2/UDB box that is "seen" by the
mainframe (TCP/IP used by DB2/UDB must be defined on the mainframe);
- create, if you haven't already done that, an entry in the communication
database pointing to the DB2 UDB database;
- create a table on the mainframe that has the same layout of the one in the
DB2/UDB database;
- run the load utility on the mainframe using a cursor that points to the
table on DB2/UDB. That way you can run the load using LOG NO.
Let me know if you need more info.
Enjoy,
Mauro.
"Carmine" <ca************@iqfinancial.com> wrote in message
news:1e************************@posting.google.com ...
will it work with an ixf file,
or does the file have to be ascii?
thanx...
el****@hotmail.com (Lekharaju) wrote in message
news:<1f**************************@posting.google. com>...
you can not run load from pc into mainframe, use file transfer
utility to main frame , create JCL , use load utility
that will work
ca************@iqfinancial.com (Carmine) wrote in message
news:<1e*************************@posting.google.c om>... This is what I get when I try to do a load
from a pc to the mainframe...
SQL1325N The remote database environment does not support the
command or one of the command options.
Martin <Ne**@avisoft.force9.net> wrote in message
news:<4c4e5928d4Ne**@avisoft.force9.net>... > In article <1e*************************@posting.google.com> ,
> Carmine <ca************@iqfinancial.com> wrote:
> > I need to import a huge .ixf file from a pc to db2 v7 zos.
> > Is there a way to stop archive logging while the
> > data is being imported?
>
> Try LOAD with LOG NO !
>
> Do not use SQL INSERT - it is MUCH slower ... partly because it will
log > all the changes.
>
> > If not, is it safe to delete archive logs that haven't expired?
>
> Noooooo! The logs apply to the whole DB2 subsystem - all
application data > changes and system catalog/directory.
>
> Martin