Howdy:
Running a DB2 connect client (Command Line Processor for
DB2 SDK 7.2.0 on Windows NT) trying to connect to
OS/390 Mainframe running DB2 ver. 6.2.1 to build an
IXF file.
I have been extracting data into an IXF format for sometime,
but have found something odd about the IXF files that didn't
exist before.
When I create an IXF file, I get something new (with
unix, I can look at the file with 'strings'):
[snip build process info]
D:\sql_scpt\prod_sql>db2 -tf ip0proot.sql
Database Connection Information
Database server = DB2 OS/390 6.1.2
SQL authorization ID = jobuser
Local database alias = DB2ALIA
SQL3104N The Export utility is beginning to export data to file
"d:\ixf_dir\ip0proot.ixf".
SQL3105N The Export utility has finished exporting "919" rows.
Number of rows exported: 919
[/snip build process info]
This looks good, but when I check the file with strings,
I see a few new things added.
-- now --
[snip from ip0proot.ixf as of 30 Sep]
000051HIXF0002DB2 02.0020030930122049000330043700000
001604T023d:\ixf_dir\ip0proot.ixf
^^^^^^^^^^^ *(unwanted directory path)
[/snip from ip0proot.ixf]
-- before --
[snip from other IXF as of 17 Sep]
000051HIXF0001DB2 01.0020030917191348000590043700000
000086T17claimsum_hc_2003.
^ *(no directory path)
[/snip from other IXF]
Yet, all of the SQL scripts start with similar
export statements:
[snip from SQL]
export to d:\ixf_dir\ip0proot.ixf of ixf
...
export to d:\claims_ixf\claimsum_hc_2003.ixf of ixf
[/snip from SQL]
Questions:
* What would cause the IXF process to put the directory path
in, where before it didn't? Is this some parameter setting?
* Is there a way to *not* have an extract via IXF put the
directory path when creating the IXF file?
* Since I'm not the DB2 DBA on the mainframe, what questions
could I ask them to see if there were any changes that were
made that would account for something like this?
Thanks all!
-X
