On Tuesday, 03/02/2010 at 12:13 EST, zMan <zedgarhoo...@gmail.com> wrote:
> On Tue, Mar 2, 2010 at 9:01 AM, Alan Altmark
<alan_altm...@us.ibm.com>wrote:
> So that you get the equivalent of SET OBSERVER instead of SET SECUSER.
>
> I think he meant, "What use is it?"
>
> The answer is that it's (sort of) a R/O SECUSER: you see the output but
you
> can't do a CP SEND back. And OBSERVER output isn't quite tagged the same
as
> SECUSER output (which I discovered to my frustration when it first came
out).
Off the top of my head:
Secondary user
- Can use CP SEND to the primary
- Only sees console output of primary when primary is disconnected
- Class G secondary can SEND only when primary is disconnected
- Class C secondary can SEND at any time
- Traffic to primary's *MSG connection is stopped while secondary is
logged on
Observer
- Cannot SEND to the observed virtual machine ("observee")
- Sees all console traffic without regard to connect/disconnect status of
the observee
- Does not interfere with observee's *MSG traffic
And as you note, the programming characteristics via *MSG are different
for the observer and the secondary user.
Alan Altmark
z/VM Development
IBM Endicott
