Conference azur::mcc

6032.0. "SYSTEM-E-EXQUOTA messages only during STARTUP" by CUJO::BROWN (Dave Brown) Thu Jun 23 1994 16:34

    
    	I have been working a problem with a customer for the last few days
    which seemingly has no resolution. Anytime MCC_STARTUP_BMS is called
    from SYSTARTUP_V%.COM, the following error occurs:
    
    	(excerpt from MCC_STARTUP_BMS)
    
    		.
    		.
    		.
    $!		Enroll the Director Management Modules
    $		ON ERROR THEN $GOTO DISPATCH_SET_PROT
    $		manage/enterprise/presentation=mcc_fcl_pm
    DECmcc (v1.3.0a)
    
    		do mcc_system:mcc_enroll_dir.com
    		do mcc_system:mcc_enroll_bms.com
    SYSTEM-E-EXQUOTA, exceeded quota
    SYSTEM-E-EXQUOTA, exceeded quota
    		create mcc 0 alarms rule __dummy_test expr=(sample foo user
    bytes sent = 50), proc=nl:
    %DEBUGBOOT-W-EXQUOTA, exceeded quota
    %CMA-F-EXCCOP, exception raised; VMS condition code follows
    -SYSTEM-F-INSUFMEM, insufficient dynamic memory
    		.
    		.
    		.
    
    	As said above, THIS ONLY OCURRS DURING STARTUP. If MCC_STARTUP_BMS
    is run interactively once the system is up, this problem does not
    occur. I have checked every SYSGEN and UAF parameter conceivable and
    raised some of them to obscene values and still this problem ocurrs.
    This problem is ocurring on a system that I am helping the customer
    build, hence that is why we noticed the error messages; we were paying
    attention to the STARTUP output.
    
    	This problem started when the customer copied the MCC dictionary
    filed from another system to this system. The customer likes to perfom
    dictionary updates on one system then propagate the ditionary files to
    the other systems which run MCC. Historically, this has worked just
    fine.   
    
    	We tried going back to the system on which the customer updates and
    distributes the MCC dictionary, rebooted it, and it got the same error
    (guess no one ever paid attention to the output before...). Also tried
    this on the system we maintain on site and we got the error above with
    14 exceeded quotas and a couple ACCVIOs.
    
    	We noticed that some of the systems only have one *stack*.com file
    and others have three. These are the files which set the MCC stacks via
    logicals to certain values. What should these *stack*.com files
    contain? Is their content relevant to this problem?
    
    	Has anyone seen a problem like this before?????
    
    	Thanks,
    
    	Dave  

    
    
    	We have worked around this problem by submitting the starting of
    MCC to a batch job rather than running it inline in SYSTARTUP_V5. The
    only place this error ocurrs is when MCC is started up within
    SYSTARTUP_V5.