STATUS SET TO NOTOK AS A RESULT OF DO RERUN

All questions about Control-M jobs definitions
Post Reply
User avatar
klethere
Nouveau
Nouveau
Posts: 6
Joined: 12 Feb 2009 12:00

STATUS SET TO NOTOK AS A RESULT OF DO RERUN

Post by klethere » 15 Apr 2009 2:24

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.

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 16 Apr 2009 9:47

have a look on the on do parameters of your job, and the particulary order of them

regards
philmalmaison

User avatar
dbeardking
Nouveau
Nouveau
Posts: 12
Joined: 02 Jul 2009 12:00

Post by dbeardking » 03 Jul 2009 4:47

Hi,

I have come across the same situation as well. There are quite a few jobs which shout 'Ended Not OK' and the logs say 'STATUS SET TO NOT OK AS A RESULT OF DO RERUN'.

Wondering why such alerting is in place. Can you explain ?

Regards,
Jasper.

User avatar
gratedsandy
Nouveau
Nouveau
Posts: 37
Joined: 14 Mar 2007 12:00

Post by gratedsandy » 03 Jul 2009 10:22

This is seen when you have a 'DO RERUN' code implemented under the STEPS tab.
Whenever, there is a Do Rerun statement, Control-M will set the Status of the job to NOTOK before doing the re-run. Th

User avatar
rahulsehgal
Nouveau
Nouveau
Posts: 148
Joined: 19 Mar 2009 12:00
Location: Delhi
Contact:

Post by rahulsehgal » 03 Jul 2009 7:51

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,

User avatar
brownbag
Nouveau
Nouveau
Posts: 161
Joined: 11 Oct 2007 12:00
Location: Melbourne

ENDED NOTOK AS A RESULT OF DO RERUN

Post by brownbag » 06 Jul 2009 4:20

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,
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]

User avatar
schidl
Nouveau
Nouveau
Posts: 16
Joined: 11 Jun 2007 12:00
Location: Germany
Contact:

Post by schidl » 06 Jul 2009 6:25

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

User avatar
dbeardking
Nouveau
Nouveau
Posts: 12
Joined: 02 Jul 2009 12:00

Post by dbeardking » 06 Jul 2009 11:58

Hi Guys,

Thanks for enlightening. In that case, if the rerun counter is set to 3, will all the 3 reruns end Not OK ? Any specific reason why such design is in place

User avatar
schidl
Nouveau
Nouveau
Posts: 16
Joined: 11 Jun 2007 12:00
Location: Germany
Contact:

Post by schidl » 07 Jul 2009 9:50

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

shazinaz

Post by shazinaz » 29 Sep 2011 12:46

Thank you for a very clear and helpful post.

Post Reply