On Wed, Jan 28, 2009 at 10:11 AM, Ted MacNEIL <[email protected]> wrote:
> Or, consider propagating PROCLIBs. > If you maintain them from one system, and one system only, it's not that > difficult. hmmmm, I can look into this idea... we already have duplicated loadlibs and such.... Is that an automated sort of thing? i.e. a change to a member in that library is detected and automatically sent to the other sites? > Also, PROCs protect you from when a product, for example: SAS, changes. > You can change it one place without having to change multitudes of JCL. Generally that's true. But a PROC is just one way to implement the concept of "one copy for all to share". The question becomes, where does the proc reside? Where is the best place to keep the "one copy to maintain"? When I have geographically diverse MVS systems, and jobs are submitted from VM, perhaps the best "one place" is a CMS file on VM that all the various execs can easily share. Or an exec that basically builds an expanded proc. That way a CMS EXEC can be thuoght of as an MVS PROC, doing the simple substitutions and building an inline JCL stream which, by the time it gets to MVS has no "PROC" as far as MVS is concerned. Yet, we still have the "protection" you describe. hmmm, that sounds like a very simple solution. :-) Cheers, ---------------------------------------------------------------------- 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
