Re: AS/400 Internal Jobs CFINT01/02 -- MIDRANGE-L

Andy,

An explanation of cfint follows, but I am interested in knowing how you and
your dept came to be running such a system and what your response will be
now that you know you will not be able to use your system as you would like.


The cfint cpu wasting jobs are intended by ibm to slow down your system. Ibm
traditionally sold high priced as400 that could support many interactive,
terminal based users at the same time, with the price per user actually
being reasonable.

When much faster as400 servers were introduced to run a client/server NT
like work load ( serving web pages ), ibm also brought out the cfint task on
those systems to prevent the users of the $100k+ interactive as400 from
upgrading to the faster $30k client server systems.

Serving a web page or ftp'ing a file is considered a batch job ( no cfint
penalty ). Signing on to the 400 thru a telnet session or twinax device is
considered an interactive job and every cpu second used by such a job will
incur the wrath of cfint.


Steve Richter


-----Original Message-----
From: ajeffery@bacardi.com <ajeffery@bacardi.com>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Friday, September 07, 2001 9:21 AM
Subject: AS/400 Internal Jobs CFINT01/02


>We have response time issues when the above internal jobs kick in.
>I believe these jobs allocate resource from interactive jobs and assign
>to Batch jobs(apparently our AS/400 is biased to Batch processing).
>Is there anyway of controlling these jobs? i.e. Thresholds etc?
>
>The Interactive sessions get priortised to around 89 and the Batch Jobs 20.
>Note that the CFINTxx jobs do not appear within WRKACTJOB.
>
>Any assistance would be much appreciated.
>
>Andy
>
>===========================================================================
===
>                          Work with System Activity
>                                                            07/09/01
14:07:31
>Automatic refresh in seconds  . . . . . . . . . . . . . . . . .      5
>Elapsed time . . . . :   00:00:02        Average CPU util . . :   95.8
>Number of CPUs . . . :   2               Maximum CPU util . . :   98.9
>                                         Minimum CPU util . . :   92.6
>Type options, press Enter.
>  1=Monitor job   5=Work with job
>                                                          Total  Total
>     Job or                                          CPU   Sync  Async
PAG
>Opt  Task        User        Number  Thread    Pty  Util   I/O    I/O
Fault
>     CFINT01                                     0  44.6      0      0
0
>     CFINT02                                     0  42.1      0      0
0
>     WH_PCKLST1  xxxxxxx     886685  00000036   23   1.3     60    188
0
>     QPADEV01GH  xxxxxxx     885865  00000058   89   1.1      2      1
0
>     QPADEV01DZ  xxxxxxx     885650  00000014   89    .7     93      0
0
>     GLUPDATE    xxxxxxx     875943  00000001   30    .6      0      5
0
>
>     QPADEV01D5  xxxxxxx     886722  00000019    1    .5      1      0
0
>
>     QPADEV01FL  xxxxxxx     885697  0000001D   20    .1     15      2
0
>===========================================================================
===
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>
>