The cause is what in my eyes is a very old bug, it exists since the VM/XA days; VM/SP had it right: in the VM/XA family, when a disconnected user, without a secondary user, causes a VM READ, it is translated into a CP READ With SECONDARY user one can correct the problem: SEND a BEGIN command With OBSERVER one is stuck: one can send a BEGIN, but the following VM READ is again translated in CP READ. If that could be fixed... Or am I dreaming too much
2010/3/3 Alan Altmark <alan_altm...@us.ibm.com> > On Wednesday, 03/03/2010 at 12:04 EST, Steve Marak > <sama...@gizmoworks.com> wrote: > > We've seen these additional differences between SECUSER and OBSERVER > > processing - > > > > Secondary user sees message HCP150A when the primary is disconnected and > > VM or CP read is issued, observer does not. > > > > It doesn't appear that an OBSERVER, even with class C SEND, can satisfy > a > > VM read issued by a disconnected user. On our system, the SEND is > honored, > > but everything is processed by CP on the target user, whereas with > > SECUSER, the input is passed to the guest unless sent with SEND CP. > > > > I know that's poorly worded. Example: > > > > USERA has USERB as SECUSER, is disconnected, RUN ON, and issues a VM > READ. > > USERB (with or without class C) does "SEND USERA Q DISK" and sees the > > normal CMS Q DISK output. > > > > USERA has USERB as OBSERVER, is disconnected, RUN ON, and issues a VM > > READ. USERB (who has class C) does "SEND USERA Q DISK" and sees > > "HCPCQV003E Invalid Option - DISK". > > On my system, I don't get any output at all; the command simply goes into > the target user's console input buffer. Subsequent SENDs get RC=36 > "console input waiting" (aka NOT ACCEPTED) and I have to SEND CP USERA > ATTN to the guest to process the command QUERY DISK. (I don't get > HCP003E, implying equivalent of TERM MODE CP on the target.) It all works > fine with SECUSER, though I get the same no-output problem on the first > SEND after I turn off OBSERVER and turn on SECUSER. > > As far as failing to get HCP150A, that is somewhat ambiguous. As with SET > OBSERVER, the SET SECUSER command does not document that one could expect > to get HCP150A, but it is mentioned on CP SEND as the impetus to issue the > SEND. It gets a little stranger since OBSERVER works with a connected > user, but HCP150A is issued only when the primary is disconnected. > > I think a call to the Support Center is in order. IMO: > - HCP150A should be sent to an observer as well as to a secondary user > - HCP150A should be send to an observer even if the primary is logged on > - The results of a class C SEND should be the same whether you are > observer or secuser > > Alan Altmark > z/VM Development > IBM Endicott > -- Kris Buelens, IBM Belgium, VM customer support
