I am trying to look into doing both. The REFORMAT command takes a database file (text file in DB2) and puts it into an ASCII format. When looking at the file in UNIX, it looks like a regular fixed-length ASCII file. However, there are things in that file, like logical deletions of records, that DB2 and UNIX do not process. When you port it into a Windows environment, you get characters that look like a y with two dots over it.
The REFORMAT command fixes this issue. After running it, the file looks like an ASCII file and is easily portable into SQL Server. The only problem is that at this point, it is a manual process. I am looking into utilizing Host Integration Server to take care of this issue. I am thinking that the OLE DB Provider for DB2 might be a way to go, but don't know enough about DB2 to provide the right parameters for the necessary .udl file.
Thanks for your response. Please let me know if you have any insight on this.