[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

4008.0. "Interval Time Scope of Interest : Where ??" by TAEC::HAYES (Tu quoque mi fili ! C.Hayes SVP @VBE) Mon Nov 02 1992 12:35

Hello ,

Do you know if it is possible to get the information given in the Interval Time for 
Absolute Scope of Interest from the input parameters to a FM? 
I have tried, but I didn't manage to do it. 
The Scope of Interrest Time (duration) is easy to find in the 
Time_Spec parameter, but not the Interval Time.


Could someone from the kernel, historian or performance
analyzer team help here ??


	Thanks to answer



		Catherine
T.RTitleUserPersonal
Name		DateLines
4008.1Repeat Interval reverse mcc_ats_link ??TAEC::HAYESTu quoque mi fili ! C.Hayes SVP @VBETue Nov 03 1992 09:5454

	
	hello,



Let me give some more background to this question.

My customer is trying to build a performance FM.

In the Iconic Map PM V1.2, in the scope of interest time window
there is duration to specify and "Repeat Interval".

I guess this "Repeat Interval" is what is called the Periodicity
in the SRM.

The periodicity is present when we want to encode a timeframe
using mcc_ats_link as the seventh parameter.

But, it is not present when we want to decode this parameter
using mcc_ats_get_first or mcc_ats_get_current...

Thus, is there a way/routine to decode this periodicity in order to manipulate
it in my own code ? What way/routine ? 

If not, is there a work-around we could advise, like to do two
mcc_ats_get_first (begin time) and mcc_ats_get_next (begin time)
and substract those two (which is not very clean).

  




	   status = mcc_ats_link(
				    p_call_params->p_timeframe,
				    &k_ats_schedule,
				    &k_ats_abs,
				    p_begin_time,
				    &k_ats_abs,
				    p_begin_time,
				    p_interval_time,
				    p_end_time);    
		


	Thanks to help



		Catherine
4008.2use your ugly workaround for nowTOOK::T_HUPPERThe rest, as they say, is history.Tue Nov 03 1992 11:1623
    
    
    
    (also answered via MAIL)
    
    There is no available routine to extract the periodicity of a scope of
    interest (or schedule, for that matter).  The mechanism of using
    mcc_ats_get_first, then mcc_ats_get_next is the only method we have at
    this time.  This method works if only a single "start" time is
    specified for the scope of interest.  If multiple "start" times were
    specified, the recipient of the scope of interest cannot readily
    distinguish between intervals caused by the several "start" times and
    those caused by the "periodicity".  Note that mcc_ats_link does not
    allow time elements of different "periodicity" to be entered into a
    time_frame, so only a single "periodicity" needs to be determined.

    If a routine to disassemble a time frame (call it "mcc_ats_unlink") is
    required for your application, it would have to go through the ECO
    process to be included in a release after V1.3.  We have no plans for
    such a routine in V1.3, which is entering FT very soon.  
    
    Ted