• See if below way works for you -

    The concept I worked on long ago in one of my assignment was we created a control table which will maintain list of batch jobs, predecessors, scheduled run, last run and whether jobs are currently active or not.. We then created a SSIS package that will keep executing every 5 mins and scan this control table to see which job needs to be pulled in to execute. Any job whose predecessor has run for current date and has scheduled time arrived/already passed, we used to kick off that job.

    In your case, you can have them update last execution time into the control table and your SSIS package running every 5 mins will do the job of triggering the next package which qualifies execution criteria. This control table can also give you flexibility if you want to hold any run by just updating flags etc.. you just need to design control table as per your requirement and use conditions in SSIS package.

    Here is sample table that we used to do -

    Job Name Predecessor LastRunScheduledRunJobActive Frequency

    ANULL07/10/2013 11:00:00 AM10:45:00 AMYDaily

    BA07/09/2013 11:35:00 AM11:30:00 AMYDaily

    :rolleyes: