Hello all,
First, best wishes to all, have a joyful and prosperous New Year.
I just received a call from customer and he said that New Day procedures deletes all jobs that have not been executed, but they have MaxWait parameter set to 1, so, they shouldn't be deleted from AJF.
What can cause this?
Some of them are in Wait condition status, some of them are in Wait Confirmation status.
No cyclic jobs.
That's never happened before.
CONTROL-M EM 6.3.01.200 (Windows)
CONTROL-M 6.2.18 (z/OS)
Thanks in advance
New Day Procedure deletes jobs that shouldn't be deleted
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- anilgupta1981
- Nouveau
- Posts: 2
- Joined: 30 Dec 2009 12:00
New Day Procedure deletes jobs that shouldn't be deleted
This is because you are not using max wait or max wait is not defined. Put the max wait 5 in execution tab and your jobs will not be deleted
Hello all,
NDP performs at 06:00 AM, ODATE is OK. Calendars checked and updated to 2010.
MaxWait=1, customer do not want to set it to 5, there is no need for that.
We solved problem using BMC Support and documentation for z/OS - there are one parameter in IOA configuration:
ID=WM2367,APPLY=YES,DATA=0,DATAC=00 (default varable)
We changed it to:
ID=WM2367,APPLY=YES,DATA=0,DATAC=01
Check BMC KB for WM2367.
NDP performs at 06:00 AM, ODATE is OK. Calendars checked and updated to 2010.
MaxWait=1, customer do not want to set it to 5, there is no need for that.
We solved problem using BMC Support and documentation for z/OS - there are one parameter in IOA configuration:
ID=WM2367,APPLY=YES,DATA=0,DATAC=00 (default varable)
We changed it to:
ID=WM2367,APPLY=YES,DATA=0,DATAC=01
Check BMC KB for WM2367.