Extended Calendar

[Barbara Redzinski]

I need to look at the dates a extended calendar created 1 month ago.  Is it possible?  I trying to investigate why a job ran when it shouldn't have.

[Michael Woods]

Hi Barbara,

If you have access to WCC you can go into quick edit and switch the dropdown from the default job to calendar.  Then put in the calendar name that you want to get the dates for and click the Go button.  You will then need to select 'Extended Calendars" by the search results.  Once it is found click on Generate Preview and you will get a 'calendar view' of the generated dates.

If you don't have access to WCC, you can use autocal_asc.  After you enter the command on the next prompt, select option 2 for Administer Extended Calendar.  The select option 5 Preview an Extended Calendar.  You will be prompted for the calendar name and after you enter and hit enter, you will get the generated dates.

Regards,

Mike

[Barbara Redzinski]

Thanks Michael for the response.  I have access to both, but unfortunately the extended calendar will only give me dates going forward from today.  Even if I pick January 2023 and hit go.  It won't show previous dates in the calendar. 

[Michael Woods]

Sorry, I missed the bit about previous dates.  There is no way I know of that would show you the previous dates.  If you still have teh event demon log if the job was 'scheduled' to run you should see a message associated with the STARTJOB saying "Event was scheduled based on job definition.

If there are other jobs using the same calendar, did they also run?  If the job was force started, you should see that in the event demon as well as the as_server logs.  The autotrack reports or archives should also help identify who did it as well.

If those suggestions don't help, would you mind putting in the extended calendar definition here as well as the suspected date?  We may be able to work back and see what days should have been generated.

Mike

[Barbara Redzinski]

Mike,

Attached are the two calendar definitions.  The extended calendar and the standard holiday calendar.  

The issue is the extended calendar is used as a run_calendar and a exclude calendar.  The job in question uses the extended calendar as a exclude calendar and was not supposed to run on Labor day but did. 

/* ----------------- Erpfi_Labdist ----------------- */ 

 

insert_job: Erpfi_Labdist   job_type: BOX 

owner: jserpfiP10

permission: gx

date_conditions: 1

days_of_week: su,mo,tu,we,th,fr,sa

exclude_calendar: CalDay1thru2WD1ShiftWBS

start_times: "17:40"

condition: d(Erppm_Cats2pm_ABAP)

description: "Post labor and vehicle distributions from CATS"

job_terminator: 1

alarm_if_fail: 1

alarm_if_terminated: 0

group: PRD

The interesting fact is the job was not supposed to run on the January 2nd, and it didn't.  (I checked the demon log).

I am not sure if the "Schedule anyways, ignoring Holidays" is messing it up.

Barb

[Michael Woods]

Good catch!  You got it, it's the holiday action saying to "schedule anyway, ignoring holidays" that is causing it to run on the holidays.

It sounds like you want "Do not schedule the job on holidays" instead.

Regards,

Mike

[Barbara Redzinski]

Thanks Michael for all your help.  Much appreciated. :)