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] From: John McKown <[email protected]> To: [email protected] Date: 07/19/2011 06:39 AM Subject: restricting how I do things so that others understand? Sent by: IBM Mainframe Discussion List <[email protected]> I'm working on a project which involves "converting" a lot of VSAM files. So far, I've restricted myself to using PDSes and REXX. Everybody in my group (mainframe sysprogs) understands these. But, for my own convenience, I'd like to use UNIX files. Why? Because I can create really long file names, such as: export-jcl.<vsam_dsn>, import-jcl.<vsam_dsn>, define-jcl.<vsam_dsn>, and so forth. But nobody else in my group really "digs" UNIX stuff and none of them, other than myself, actually likes it. So, should I restrict myself to only using generally understandable stuff. Or, since this project is not production (basically do the conversion then ignore it), should I just do it the way that is easiest for me? The problem with this is that there are a large number of files to convert and it will take quite a while. So using UNIX basically means it is my baby entirely. -- 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
