Re: passing Call commands (with parms) from program to program

Hi

I admit I'm having a little trouble coming to terms with exactly what
your situation really is but (echoing other comments) it sounds to me
like a case of over-thinking something instead of re-thinking it.

Instead of submitting the job consider sending the second part of the
request to a dataq and use a server job to respond to the part that is
'too long to wait for".

You can then assign a priority in the job queuing the request, and/or
run additional servers and/or tune the server jobs as required. A
server job will also be far more efficient in terms of system
resources.

Either that or use the existing job description/job queue resources
better rather than taking what appears to be on the surface of it some
kind of brute force approach to job management.

On Thu, Oct 21, 2010 at 2:57 AM, Needles,Stephen J
<SNEEDLES@xxxxxxxxxxxxx> wrote:

Thanks Charles.  I'll look at Scott's Spawn (there is a joke in here somewhere :-) ), but I like your comment on using a DS.  I'll look into that.

The goal is to tune SBMJOB and CHGJOB parameters by Program to dynamically change the execution environment of Program_B throughout the day, without affecting other processes, and without having to change code at each "tune-up".

Program_A performs tasks that will take less than .15 seconds, but it submits the longer running portion to batch to keep the response time low.  So there may be many different Program_A's.

Program_B is the longer running process that is expected to be completed somewhere further down the transaction's process, but takes too long to wait for.

Program_X contains logic to retrieve data from a table that describes the SBMJOB parameters to use when executing Program_B.  It is the Submitter and is always called from whatever is representing Program_A at the time.

Program_Y contains more logic to use in a CHGJOB command to further describe the execution environment of Program_B.  Program_B is then executed from this program using the call string originally provided by Program_A.  This is the Executor.

I hope this makes the roles of each Program easier to understand.

-----Original Message-----