We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.
Our Support systems migrated on Saturday, May 21. We'll automatically forward you to the new location for this content.

Job ran as rerun, but should be normal monthly run. Why?

Comments

3 comments

  • Avatar
    Matthew Kennedy

    Hi Stacey,

    If the job is run once more, does the output again reflect it was performed as a "rerun"?

    There are many possibilities on why this may have occurred. On what platform is the team hosting ACR? I recommend opening a support case so we may review your JCL that was submitted for the job run.

    Matthew Kennedy

    0
    Comment actions Permalink
  • Avatar
    Stacey Bauer

    Thanks for reaching out Matthew,

    I already reached out to support.  Thought someone might have an easy answer.  Nothing changed in JCL and we don't use any operator coded parameters.  Nothing changed in the ACR balancing job beyond deleting a few items as noted above.  Never ran as rerun before (unless the actual batch job needed to rerun).  Thought there might be an easy idea what would trigger rerun just by deleting a few items. 

    Thanks anyway

    Stacey

     

    Stacey

    0
    Comment actions Permalink
  • Avatar
    Stacey Bauer

    One thing that is odd is that the Run date and rerun date are the same and the job only ran once.  The start time is when the job started and the rerun time is when the job ended. The run that originally generated the 20200301 cycle number was back on March 1. 

    0
    Comment actions Permalink

Please sign in to leave a comment.