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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: AS/400 Internal Jobs CFINT01/02
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Fri, 7 Sep 2001 10:33:04 -0400
List-Archive: <http://archive.midrange.com/midrange-l/>
List-Help: <mailto:midrange-l-request@midrange.com?subject=help>
List-Id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-Post: <mailto:midrange-l@midrange.com>
List-Subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

>interactive job and every cpu second used by such a
>job will incur the wrath of cfint.

Semantic correction: every CPU second used by such a job counts toward the
interactive CPW workload.  CFINTxx won't pop up hard until the CPW threshold
is exceeded.  You can run all the interactive work you want _up to that
point_ without worrying about CFINTxx.  That's why Andy is noticing CFINT
now and not before.  His machine's interactive workload went up and "crossed
the line."

Buck

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.