Not converting VSAM to something else. Doing some mass migrations, one file at a time, from Data Accelerator compression to SMS compression. Which requires: (1) EXPORT vsam cluster; (2) remove from Data Accelerator; (3) add to SMS compression (using special data class); (4) IMPORT the vsam cluster; (5) rebuild any AIXes and PATHs.
I wanted to use UNIX just to simplify my coding so that each function on each cluster went into a unique UNIX file whose name made the function obvious. such as: export.my.vsam.file import.my.vsam.file def-aix-path.my.vsam.file buildixs.my.vsam.file or maybe put the function at the end of the name instead of the beginning. On Tue, 2011-07-19 at 13:40 -0700, Skip Robinson wrote: > I have a question no one seemed to ask: why the war on VSAM? There was > time back in the Dark Ages when nobody trusted VSAM, but I think we're > past that. It's free. It's pretty versatile considering that you can chose > between sequential data or indexed data with just a few definitional > parameters. What's the beef? > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] -- John McKown Maranatha! <>< ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
