STATUS SET TO NOTOK AS A RESULT OF DO RERUN
STATUS SET TO NOTOK AS A RESULT OF DO RERUN
Has anyone seen this when using the rerun logic on the post proc steps?
JOB STATE CHANGED TO Executing
ENDED AT 20090415132133. OSCOMPSTAT 0. RUNCNT 1
STATUS SET TO NOTOK AS A RESULT OF DO RERUN
ENDED NOTOK
JOB STATE CHANGED TO Analyzed
QUANTITATIVE RESOURCES RELEASED
CONDITION OHH-TEST001-OK 0414 DELETED
CONDITION OHH-TEST001-OK 0415 DELETED
the job doesn't actually fail and does run the next time. I'm wondering if this is functionality of control-m that if you use the rerun login it assumes that the job originally failed and sends off a shout.
JOB STATE CHANGED TO Executing
ENDED AT 20090415132133. OSCOMPSTAT 0. RUNCNT 1
STATUS SET TO NOTOK AS A RESULT OF DO RERUN
ENDED NOTOK
JOB STATE CHANGED TO Analyzed
QUANTITATIVE RESOURCES RELEASED
CONDITION OHH-TEST001-OK 0414 DELETED
CONDITION OHH-TEST001-OK 0415 DELETED
the job doesn't actually fail and does run the next time. I'm wondering if this is functionality of control-m that if you use the rerun login it assumes that the job originally failed and sends off a shout.
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France
- dbeardking
- Nouveau
- Posts: 12
- Joined: 02 Jul 2009 12:00
- gratedsandy
- Nouveau
- Posts: 37
- Joined: 14 Mar 2007 12:00
- rahulsehgal
- Nouveau
- Posts: 148
- Joined: 19 Mar 2009 12:00
- Location: Delhi
- Contact:
ENDED NOTOK AS A RESULT OF DO RERUN
Yes, but there is no reason that the job should end NOTOK. You should be able to do a rerun on a job without this occurring. I think it may be a bug.[/quote]Hi,
This happen when you try to Rerun an already Ended Ok job,
Please check the steps tab in job definition, there you may have set this code:-
On Statement * Code OK
Do Rerun
Regards,
Hi,
it works as designed, it's not a bug. Define in the next line after DO RERUN a DO OK, and everything works fine.
E.g., you can find the description of this behaviour in the CONTROL-M/Server Admin Guide -> Utilities -> ctmcreate
"Normally, when a -dorerun parameter is implemented, the current run of the job
ends with NOTOK status. To ensure that the job will have OK status even though
it is rerun, specify a -dook parameter immediately after the -dorerun parameter."
Regards,
schidl
it works as designed, it's not a bug. Define in the next line after DO RERUN a DO OK, and everything works fine.
E.g., you can find the description of this behaviour in the CONTROL-M/Server Admin Guide -> Utilities -> ctmcreate
"Normally, when a -dorerun parameter is implemented, the current run of the job
ends with NOTOK status. To ensure that the job will have OK status even though
it is rerun, specify a -dook parameter immediately after the -dorerun parameter."
Regards,
schidl
- dbeardking
- Nouveau
- Posts: 12
- Joined: 02 Jul 2009 12:00
Hi,
yes, every rerun ends with NOTOK.
I don't know why this "feature" is implimented. I'm working with CONTROL-M/Server DS over 13 years know and this case is something, that i've accepted as "strange behaviour" of CONTROL-M
The only solution is to define the job as CYCLIC if possible.
Regards,
schidl
yes, every rerun ends with NOTOK.
I don't know why this "feature" is implimented. I'm working with CONTROL-M/Server DS over 13 years know and this case is something, that i've accepted as "strange behaviour" of CONTROL-M
The only solution is to define the job as CYCLIC if possible.
Regards,
schidl