Just use the PGM=IPOUPDTE from IBM. We are using this tool to change JCL. It is delivered from IBM with every z/OS.
Alexander -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Staller, Allan Sent: Thursday, August 19, 2010 5:18 PM To: IBM-MAIN@bama.ua.edu Subject: Re: JCL "Mass Editor" 1) PDS COMMAND from CBT tape 2) Use DATASET ALIAS to keep the same name in JCL but point to a "different" file. <SNIP> I am is seeking a JCL "Mass Editor" (basically, multiple file search and replace in an LPAR). We have 3,000 JCL scripts and are seeking to make changes to upgrade SAS versions. Would you know of an appropriate tools to use (I know that someone could write scripts to examine the JCL scripts, but it would be a lot nicer if one would just be able to use a "search and conditionally replace" against all of the JCL in an LPAR). </SNIP> Perhaps you should consider "biting the bullet". Consider this an investment in the future! <SNIP> 3. I am sure that there are not one or two procs somewhere where the change could be made. Most shops have procs that control the calls to SAS and other such products. The idea is to bury all the installation specific stuff in one proc, then have the user jobs call the proc. That way when you change something, you only change it in the one proc, not every user job. It appears that the JCL was not originally structured this way... </SNIP> HTH, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
