ESP Workload Automation

Back to discussions
Expand all | Collapse all

When looking at FORCE_STARTJOB events in iDash reports, why would the counts in Autotrack report and Event report be different given all of the other criteria including time interval are the same?

  • 1.  When looking at FORCE_STARTJOB events in iDash reports, why would the counts in Autotrack report and Event report be different given all of the other criteria including time interval are the same?

    Posted Mar 10, 2015 09:25 AM

    When we run an Autotrack report and an Event report in iDash with same selection criteria including time interval, we sometimes see a very different number of FORCE_STARTJOB events.  The force start counts in the Autotrack report are sometimes smaller than the counts in the Event report.  What would explain the difference?



  • 2.  Re: When looking at FORCE_STARTJOB events in iDash reports, why would the counts in Autotrack report and Event report be different given all of the other criteria including time interval are the same?

    Posted Mar 12, 2015 04:36 PM

    Anyone able to assist with this question?

     

    Thank you

     

    Douglas Mutart wrote:

     

    When we run an Autotrack report and an Event report in iDash with same selection criteria including time interval, we sometimes see a very different number of FORCE_STARTJOB events.  The force start counts in the Autotrack report are sometimes smaller than the counts in the Event report.  What would explain the difference?



  • 3.  Re: When looking at FORCE_STARTJOB events in iDash reports, why would the counts in Autotrack report and Event report be different given all of the other criteria including time interval are the same?

    Posted Mar 12, 2015 05:16 PM

    Je suis absent(e) du bureau jusqu'au 13/03/2015

     

     

     

     

    Remarque : ceci est une réponse automatique à votre message  "Re: [CA

    Workload Automation] - When looking at FORCE_STARTJOB events in iDash

    reports, why would the counts in Autotrack report and Event report be

    different given all of the other criteria including time interval are the

    same?" envoyé le 12/03/2015 21:37:29.

     

    C'est la seule notification que vous recevrez pendant l'absence de cette

    personne.

     

     

    This message and any attachments (the "message") is

    intended solely for the intended addressees and is confidential.

    If you receive this message in error,or are not the intended recipient(s),

    please delete it and any copies from your systems and immediately notify

    the sender. Any unauthorized view, use that does not comply with its purpose,

    dissemination or disclosure, either whole or partial, is prohibited. Since the internet

    cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS

    (and its subsidiaries) shall not be liable for the message if modified, changed or falsified.

    Do not print this message unless it is necessary,consider the environment.



  • 4.  Re: When looking at FORCE_STARTJOB events in iDash reports, why would the counts in Autotrack report and Event report be different given all of the other criteria including time interval are the same?
    Best Answer

    Posted Mar 12, 2015 08:04 PM

    This may require some additional analysis of the actual data that is loaded into the iDash DB. Is the autotrack report missing data for a particular day? I recommend opening a support issue so we can help analyze this further.

     

    Thanks,

    Parag