Hi Kelly,
Do you have lots of jobs that are by themselves or independent of other jobs?
There are several ways to create a last job in DE. You can use a LINK job at the end. All jobs (and job streams) can point to this last job as successor.
You can also look into Global Variables, and create a job dependency, see
here.
HTH,
Nitin Pande
------------------------------
Support
Broadcom
Toronto
------------------------------
Original Message:
Sent: Sep 22, 2022 11:37 AM
From: Kelly Sanchez
Subject: Successor to all Workload Objects in Application
Thank you Nitin but this application has many jobs and depending on the time of day, the last job will vary. I can define everything as a pred. I was just looking for an easier way.
Original Message:
Sent: Sep 22, 2022 08:55 AM
From: Nitin Pande
Subject: Successor to all Workload Objects in Application
Hi,
So in DE, there are several dependencies that can be used. For a job to run at the very end, you can create a dependency between jobs, and put the last job at the very end.
HTH,
Nitin Pande
------------------------------
Support
Broadcom
Toronto
Original Message:
Sent: Sep 21, 2022 09:17 AM
From: Kelly Sanchez
Subject: Successor to all Workload Objects in Application
On the mainframe, CA Workload Automation ESP Edition r12.0.00, has a statement "APPLEND' that executes automatically after all other workload objects have completed except workload objects that are successors to APPLEND. Can anyone in the dSeries community advise if there is a comparable statement in dSeries? I have a large dSeries application where I want all jobs to complete before a job is executed.