Successor release after 3 gens of Predecessor

[Loren Watts]

Is there logic to have my successor appl wait until ESP sees its predecessor has completed 3 generations?

My customer says the predecessor has to run several times in order to build up the volume needed for the successor to process.

------------------------------
Loren Watts
Cigna Healthcare
------------------------------

[Chris_Elvin]

The method that springs to mind here would be to use a THRESHOLD resource

Initially set to zero and incremented at the end of application A, the jobs in application B would have a dependency on the threshold resource value and so could not run until the resource has reached a certain value.

Once application B is running, one of its jobs could either reset or decrement the value of the resource.

To prevent multiple generations of application B waiting on the resource, you could set the event for B to "Do Not Trigger If Active" or else add a mechanism to either WITHDRAW or COMPLETE application A if it is waiting on the resource.

------------------------------
Thanks in advance
Chris
------------------------------

[Loren Watts]

Hello Chris. The THRESHOLD idea sound like it might fit.  Thank you for your help.

------------------------------
Loren Watts
Cigna Healthcare
------------------------------

[Chris_Elvin]

No problem Loren,  I am here to help.

Another thought just occurred:  How about having the downstream application be manually triggered by the upstream one only when sufficient data is available?

If you need any more help, feel free to contact me

------------------------------
Kind Regards
Chris
------------------------------

[Lucy Zhang]

Hi Loren,

Obviously the ESP external JOB can't be matched to 3 generations of the home application.

Can the 3 runs be put into the same application A? If yes, then the 3rd run (like A.THREE) can be specified as external in application B.

Note: TEMPLATE can be used to avoid duplication.

If not, is there a way to tell which run is the final run? If yes, then in the final run, the command like below can be issued to release the application B from APPLWAIT:
JOB A
<IF it's the final run> THEN -
ESPNOMSG AJ ALL APPL(B) UNWAIT
...
ENDJOB

APPL B WAIT NOPOST_WHILE_WAITING
JOB A EXTERNAL APPLID(A)
...
REL B
ENDJOB

JOB B
...
ENDJOB

Other than external JOB, resources and global variables can be used to control workloads in different applications. Chris provided a very good method using resources.

Hope this helps,

Lucy

[Loren Watts]

Thank you for the ideas Lucy

------------------------------
Loren Watts
Cigna Healthcare
------------------------------

[Lucy Zhang]

Hi Loren,

You are welcome!

If more specific details can be provided, we can help to come up with the best solution.

Regards,

Lucy