For what it's worth, my client has been using PDSE for all their production
loadlibs,
source libraries, proclibs, etc. (managed by Endevor) since sometime just after
Y2K. The initial reason I pushed for it was occasional JES2 PROC issues after
weekly
compress jobs would run.
The only problem I recall in all these years was related to "illegal" sharing
between
a prod / devl sysplex (via MIM) of a prod CICS loadlib that someone included in
a
devl region shortly after we starting using PDSEs for the Endevor controlled
prod/qa/devl/test environments. Because PDSEs had to be SMS controlled
("going back to some ancient OS/390 release" as Ed said in a recent post) and
those
sysplexes have different SMS pools and the DASD volumes are not online
to the other plex, no other mistakes have ever happened. Actually, I'm
a bit surprised myself after all these years that there hasn't been a problem
every now and then due to sharing PDSE outside sysplex boundaries.
Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
ITIL v3 Foundation Certified
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://search390.techtarget.com/ateExperts/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
