AutoSys Workload Automation

When you have 2 calendar types and decide that it would be fun to make the name and type the unique pair and not just the name.

Then ask yourself which calendar gets used? 

*sigh*

chalk this up to Steve C. would never think of doing that therefore never looks until he is told by another.. 

as i teach in all my classes .. sometimes you just dont do that ... 

So Dan/CA .. is this a BUG or by design before i open a ticket and complain :-)

autocal_asc -l

fom Extended Calendar
fom Standard Calendar

run_calendar: fom

so which one is used? 

*sigh*

Thank you 

You definitely can't do it on purpose. I checked SP7 and both autocal_asc and WCC block the creation of a new calendar if the name is already in use, even when the existing calendar is not the same type you are creating. I also checked 11.0 SP5 and you couldn't do it there either. Open an issue on that one.

Scott,

you are correct. so this must have occurred in 11.3.6 SP1  or 11.3.5 we are at SP6Cum1 and it doesn't allow the create. I would have thought a unique constraint would have had an issue sooner.. 

i will just have the duplicate removed, but it worries me that wcc doesnt balk. or scheduling doesnt balk.. 

I don't know if that's a good thing or bad thing.. 

I appreciate you checking the longevity. 

Steve C.