>One man's design point is another man's onerous restriction. I didn't say it was right. I just said it was.
I can report on a problem that should not exist, but it's there. CF's cannot be shared between SYSPLEX's. They can only be dedicated. But, if a CF is online to any image, it is polled by that image, regardless of whether it is in use by that image, or not. This causes the CF to interupt itself to just say "go away", then it can go on and do real work. IBM claims that this is just in case the CF becomes available for use in the existing SYSPLEX. Bullsnot! It requires a lot of work to move a CF from one SYSPLEX to another! Yes, we can configure them offline (had to). But, if they're not in the SYSPLEX policy, why are they polled? I had a discussion with a VTAM expert. If an NCP is not defined to an image, it is not polled. What is the difference. BTW, this extraneous polling shows up as 'negative' PR/SM overhead if a CF is part of a CEC, rather than standalone, regardless of how it's defined (dedicated or shared). This would have been an RPQ to fix. Or, get outsourced to IGS and don't talk about it! - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
