[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3546.0. "MCC 1.2, Accessing STATISTICS causes STACK DUMP" by CSC32::ORTIZ () Wed Aug 12 1992 13:34

    I have a guy out in the field that has a customer running MCC V1.2.
    Whenever he does a STATISTIC command through FCL a STACK DUMP is
    generated. For example, MCC>SHOW NODE4 nodename ALL STATISTICS, will
    cause a dump. If he does this in the ICONIC MAP the process is blown
    away.
    
    Has anybody seen this problem? Any help will be appreciated....
    
    Thanks
    RO
T.RTitleUserPersonal
Name
DateLines
3546.1QAR 3348TOOK::MINTZErik Mintz, dtn 226-5033Wed Aug 12 1992 14:143
Whoever looks at this will probably need more information, but
meanwhile, I have entered this note as QAR 3348.

3546.2More info on Statistics stack dumpODIXIE::PEACOCKRFri Aug 14 1992 16:1819
    I was the one on site.  The system is a VAXstation 4000 Model 60 with
    32 megs of memory, running 5.5 VMS.  I was executing DECmcc from the
    System account.  This system also has the Terminal Server AM and the
    ELMS AM installed.  As far as I could tell, everything else was working
    O.K.  I got no error messages before MCC went away.  I had used the old
    MCC_AUDIT.COM procedure to set system parameters, and the only thing
    that was well below the normal was the pagefile, which had been set at
    only 38,000 blocks.  We had run out of space on the systems disk and
    later moved the system to a RZ57 but did not go back and re-set the
    pagefile size
    
    I've been playing around in the office with both the 1.2 field test
    version and now the SDC 1.2 version on a woefully undersized Vaxstation
    3100 with 16 megs of memory running 5.4 and have never had this happen.
    
    I wish I could provide more info, but I didn't know where to look for
    any kind of logs or messages.
    
    Rick