On Tue, Mar 2, 2010 at 12:32 PM, Alan Altmark <alan_altm...@us.ibm.com>wrote:
> 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.
Thanks. I hope it didn't sound like I thought OBSERVER was broken -- my post
was just to hopefully help others not make the same assumption I did, that
it was JUST a R/O SECUSER. It's a nice facility.
--
zMan -- "I've got a mainframe and I'm not afraid to use it"
