Tweet
In a customer case, a user program was trying to call in sequence two other programs needing different JVM settings.
As a result, the second call was bumping out.
There was a need to submit to a batch job the execution of the second program and to wait for its end before resuming process.
So we invented a technique called TIGHTLY SYNCRHONIZED JOB to have that done.
In another customer case, a user program was calling in sequence a number of other programs to compute the Company quarterly profit.
However, the elapsed time of this job was unacceptably long.
So we invented a technique called LOOSELY SYNCRONIZED JOB to run some parallel processing. The elapsed time was cut down to one half.
Then we though that other IBM i developers could take advantage from these techniques.
This is why we packed our code in a tool - SYNCJOB - now available from site http://www.easy400.net .
For more information, check out page http://www.easy400.net/syncjob/html/page1.htm .
Giovanni B. Perotti
As a result, the second call was bumping out.
There was a need to submit to a batch job the execution of the second program and to wait for its end before resuming process.
So we invented a technique called TIGHTLY SYNCRHONIZED JOB to have that done.
In another customer case, a user program was calling in sequence a number of other programs to compute the Company quarterly profit.
However, the elapsed time of this job was unacceptably long.
So we invented a technique called LOOSELY SYNCRONIZED JOB to run some parallel processing. The elapsed time was cut down to one half.
Then we though that other IBM i developers could take advantage from these techniques.
This is why we packed our code in a tool - SYNCJOB - now available from site http://www.easy400.net .
For more information, check out page http://www.easy400.net/syncjob/html/page1.htm .
Giovanni B. Perotti