Conference azur::mcc

1312.0. "Noname-W-Nomsg & Windows ACCVIO?" by KERNEL::MACLEAN (I CAN and I WILL...But Not today!) Mon Aug 05 1991 13:21

I have a customer who is seeing the following Scenario:-
    
EMS V2.0 running on a (standalone) 6410 with Vms 5.4-2 ...Customer is Set
Host via Decnet Across to the 6410 from  Vaxstn3100 (Vms Version still in
query),GKS is V 4.0  he believes(will verify this) and having  customized
workstation security is trying to do the following....I'm aware that the
latest V. of EMS is V2.1 but we have just got his EMS fully  installed after 
Resolving a number of customer Instalation (NMCC/RDB/ELMS )prb.s,and they 
are NEW/SENSITIVE customers........

$SET DISPLAY/CREATE/NODE=Nodename
$MANAGE/ENTERPRISE/INTER=DECWINDOWS
%NONAME-W-NOMSG, Message number 0326B180
%NONAME-I-NOMSG, Message number 03269393
%NONAME-I-NOMSG, Message number 0326939B
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000001E,
 PC=00247E38, PSL=03C00004
%SYSTEM-E-ACCVIO, access violation, reason mask=00, virtual address=0000000A,
 PC=0000000A, PSL=0000000F
$

Can anyone shed any light on exactly what message file in particular these
should be found in ,or what appears to be the problem.We have run the message
no.s through as many  Sys$message *.msg files as we could find but still no 
joy!! 

We discovered that If he just does a $MANAGE/ENTER  only, after doing 
$SET DISPLAY etc,this works Ok.. Any Help gratefully appreciated!!,

    Thanks In Advance,
    
			Sandie...
         
                        

It was my understanding that the iconic map interface, what you are trying to run
was NOT supplied in the v2.0 EMS kit; that is why you 
are having the problems. What exactly is giving the accvio beats me.
I will pass your request along, but it isn't in that kit (pretty
sure).

    Thanks for the speedy reply!!-I couldnt find an Old 2.0 SPD other than
    that in Note 426.7,However it looks as if you are right!!-Although 
    Previously I've seen an error  saying that a particular file couldn't
    be found,when you try to use the windows interface when the functionality
    wasn't there.I'm still interested in being able to find out what the 
    Nomsg messages mean/What caused the AccVio so thanks for passing the 
    request along
            
    Regards,
    Sandie.........

    Jill is correct.  The DECmcc SMS/EMS V2.0 kits include DECmcc BMS V1.0,
    which does NOT include the Iconic Map PM.  The SPD/SSA listed in 426.7
    should be fairly accurate.
    
    The current version, SMS/EMS V2.1, DOES include the Iconic Map, which
    is part of BMS V1.1.  The V2.1 SPD does document the included modules.
    
    Lisa 

remember that DECmcc doesn't own the MANAGE verb. If you do not specify the
/enterprise qualifier on the command, then you will go to RSM, it is my
guess that if mcc isn't there then it may still be going to RSM which
may not be handling the qualifier correctly.

jill