Conference azur::mcc

557.0. "DECmcc performance graph procedure " by HERON::MORALES (DEC:.VBO.EIS.Telecom.DTN828-5383) Fri Dec 14 1990 10:49

		Hi DECmcc users,	

	With EFT 1.1 reports package, you can produce utilization graphs only
	from past data.
	For our demos in the ACT, we have written a DCL procedure 
	that reads the output from Performance Analyzer and produces a 
	"realtime-time"	performance graph (using DECgraph).
	I have tried it with several statistics attributes like	node4 packet
	rate, line utilization percent, bridge line filtered frames etc..

If you want to try it :

	in your sys$login, copy from WALNUT::DUA0:[PUBLIC] the 2 files
	GRAPH_MODEL1.GRG
	MCC_PERFORMANCE_GRAPH.COM

	1- submit in batch a PA command like

$ MANAGE/ENTERPRISE
SHOW NODE4 DUPOND PACKET RATE, AT EVERY 0:0:30,FOR START -0:0:0 DURA 0:0:15, -
TO FILE SYS$LOGIN:NODE4_PACKET.PERF

	2- Execute  MCC_PERFORMANCE_GRAPH.COM and give as P1 parameter
	the filename from PA (node4_packet.perf in that case),
	P2 is the number of samples you want on the display, P3 is the
	screen refresh rate.(P2 and P3 are optional as defaults exist).

 $ @MCC_PERFORMANCE_GRAPH.COM SYS$LOGIN:NODE4_PACKET.PERF 10 0:0:30

	this will produce an histogram of the node packet rate
	with 10 samples ( the window display shifts at every sample ) and
	the refresh rate is 30 seconds.
	To be able to read on the graph the time of the sample, P2 =20 is 
	the maximum, but you can use greater values.

	
	This is an example of what can be done using PA and DECgraph.
	You could also create an alarm on a threshold (line outilization for 
	example) and when the rule fires start an histogram on a window...


			Manuel.

    I had some trouble with this, but it is pretty good.
    
    1. I had interaction between the mcc and graph routines at the file
    level. Occasionally mcc would exit with an error. I modified the 
    graph command file to do an open/share (rather than open/read) 
    and read/nolock and it stays up for longer.
    
    2. I had a problem with DECgraph 1.6 on VMS5.3-1 on a workstation. It
    failed with file not accessable on channel. An assign/user of
    sys$command to sys$input before the graph command fixed this 
    (probably a GRAPH problem).
    
    	rgds,
    
    Dave McCallum.
    

	 Dave thanks for your inputs.

I have already been called for problem 2, this is related to DECgraph 1.6,
the procedure works fine with DECgraph 1.5 (that we used for the limited
testing we did).

There is a new command file in walnut::dua0:[public].

		Manuel.