Re: ICF Prestart Job

There are 1500 different computers connecting to the one process that gets 
customer information.  And you are correct, the prestart job running but 
it isn't working correctly.  The target program is written so that should 
run forever, but it doesn't wait at the acquire.  It errors out on the end 
causing it to drop out of the Do forever loop and ends. So I am not 
gaining much from the prestart job. 

Thanks. 

Mark Garton
Information Systems
O'Reilly Auto Parts



date: Thu, 9 Feb 2006 07:29:13 -0800
from: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
subject: RE: ICF Prestart Job

So there are 1500 different computers connecting to one to process the
ICF data or is it all coming from the same computer but 1500 different
jobs?  Just trying to get a better idea of your environment.  It sounds
like you already have the prestart job running and accepting the ICF
connection but the program is not quite working correctly.  Am I on
track?


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
mgarton@xxxxxxxxxxxxxxx
Sent: Thursday, February 09, 2006 5:35 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: ICF Prestart Job

Chris,

That is essentially what I am trying to accomplish by using a prestart
job that can be used multiple times.  I have the ICF processing in a never 

ending do loop.  The problem is that when the program loops back up to
the acquire it doesn't wait on a new program start request, erroring out 
and
dropping out of the loop.  Then a new prestart job gets started.  I
don't want the prestart job to end and that is what I am trying to 
prevent.
This program gets hit 100,000's of times a day from 1500 different 
source/client systems which is causing a performance problem.  I was 
hoping I could it get to work properly with few changes without having
to rewrite the process.

******************************************