Re: JBA ML - Machine manager & verify allocations

[Jeff_Klipa/Harvard@xxxxxxxxxxxxxx]

You MUST run the DLTADEOVR and DLTADSOVR jobs...!!!
These jobs remove any overrides you may have had in place...

You should set daymask to 0's for any job you do not want to run...

The override flag is for the NEXT RUN ONLY and should be cleared as the seq 9999
runs each day/night...

You are using the Override No Run flag in a way that it was not intended to be
used...

The intent of that flag is to include or omit a specific seq. in/from the NEXT
run of the ADS or ADE job...

Hope that helps...

Thanks for your kind words of sympathy...

This cowardly attack is not just an assault on the US it is an assault on all of
us...  Civilization itself...!!!
The global community must unite and seek out the perpetrators of these cowardly
deeds and destroy them...







GManoovaloo@ibl.intnet.mu on 09/12/2001 03:01:22 AM

Please respond to jbausers-l@midrange.com



  To:          jbausers-l@midrange.com

  cc:          (bcc: Jeff Klipa/Harvard)



  Subject      Re: JBA ML - Machine manager & verify
  :            allocations








Please note that JOB is not highlighted and no override has been applied to
the task.
We have never activated  seq 9999 ( DLT overrides) in both Day Start  & Day
If we have tasks that have been on purpose set to  0 (force no run) , what
would be the effect ?

regards


_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.