On Wed, Jan 28, 2009 at 9:57 AM, Rick Fochtman <[email protected]> wrote:
> You can't share the PROCLIB ?? The MVS systems are scattered across the country. > > You can always run the proc inline and submit the job to the correct system. > Methinks you should define "different MVS systems". Are they in a MASPLEX ? > Or are they physically separate systems? Our VM system and one MVS system can shard DASD, but the other MVS systems are hundreds of miles apart. I could put the proclib on a vm/mvs shared dasd, then if the job should go to that MVS system just build any needed overrides, otherwise copy the proc and submit it as an inline proc as you suggest. But, I think if I'm going to do that, I may as well keep the proc in vm and always submit it as an inline proc. That way I remove the dependency that the proclib be on a specific dasd volume, and I eliminate the overhead of accessing/reading an OS volume from VM. Thanks ---------------------------------------------------------------------- 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
