Conference help::decnet-osi_for_vms

3983.0. "ACCVIO with NET$MOP.EXE , 6.3 ECO5" by AUBER::HO (Dung HO - TSC - France) Mon Jun 02 1997 11:28

 Hi,

 VMSVAX 6.1 , Decnet/osi 6.3 Eco 5

 Does someone know any %SYSTEM-F-ACCVIO problems with NET$MOP.EXE ?

 Do we have a more recent version of NET$MOP.EXE for Decnet/osi 6.3 ?

 Can he use the NET$MOP.EXE of DECnet-Plus ? Which has link date/time:
16-NOV-1996 02:14:39.66 

 Thanks for ideas,

    Youngy

*********************************************

 Customer has the NET$MOP.EXE version

                image name: "NET$MOP"
                image file identification: "V6.3"
                link date/time: 22-OCT-1995 03:00:49.43
                linker identification: "05-13"

 and found in the net$mop_output.log :

%%% Management #3 PC=0000C36B 28-MAY-1997 17:07:58.07 %%%
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=A22B0008,
PC
=0000C36B, PSL=03C00008

%%% Resignalling 28-MAY-1997 17:07:58.10 %%%
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=A22B0008,
PC
=0000C36B, PSL=03C00008

  Improperly handled condition, image exit forced.

 Signal arguments       Stack contents

 Number = 00000005   20040000
 Name   = 0000000C   00000000
   00000001   000BE778
   A22B0008   00000000
   0000C36B   21FC0000
   03C00008   000BE7CC
      000BE79C
      0000BE61
      00000048
      00000000

 Register dump

 R0 = A22B0008  R1 = 0010CA48  R2 = 0010C310  R3 = 00000000
 R4 = 00000005  R5 = 00000004  R6 = 000BE730  R7 = 00000000
 R8 = 000BE734  R9 = 00004720  R10= 0000041C  R11= 00005387
 AP = 000BE634  FP = 000BE5F8  SP = 000BE748  PC = 0000C36B
 PSL= 03C00008

    Hi Youngy,
    
    I looked quickly at MOP fixes post ECO5, although there have been many
    fixes that affect MOP, I did not see any obvious fix for this problem.
    
    It is not a good idea to copy other versions of MOP.  You may get a 
    version mismatch, and even if you don't you may have other problems 
    because MOP depends upon other images that may have changed.  
    
    I recommend that you submit an IPMT for this problem.  Include the 
    information you provided.  If you know of any MOP activities that 
    were going on at the time of the accvio, please include that 
    information.  Also, if you have reason to believe that anyone had 
    issued NCP Emulator commands at the time of the accvio, include
    that information as well because some NCP Emulator commands generate
    MOP management requests.  Another thing you should do is restart
    MOP on that machine, issue the following SDA command:
    
    SDA>show proc/image net$mop
    
    to include that output in the IPMT.
    
    I suggest that when the ECO7 kit becomes available (this should
    happen within the next week or two), have the customer apply that
    it.  There will be many MOP/Process EMAA problems fixed in that kit.
    
                                    - LL