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. 

Thanks for your help 


Mark Garton
Information Systems
O'Reilly Auto Parts



message: 5
date: Wed, 8 Feb 2006 12:50:23 -0800
from: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
subject: RE: ICF Prestart Job 

Why do you need to detach / end all the time.  Change the target program
in to a NEPS, (never ending program/server).  This job can sit connected
to the remote system 24x7 and wait at a data queue for the next entry to
process.  Have the source program send a entry to the data queue, then
wait a the data queue for a reply.  The ICF program then only handles
passing the request down the ICF. 


Christopher Bipes
Information Services Director
CrossCheck, Inc.