AutoSys Workload Automation

  • 1.  Difference in START & END TIME in autorep -j

    Posted Jan 14, 2019 02:18 PM

    Why there is difference between START TIME & END TIME showing in the following output

     

    Job Name Last Start Last End ST/Ex Run/Ntry Pri/Xit
    ________________________________________________________________ ____________________ ____________________ _____ ________ _______
    test_abc 01/14/2019 14:13:27 01/14/2019 14:13:27 SU 478/1 0

    Status/[Event] Time Ntry ES ProcessTime Machine
    -------------- --------------------- -- -- --------------------- ----------------------------------------
    STARTING 01/14/2019 14:13:27 1 PD 01/14/2019 13:13:27 abc
    RUNNING 01/14/2019 14:13:27 1 PD 01/14/2019 13:13:28 abc
    <Executing at WA_AGENT>
    SUCCESS 01/14/2019 14:13:27 1 PD 01/14/2019 13:13:28 abc



  • 2.  Re: Difference in START & END TIME in autorep -j

    Posted Jan 23, 2019 02:02 PM

    The left hand side is the actual event. the right hand side is when the event process acknowledged processing it. 



  • 3.  Re: Difference in START & END TIME in autorep -j

    Posted Jan 23, 2019 03:20 PM

    Hi Steve,

     

    Is there a way by which i can retrive the old event_demon log file for the date 14th Jan, as i am having the offset difference of 1 hr where DB is storing & process the events 1hr late as per actual.

     

    so wondering how this issue occurs all of sudden & now how to fix this.

     

    CAUAJM_I_40218 **** Time offset between CA WAAE and Event Server 1 is 3600 seconds. ****

     

    i am assuming that something happened on 14th Jan event demon logs but its no more in system.

     

    event demon log for today on forcestart a job :

    [01/23/2019 14:40:00]      ----------------------------------------
    [01/23/2019 14:40:31]      CAUAJM_I_40245 EVENT: FORCE_STARTJOB   JOB: pepwxw00008_test
    [01/23/2019 14:40:31]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: STARTING        JOB: pepwxw00008_test MACHINE: pepwxw00008
    [01/23/2019 14:40:31]      CAUAJM_I_10082 [pepwxw00008 connected for pepwxw00008_test 1151.525.1]
    [01/23/2019 14:40:32]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: RUNNING         JOB: pepwxw00008_test MACHINE: pepwxw00008
    [01/23/2019 14:40:32]      <Executing at WA_AGENT>
    [01/23/2019 14:40:32]      CAUAJM_I_40245 EVENT: CHANGE_STATUS    STATUS: SUCCESS         JOB: pepwxw00008_test MACHINE: pepwxw00008     EXITCODE:  0

     

    but autorep says

     

    Job Name                                                         Last Start           Last End             ST/Ex Run/Ntry Pri/Xit
    ________________________________________________________________ ____________________ ____________________ _____ ________ _______
    pepwxw00008_test                                                 01/23/2019 13:40:31  01/23/2019 13:40:31  SU    525/1    0

      Status/[Event]  Time                 Ntry ES  ProcessTime           Machine
      --------------  --------------------- --  --  --------------------- ----------------------------------------
      STARTING        01/23/2019 13:40:31    1  PD  01/23/2019 13:40:31   pepwxw00008
      RUNNING         01/23/2019 13:40:31    1  PD  01/23/2019 13:40:32   pepwxw00008
        <Executing at WA_AGENT>
      SUCCESS         01/23/2019 13:40:31    1  PD  01/23/2019 13:40:32   pepwxw00008
      [STARTJOB]      01/30/2019 13:12:00    0  UP
        <Event was scheduled based on job definition.>



  • 4.  Re: Difference in START & END TIME in autorep -j

    Posted Jan 28, 2019 03:24 PM

    Might want to check and see what the system time is on each system, assuming your database and scheduler is on different servers. 



  • 5.  Re: Difference in START & END TIME in autorep -j
    Best Answer

    Posted Jan 28, 2019 04:12 PM

    TZ variable in CRS config file got changed during patching by DBA team which caused the issue. Its been fixed now.