On Sep 23, 2005, at 5:19 PM, Mark Zelden wrote:
---SNIP--
RESERVEs are not an issue regardless of the PROCESS= setting. You
can always find the ones your not processing with a DISPLAY COUNTS
command.
Cheers,
Mark
In previous years, (SDSI and MIM) put o
On Fri, 23 Sep 2005 14:18:50 -0500, Dave Danner <[EMAIL PROTECTED]> wrote:
>Also, if you do this make sure you have SET GDIF COUNT=SYSTEMS and issue
>DISPLAY COUNTS commands before and after the change. I was amazed at the
>number of SYSTEMS ENQs we were not serializing because we didn't
>specifi
On Thu, 22 Sep 2005 20:11:14 -0500, Glenn Miller <[EMAIL PROTECTED]>
wrote:
>I'm curious how other shops are 'configured'. We currently use the CA-MII
>( Multi-Image Integrity ) and
>CA-MIA ( Multi-Image Allocation ) products. We are having a
>discussion/issue regarding the ENQ
>Processing Mode
Kees,
The only parallel sysplex 'sharing' requirement we have been told is
no reserve's are allowed in a GDPS/PPRC Hyperswap environment.
CA-MIM has strongly recommended the use of ALLSYSTEMS mode
for a number of reasons:
ALLSYSTEMS mode allows Unicenter CA-MII to automatically manage
all SCOPE=S
<[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>...
> I'm curious how other shops are 'configured'. We currently use the CA-MII
> ( Multi-Image Integrity ) and
> CA-MIA ( Multi-Image Allocation ) products. We are having a
> discussion/issue regarding the ENQ
> Processing Mode of CA-M
I'm curious how other shops are 'configured'. We currently use the CA-MII
( Multi-Image Integrity ) and
CA-MIA ( Multi-Image Allocation ) products. We are having a
discussion/issue regarding the ENQ
Processing Mode of CA-MII, which can be either 'SELECT' or 'ALLSYSTEMS.
Currently, we use
the 'SEL
6 matches
Mail list logo
