Box Job Stuck Running

[ca.portal.admin]

I have a set of task that get performed at different times Mon-Sat then on Sunday.   I have put those task in a box but see no way to create my different Mon-Sat times then Sunday.   To avoid duplicating the box with my task I start my box based on successful completion of other box jobs.   I   have two dependencies with an or condition that starts the box, so no schedule on the box with the task in it.   The box jobs that my box is dependent on are two other Box jobs that have no task in them but do have a schedule.   One box job has my Mon-Sat schedule and then the other my Sunday schedule.   Everything works fine but on rare occasion the empty boxes that I use for the schedule  get stuck running and I am forced to kill them so they can run again.   Further more their last run time that got stuck I can see that the dependent box job that runs my actual task did run.   So it is like some of autosys thinks the 'empty box job' completed and some of autosys thinks it did not.   Why would this be ?   Am I asking for trouble with these empty boxes I am using ?   Is there a different way to get the schedule to run on different times Sunday than the rest of the days without duplicating the entire box with my task in it ?

[Anon Anon]

This sounds like it should just work.   The empty box jobs should not become stuck in RUNNING status.   This assumes that you have not defined any box_success conditions for the empty box jobs.Did you trawl through your scheduler log to see if any further errors were logged there?

[ca.portal.admin]

Looking in the log file named event_demon.... I see that the empty box starts,   next second it shows running, next second it shows success.   Then the job runs that is dependent.   Then next time comes around 24 hours later in this case and the empty box does not run as it should since it still shows as running from previous.   Nothing in this log other than the above for this set of jobs.

[Joseph Poutre]

ca.portal.admin wrote:

Looking in the log file named event_demon.... I see that the empty box starts,   next second it shows running, next second it shows success.   Then the job runs that is dependent.   Then next time comes around 24 hours later in this case and the empty box does not run as it should since it still shows as running from previous.   Nothing in this log other than the above for this set of jobs.

Run "autorep -d -J" on the box and look at the ProcessTime column. If the timestamp for the Running event is later than the timestamp for Success, you need to get a patch from CA. This is a known bug for which there are patches.