"Barbara Nitz" <[email protected]> wrote in message
news:<[email protected]>...
> >I have been looking into IRD, to see if this could be useful and in
that
> >process I defined the SYSZWLM structures. In the end I decided that
IRD
> >was not useful, because it stops working when an LPAR is soft-capped
and
> >that just was when I needed it to do its job.
> You are not supposed to find anything IBM does not useful! :-)
> 
> >The moment I activated the policy with the SYSZWLM structures, all
WLMs
> >in all Sysplex members jumped on it and allocated it and they keep on
> >allocating it. I reloaded the old policy and the structures came in a
> >Pending-delete status, but cannot be deleted because WLM allocates
it.
> >SETXCF FORCE and IPLs don't help, I can only think of a Sysplex wide
IPL
> >to get rid of the structure. 
> 
> As far as I remember, there is no way to turn IRD off if it was ever
turned on by defining those structures. And XCF/XES is very bad in not
providing any cleanup abilities for anything sysplex related. Did you
try a structure rebuild? There was a time when that would have gotten
rid of these sturctres because there was  no place to build them into.
These days the rebuild might just be denied. If rebuild doesn't work, a
sysplex IPL without those structures defined is your only chance.
> 
> Just like XCF will always remember that at one time a certain couple
data set (ARM in our case) used to be active. It will show up faithfully
on a D XCF,CPL command despite the fact that the whole plex was IPL'd
without the ARM CDSs in COUPLExx and despite the fact that those
datasets don't physically exist anymore. 
> 
> Barbara Nitz

You can turn IRD off effectively in IEAOPT00 by disabling its functions,
but that does not remove the structures, nor probably the overhead of
WLM's exchange of information. I tried the Rebuild, and it rebuilds
perfectly, leaving the structures in a pending delete status. 

For the mentioned Logstream problem, I suggested a 'drain' status,
current connections keep on working, but no new connections are
permitted, but this was rejected. A similar function seems useful for
structures, but I am afraid I will get the same answer.

Luckily this is our test Sysplex, so I can schedule a Sysplex wide IPL,
but this will be a real problem in production sysplexes.

Kees.

********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to