We run it and OBSERVER works quite well, thank you very much, without interfering with *MSG.
But while we're (obliquely) discussing OBSERVER, ISTR that early on we were told we could have multiple observers of a userid, but that hasn't appeared to be the case. Also I thought secuser and observer would both be settable on a userid, but that isn't true either. --Mike NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. The IBM z/VM Operating System <[email protected]> wrote on 08/19/2008 10:14:16 PM: > On Wednesday, 08/20/2008 at 12:50 EDT, Rob van der Heij > <[EMAIL PROTECTED]> wrote: > > On Tue, Aug 19, 2008 at 11:58 PM, Alan Altmark <[EMAIL PROTECTED]> > wrote: > > > > > Ah, one of the Great Schisms. See the 3rd from the last paragraph in > the > > > description of *MSG in the CP Programming Services book: > > > > What troubles me is that the folks in IBM who push the new automated > > operator product seem to have missed this part of their education. > > Apparently the documentation suggests that you can simply set secuser > > all over the place to manage virtual machines. And as we know this > > breaks the ability for the victim to process *MSG. > > I'll have to let someone who has factual knowledge of the product answer > that question. > > Alan Altmark > z/VM Development > IBM Endicott
