[snip from ip0proot.ixf as of 30 Sep]
000051HIXF0002DB2 02.0020030930122049000330043700000 001604T023d:\ixf_dir\ip0proot.ixf
^^^^^^^^^^^ *(unwanted directory path)
Is this actually causing problems for you? The record you are showing is the IXF header record, and just contains information about the export, like when it was exported, the filename, etc. The fact that it contains the full pathname does not effect the data or what is necessary to load it.
Questions:
* What would cause the IXF process to put the directory path in, where before it didn't? Is this some parameter setting?
This is (in my experience) controlled by how you specify the filename in the EXPORT command (on the client). If you give a fully-qualified path (d:\claims_ixf\claimsum_hc_2003.ixf) you'll see the entire path. If you just give a filename (claimsum_hc_2003.ixf) you'll just see the filename.
Have your export scripts been changed to specify full pathnames for the export files recently?
* Is there a way to *not* have an extract via IXF put the directory path when creating the IXF file?
Don't include the full path name for the export. i.e.
d: cd \claims_ixf db2 "export ..."
* 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?
Nothing on the mainframe would affect this, because all of the IXF formatting is taken care of by the export utility. Has there been a new DB2 fixpack installed on your NT machine lately?
Good luck,
Ian Bjorhovde [EMAIL PROTECTED]
- ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
