[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

2265.0. "T1.2.4 - Notification - ILVTOOBIG problem" by WARDLE::REX (Life's not what I thought it was!) Tue Feb 04 1992 12:06

I am running T1.2.4 on a VS3100 VMS V5.5

I have enable 160 alarms polling Phase IV DECnet nodes & child entities 
& DECbridges, using 3 batch jobs with a 100 rule, 55 rule, 5 rule split.

The Iconic map is then introduced, along with the Notification services window.

I am displaying all levels of alarms except INDETERMINATE & CLEAR.

Before all of the alarms are enabled, I get the following message

** Window titled: Notify Request 1 for domain .top encountered an exception
** 
** Unexpected condition returned to Notification FM.
**
** MCC Routine Error: %MCC-E-ILVTOOBIG, no more room in buffer for additional 
** values

The polling continues, and alarms are registered, although the majority are 
exceptions where the entity has not reponded completely or at all to the alarm 
poll.

I this an issue that can be resolved with system parameter or process quota 
change ? Or a bug.

If this is a known bug, when is a fix due ? I wish to demonstrate the T1.2.4 to 
customers to give them a feel for what is coming this Spring with V1.2 SSB.

&^)

Rex
T.RTitleUserPersonal
Name
DateLines
2265.1QAR 2251TOOK::MINTZErik Mintz, DECmcc DevelopmentTue Feb 04 1992 13:392
QAR 2251.  Someone will post a reply here as well.

2265.2check sysgen quotasTOOK::CALLANDERMCC = My Constant CompanionWed Feb 05 1992 10:5712
    please check what you have set for the sysgen parameter gblsections
    it should be between 600 and 700 for events to work correctly
    with the v1.2 kit. 
    
    You should also have gblpages around 40000 and procsectcnt to about 64.
    Do these match your configuration?
    
    As to ilvtoobig, that one stumps me. It was entered by as a qar by Eric
    (mcc_internal #2265). 
    
    jill
    
2265.3Are you using OCCURS expression rulesTOOK::ORENSTEINWed Feb 05 1992 11:0111
    Are you using any OCCURS expression Rules?
    
    We do know of a buffer-size problem in displaying data that comes from
    the OCCURS kinds of rules.  The problem that we know of will be fixed
    for V1.2.  
    
    If you are not using the OCCURS expression Rules, we will need to in-
    vestigate.
    
    		aud...
    
2265.4Problem updateWARDLE::REXLife's not what I thought it was!Mon Feb 17 1992 07:0515
	RE: .2

I have increased GBLSECTIONS to 700, this has REDUCED th occurances of the ILV 
error although not removed them.

	    .3

No occurs alarms are operational, as I can not get the DECnet event process 
running !

		%*)

			Rex

2265.5is evl running is using dna4, check the logTOOK::CALLANDERMCC = My Constant CompanionTue Mar 10 1992 17:218
    I assume this means you did a reboot to get the new
    value. So why aren't occurs running, are you happening
    to run them against dna4 (node4) entities? some people
    are experiencing problems with the T1.2.4 DNA4 evl
    process. Have you validated that the event logger is
    up and running properly?
    
    
2265.6Upgraded to X1.2.15 - will try to re-createWARDLE::REXLife's not what I thought it was!Wed Mar 11 1992 12:5616
	Under T1.2.4 the MCC_DNA4_EVL process refused to start, it crashed
	with a bug that was "fixed in a later version".

	I have upgraded to X1.2.15 and MCC_DNA4_EVL is working, although I now 
	suffer the error as in note 2545.

	I will attempt to re-create this problem on X1.2.15, I hope to be 
	unsuccessful.

	Cheers,

	$*)

	Rex

2265.7ILVTOOBIG error message when enabling alarmsCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentTue Aug 10 1993 13:2810
    I have a customer who has seen the ILVTOOBIG error message when
    enabling alarm rules (only 12 of them).  What was the resolution for
    this problem?
    
    MCC V1.3, VMS V5.5-2, VAXstation 4000 M90, 64MB
    Resource settings mentioned in .3 are even higher on this customer's
    machine.
    
    Thanks,
    Dan