In my understanding of TSM the ASCII/EBCDIC issue is not with the client data, it's with the TSM database. The data on the tape is in the format in which it is delivered by the client - TSM doesn't change client data in any way. You can use the export/import route you like best. I think the server- to-server route will be much faster as you process the data only once.
I did server-to-server import/export (AIX to Windows) and it worked great. Be aware that TSM writes the primary and copy pool at the target system at the same time. So you need more available drives on the target system. HTH Thomas Rupp -----Ursprüngliche Nachricht----- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Mark Wheeler Gesendet: Freitag, 10. Februar 2006 21:37 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] Exporting ADSM/VM Data to an (ASCII-based) TSM Server I'm planning to replace my ADSM/VM 3.1 server with TSM 5.3 on zSeries Linux. I have about 14 terabytes of data to move. My tape vendor says I can't export/import using tape because of ASCII/EBCDIC issues. He says I have to go the server-to-server route. Some of my clients store over a terabyte of data each, which I'm expecting could take a while! Has anyone moved from ADSM/VM (or TSM on z/OS for that matter) to an ASCII-based platform (Windows, AIX, Linux) using tape for export/import? Has anyone used server-to-server export/import who could provide a throughput rate estimate? In my case, I'll be able to exploit hipersockets as the "network". Thanks! Mark Wheeler, 3M Company
