Re: cfint 1, steve 0.

[Bob Larkin <blarkin@xxxxxx>]

CFINT will even get batch jobs! Personally experienced CFINT01,02,03,04 with 
each consuming 16% of CPU (Total 64%). ONE interactive job, mine running 
wrksysact. Culprit was a Domino job running code in a tight loop. It appears 
that CFINT is also used to restrict non-Domino work on the DSD line, which this 
box is. It
tought we were running a regular batch job, so it lowered the boom. IBM is 
working to properly identify the job so CFINT won't kick in.
Bob

> Steve Richter wrote:
>
> fyi,
>
> I tested my "batch job that opens a dspf is not interactive in the eyes of 
>cfint" theory.
>
> Conclusion:  You cant fool cfint!
>
> I will spare you all the gory details.  Basically, I ran a cpu consuming dspf 
>pgm on 5 5250 display stations from both batch and interactive jobs on a 
>server model 170.  In both modes, the pgm started out well but then cfint 
>became aware that there was some interactive computing going on and it lowered 
>the boom.
>
> Now if I could only find a system where I could test my "hook the sept and 
>intercept the calls to data mgmt" theory ...
>
> Steve Richter
>
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---