s ^L= 1  j a
 f c= 1 : 1  q:'^L h  0 . 1 
 zwr  q 
a h  2  s ^L= 0  q

 f  r *q: 0  j a h  0 . 1 
 zwr  q 
a ;Здесь помещается обработка.
 ;Длительность процесса не должна превышать тайм-аут
 ;для данного случая  0 . 1  сек+время выполнения комманд FOR , READ и JOB
 q

 f  q:'^j  h  0 . 01 

View

The VIEW command adjusts an environmental factor selected by a keyword argument. For example, VIEW controls journal buffer flushing, determines whether GT.M reports undefined variables as errors or treats them as null, and determines which BREAK commands should display messages.

.....

"TRACE":value:<expr>

Traces GT.M program execution and generates profiling information about the lines and functions executed; with low impact on the run-time performance.

The feature turns on (value= 1 ) or turns off (value= 0 ) tracing. <expr> must evaluate to a string containing the name of a GT.M global variable. The global may also have subscripts; however the subscripts must be literals or the special variable $JOB. Refer to the "Intrinsic Special Variable" chapter in this manual for process identifier description. 
Thus, if the GT.M program lv1.m is:
 
lv1	f i= 1 : 1 : 10  d 
	.s l(i)=i 
	.d bar 
	for i= 1 : 1 : 5  for j= 1 : 1 : 4  s lij(i,j)=i+j 
	q 
bar	s l(-i)=-i 
	q 
 
And the program lv2.m is:

lv2	VIEW "TRACE": 1 :"^lvtr" 
	d ^lv1 
	VIEW "TRACE": 0 :"^lvtr" 
	zwr ^lvtr 
	q 

On executing lv2, the output looks like this (times in the example were chose for clarity of illustration and are not typical):

^lvtr("lv1","bar")="10:8:1:9" 
^lvtr("lv1","bar", 0 )="10:5:1:6" 
^lvtr("lv1","bar", 1 )="10:3:0:3" 
^lvtr("lv1","lv1")="1:37:2:39" 
^lvtr("lv1","lv1", 0 )="1:8:0:8" 
^lvtr("lv1","lv1", 0 ,"FOR_LOOP", 1 )= 10  
^lvtr("lv1","lv1", 1 )="10:3:1:4" 
^lvtr("lv1","lv1", 2 )="10:19:2:21" 
^lvtr("lv1","lv1", 3 )="1:15:0:15" 
^lvtr("lv1","lv1", 3 ,"FOR_LOOP", 1 )= 5  
^lvtr("lv1","lv1", 3 ,"FOR_LOOP", 2 )= 20  
^lvtr("lv1","lv1", 4 )="1:0:0:0" 
^lvtr("lv2","lv2", 1 )="1:47:3:50" 

In this case, ^lvtr("lv1","bar", 0 )="10:5:1:6" means that the statement bar s l(-i)=-i was executed  10  times, with a total of  5  microseconds of user time and  1  microsecond of system time. ^lvtr("lv1","lv1")="1:37:2:39" means that  37  microseconds of user time was spent within that GT.M frame (lv1^lv1), and does not include time spent in routines called from it (such as bar^lv1), whereas ^lvtr("lv1","lv1", 3 )= "1:15:0:15" includes the time spent at bar^lv1.

Note that there is no data in ^lvtr("lv2","lv2", 0 ) or for ^lvtr("lv2","lv2", 2 ) because the execution of the lines containing the VIEW commands that turn profiling on and off are not profiled.

Because of the underlying timers provided by the operating systems, times of less than a microsecond are measured as zero. Therefore, even if a statement executes one million times, it may report zero time if it took less than a microsecond each time.

The ANSI/MDC X11. 1 - 1995  Standard explicitly defines
    _hangargument_ ::= _numexpr_
and
    _timeout_ ::= : _numexpr_

Your implementation might round or truncate the _numexpr_ to an
_intexpr_ but the language itself has no such constraints. 

Check out the GT.M provided functions provided by calliing out to C
(Programmers Guide at http://www.fidelityinfoservices.com/user_documentation/GTM-PG-UNIX44/...
and look at the functions hiber_start, hiber_start_wait_any,
start_timer and cancel_timer).  But also remember that unless you are
running a real time Linux kernel, you may not get the timing accuracy
you want (there is an important difference between resolution and
accuracy).

Regards
-- Bhaskar
ks dot bhaskar at fnis dot com <-- send e-mail here