Conference csc32::consolemanager

1305.0. "PCM v1.6-211 Access Violation when reconfiguring after deleting a group." by MARVEL::BARTLETTD () Fri May 24 1996 06:21

Hi All,

I have a customer with the following configuration;

   Alpha Server 2100
   OpenVMS Alpha v6.1
   PCM v1.6-211

He has a group of machines called VMS STANDALONE MACHINES.  When he tried to
find a system from the main C3 interface and then selected the system, a C3
message box is displayed saying "System not found".  I did notice that
in the Locate System Message Window (after pressing Find on the C3) the group
name is not complete it says <system name> [VMS STANDALONE M].    

To get around this problem the customer deleted the group using the editor
(C3 interface editor), saved the database and reconfigured PCM.  The C3 window
dissapeared.  Because the customer was running this as a detached process he
received the following access violation in the log file.

POLYCENTER Console Manager
Eventlist Version V1.6-211
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved
Copyright (c) 1995 Digital Equipment Corporation. All Rights Reserved


%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00103085,
PC=80409C14, PS=0000001B
  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00000000
                                 00103085
                                 80409C14
                                 0000001B

    Register dump:
    R0  = 000000007FB90000  R1  = 0000000000103089  R2  = 000000007FE54E00
    R3  = 00000000000E0044  R4  = 0000000000000000  R5  = 0000000000C22CD0
    R6  = 00000000003CF278  R7  = 00000000003CF278  R8  = 0000000000000000
    R9  = 0000000000C0FB58  R10 = 000000007FF9D198  R11 = 000000007FFBE3E0
    R12 = 000000007F94FB58  R13 = 0000000000026DC0  R14 = 0000000000000000
    R15 = 0000000000000000  R16 = 0000000000103089  R17 = 000000007FB90008
    R18 = 00000000002000E0  R19 = 00000000002000E8  R20 = 00000000002000F0
    R21 = 0000000000000000  R22 = 00000000002000C0  R23 = 0000000000000000
    R24 = 0000000000000000  R25 = 0000000000000001  R26 = FFFFFFFF80571A84
    R27 = 000000007FB52B60  R28 = 00000000007D16D0  R29 = 000000007F94E750
    SP  = 000000007F94E730  PC  = FFFFFFFF80409C14  PS  = 300000000000001B

The C3 interface would not start, in detached login mode, errors follow;

C3: Message log file cannot be opened
C3: Message log file = sys$login:CONSOLE$C3_TREVOR_msg.log
C3: no such device or address

But it does run from the command line.

After renaming the CONSOLE$ROOT:[DATA]CONSOLE_CFG.DAT file and
restarting PCM the customer was able to run a c3 again.


After talking to the customer, I asked him to take the same actions after
starting the c3 interface diretly from the $ prompt.  After
the re-configure the following access violation was experienced; 

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=70757002,
PC=0005282C, PS=0000001B

    Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00000000
                                 70757002
                                 0005282C
                                 0000001B
    Register dump:
    R0  = 0000000000000000  R1  = 0000000000BF63A0  R2  = 0000000000011750
    R3  = 00000000000E0044  R4  = 0000000000000000  R5  = 0000000000BF23D8
    R6  = 0000000070756F72  R7  = 0000000000BF9560  R8  = 0000000000000000
    R9  = 0000000000BF5480  R10 = 000000007FF9D198  R11 = 000000007FFBE3E0
    R12 = 000000007F94FB58  R13 = 0000000000026DC0  R14 = 0000000000000000
    R15 = 0000000000B099B0  R16 = 0000000000000001  R17 = 000006CD00C76A88
    R18 = 000006CD00BF63A0  R19 = 000000007FB907E8  R20 = 0000000000B836C0
    R21 = 00000000000002DF  R22 = 0000000000B34818  R23 = 0000000000000000
    R24 = 0000000000000000  R25 = 0000000000000000  R26 = 0000000000052B18
    R27 = 000000007FB907E8  R28 = 0000000000669B2C  R29 = 000000007F94F4E0
    SP  = 000000007F94F4E0  PC  = 000000000005282C  PS  = 200000000000001B

I have tried to reproduce the problem at the CSC, but I don't have PCM
installed on an Alpha running 6.1.  We use PCM with OpenVMS VAX v6.2.


Can anyone help?

/Dave B.

    You need to IPMT this problem as the version you are running is
    V1.6-211 which is something you (or someone at your site) got from
    engineering! ECO2 is V1.6-201. Also were you running the ECO2 level on
    your VAX system or did you hav the -211?
    
    Regards,
       Dan

Hello Dan,

Yes, I did get the v1.6-211 kit directly from engineering to solve the ECO 2
archive problem.  We are also running PCM v1.6-211 here at the Customer Support
Centre.  I will IPMT this issue.


Thanks for your help.

/Dave B.