| >1. SHOW NODE4 from FCL returns the error message
> "Node does not support this system-specific operation"
Not an MCC bug, it's DECnet/OSI. See note 4011.
>2. An "Access Control Violation" event is generated periodically on my system
> where I have defined an "Event Dispatcher Outbound Stream MCC_STREAM" with
> "Sink End User = Name = MCC_EVL_SINK", and I've setup the PhaseV MCC sink
> with "MCC> ENABLE MCC 0 DNA5_AM SINK". The "Session Control Application
> MCC_EVL_SINK" is created by the ENABLE statement, and specifies "Outgoing
> Proxy = True" and "Incoming Proxy = True". When setting these parameters
> to "False" the event not generated anymore.
I don't know why the event is being generated by Session Control, please
ask the DECnet/OSI folks. One thing you could do in the meantime is to
modify your NCL startup script to set the proxy fields so that the events
don't get generated like so.
create session control application MCC_EVL_SINK
set session control application MCC_EVL_SINK address={name=MCC_EVL_SINK}
set session control application MCC_EVL_SINK Outgoing Proxy = FALSE
set session control application MCC_EVL_SINK Incoming Proxy = FALSE
>3. Autoconfigure does not work because of syntax-error when checking DNS for
> existence of directories specified in the MCC_AUTOCONFOG_PREFIX.DAT file.
> This problem is documented in a previous note.
This is probably the problem where DNS changed syntax in V2.0 and that
broke applications.
>I'm in a situation where I NO longer can demonstrate DECMcc from my WS, running
>DECnet/OSI in a standard fashion.
Hopefully the above answers will retract that statement. I run DECnet/OSI
_and_ MCC in a "standard" fashion on my workstation quite successfully,
as do others which I have come in contact.
|
|
>I don't know why the event is being generated by Session Control, please
>ask the DECnet/OSI folks. One thing you could do in the meantime is to
>modify your NCL startup script to set the proxy fields so that the events
>don't get generated like so.
>
>create session control application MCC_EVL_SINK
>set session control application MCC_EVL_SINK address={name=MCC_EVL_SINK}
>set session control application MCC_EVL_SINK Outgoing Proxy = FALSE
>set session control application MCC_EVL_SINK Incoming Proxy = FALSE
I don't want to create my own NCL script file for this. DECmcc is generating
the Session Control Application MCC_EVL_SINK for me, and therefore I expect
DECmcc to do it the right way. PLEASE create the MCC_EVL_SINK correctly.
>
>This is probably the problem where DNS changed syntax in V2.0 and that
>broke applications.
>
Well, it's been almost 6 months since I raised the question about DECmcc
running well on DECnet/OSI. The answer was YES, no problem. Who's cheating who?
The answer is in this notesfile somewhere, I don't remember where, but it's
quite fantastic to get such an answer and after installation I find that the
DECmcc system no longer won't be able to do the job.
I wonder how I should have done it to not get into these problems, and I find
it VERY strange that noone else is seeing this.
Bj�rn Olav
|