On Thu, Aug 19, 2010 at 3:45 PM, Monty Spivak <[email protected]> wrote:

> Hi,
>
> 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).
>
>
>
> Here is what I already considered and discarded for various reasons:
>
> 1. ISPF editor, and others, have a search and replace, but it is for only
> for 1 script at a time.
>
> 2. Unload it to a huge sequential file, use ISPF to edit it, and then load
> it back into a the PDS. Failing that, JCL is simply stored as clear text in
> a PDS (partitioned dataset).  Anything that will read a PDS would work, or
> use the unload process to get one sequential file first. Our customer would
> not like this approach.
>
> 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...
>
> I would appreciate if someone would point me in the right direction...
>
> Thanks, Monty
>
> Monty Spivak
> SAS Institute Canada
> [email protected]mailto:[email protected]
>
> Filemanager from IBM will allow find/change in every member of a PDS if
that is what you are after.

Jim McAlpine

----------------------------------------------------------------------
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

Reply via email to