>Sometimes DASD shared between sysplexes are
dedicated for "data transport". In such case it is enough to define it
as SHARED and rely on RESERVEs.
...
Been there. Done that.
Didn't like it!
Don't want to do it again.
It only happened intermittently, but always at a busy time.
Catalogue/dataset
>CA will have reasons why MIM should be kept, but due to costs and
how GRS is working very well now, I have no idea, outside of the job
requeuing feature, why one would keep MIM.
...
If you have a need to share DASD between two SYSPLEX's.
-teD
In God we Trust!
All others bring data!
-- W. Edwar
On Thu, 1 Sep 2005 17:07:06 -0400, LUCAS, THOMAS E <[EMAIL PROTECTED]>
wrote:
>With the recent z/OS 1.6 upgrades for SYSPLEX support, PPRC, GDPS and
>VTS (Virtual Tape Support), has anyone been able to use this technology
>infrastructure to remove and replace their existing copies of the
>software
CA-MIM still provides sharing of data (not PDSEs, though) across sysplex
boundaries, which the IBM products do not. If you have multiple sysplexes
sharing DASD, this is a show-stopper.
Cheers,,,Steve
Steve Conway
Systems Programmer
[EMAIL PROTECTED]
703.921.6432
---
-- snip --
With the recent z/OS 1.6 upgrades for SYSPLEX support, PPRC, GDPS and
VTS (Virtual Tape Support), has anyone been able to use this technology
infrastructure to remove and replace their existing copies of the
software known as "CA-MIM" (Multi-Image-Manager)? If so, how did you
justify thi
With the recent z/OS 1.6 upgrades for SYSPLEX support, PPRC, GDPS and
VTS (Virtual Tape Support), has anyone been able to use this technology
infrastructure to remove and replace their existing copies of the
software known as "CA-MIM" (Multi-Image-Manager)? If so, how did you
justify this type of p
6 matches
Mail list logo
