AutoSys Workload Automation

  • Private Community

  • 1.  Child jobs going to inactive status while box is in running state.

    Posted May 16, 2019 05:04 AM

    Child Jobs missing its run

     

    Hi All,

     

    We are facing an issue where the child jobs are in INACTIVE state when the box comes in RUNNING STATE, due to which the child jobs are missing its run & we need to manually forcestart these jobs on daily basis.

     

     

    My understanding is that child jobs in box can only run if these jobs are in AC state & as soon as box comes to RU state, these jobs shd start running, but in this case, Child jobs are INACTIVE & box is in RU state due to which the these jobs are missing its run. Am I correct?

     

    As per client, this is a bug as its was running fine in older version - R11.3.6 Sp1/Sp2 but from the day we upgrade to R11.3.6 SP7, these jobs are not running automatically.

     

    So please confirm? also, is it really important / mandatory that child jobs shd be in AC state to run as per box behavior.

     

    Raised a case with CA as well but no response so far.



  • 2.  Re: Child jobs going to inactive status while box is in running state.

    Posted May 22, 2019 10:17 AM

    Hi All,

     

    1.Making a Job OFF_ICE means that the jobs is not scheduled to run for that day & in short is removing the job / box from execution for that day hence it is the standard behaviour of OFF_ICE in all versions of AUTOSYS

    2. In order the child job in the box to run, the jobs inside the box should be in ACTIVATED state, however in this case, the jobs went to INACTIVE (switching state change from ACTIVATE to INACTIVE) as soon as it is marked as OFF_ICE.

     

    Hence it is not a BUG & autosys is behaving as per actuals, however how these jobs were running in the lower environment is still a question.

     

    Earlier version was - Workload Automation Autosys - 11.3.6 on Linux RedHat 6.5 - RO73603, RO76442, now its R11.3.6 SP7

     

    Any idea on this issue or place where in we can check. Will these patches which were applied could have made the jobs to run without any issues.

     

    your response will be highly appreciated.

     

    Regards,

    Sunish



  • 3.  Re: Child jobs going to inactive status while box is in running state.

    Posted May 23, 2019 08:29 AM

    Its not clear, but are the 4D jobs being placed ON/OFF ICE by jobs/steps in 4c?  If yes, why?  Is everything in an outer parent box?



  • 4.  Re: Child jobs going to inactive status while box is in running state.

    Posted May 23, 2019 09:31 AM

    1. Yes, the 4d child jobs are being placed ON_ICE / OFF_ICE by 4C jobs & the reason by app team is that they dont want the flow to be halted if 4c jobs stuck in failed state. 

     

    We dont know the exact details on why the job setup is like this since we take over the support from other client/incumbent but as of now, it looks like we are in tight spot with no reason on why its happening & as per client its a BUG in latest autosys version, as it was working in old envt/ex-incumbent.