Conference azur::mcc

6059.0. "Again & again mcc-e-insevtpoolmem to post event VMS 6.1" by VNASWS::ANDREAS () Wed Jul 27 1994 09:07

Problem:
	
	
	Configuration: Vaxstation 4000/90a
			over 100 MB memory
			2 disk a 2GB diskspace
			Vax/VMS V6.1

	after starting mcc via iconic map (system account) and
	opening a map manually I got to pop up windows with the
	following error message:

	mcc-e-insevtpoolmem to post event
	INSUFFICIENT POOL MEMORY TO POST EVENT

	After clicking these windows away all functions within mcc
	work properly. Exept all wich have to do with notification.
	I cant get working any notification abilities or features.

	After starting mcc via iconic map (using an mcc account)
	the iconic map crashes after serveral seconds without any other 
        message.  

	The only different between these two methodes is that the mcc 
	account have a default map specified to open automaticly.

	Mcc_audit.com work well on both accounts.

	I have also checked or installed:


	GBLPAGES >40000
	GBLSECTIONS >=600

	New images installed (from patch directory Robert Krause):

        Mcc_dna4_am.exe
	   _tcpip_am.exe
	   _notification_fm.exe
	   _pa_fm.exe
	   _concentrator_am.exe
	   _iconic_map_pm.exe 
	   _tcpip_mq_exe
	   _tcpip_mtu.exe
	mccmscmsg.exe
	mcc_msl_main.exe 

	
	The kernel-patch ECOXXX is also installed and I have also tried
	the fix mentioned in ECOXXXX.readme with the values of 40,50,60,70 and 		
        80.(mcc_notif_getevent_tss)

	The problem occours also when the dna4,dna5,evc-processes are
	not running.

	Same problem also if DEcnet phase IV or V are installed. 

	ANY OTHER IDEAS OR FIXES YET ?

-ANDY     	 	 

After doing a quick "dir/title=pool", I have to ask:
    
    "Did you look at note 5490 ?"
    
    Account params or sysgen params will have NO effect on the mcc event
    pool.  If I remember correctly (I've been away from the guts of MCC for
    a while), once you've run out of event pool (for whatever reason) you
    have no way to clear it except via a system reboot.
    
    /doug

	Doug,

	I did a quick "dir/title=pool" but found no answer to
	my specific problem.

	I posted all parameters just to get sure.

	-Andy

>	I did a quick "dir/title=pool" but found no answer to
>	my specific problem.

  After reading note 5490.*, I would've had a go at increasing
  MCC_EVENT_POOL_SIZE and MCC_EVENT_EDQ_SIZE_LIMIT, and seeing if that
  changed things (for better or worse).
  
  How many Notify requests do you typically have outstanding ?
  
/doug 

Also, please don't just rely on this notes file to fix your problem.  
If you still have problems, use the established support procedures outlined
in note 7.last.  

regards,
/doug