We are forced to aggregate disparate sysplexes into one sysplex. (Don't ask.)
We have a problem with system automation subplexing. The automation managers join two different groups, and via 'subplexing' only one of those groups' name can be changed (that name is ingxsg01 or 02 or whatever is specified as groupid). There is a second group named INGPX$$$ that is joined by only the HSAMs of both subplexes, not by the automation agents. Unfortunately, it is probably this connection that sends messages from one subplex to the other (where they really don't belong). Does anyone have an idea if it is possible to get the HSAMs not to do this? Definitely not send the messages but basically not join the same group. When I opened an ETR for this problem, IBM asked me why *I* had defined the INGPX$$$ group, which I certainly didn't. It will take a while until I find someone within IBM who even understands what I am talking about, so I thought I'd ask here. (I know there is a yahoo autmation group, but I find yahoo too nosy in the registration process.) Regards, Barbara Nitz -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail ---------------------------------------------------------------------- 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
