FORCE OK steps not executing code OK

[icemanCTM]

Not running steps, whith force Ok Job, what's up?

not running with code = OK, FORCE

Control-M 6.3

[Banshee06]

What does the job log show?

[icemanCTM]

27/05/10 09:46:23 TR5120 JOB STATE CHANGED TO Analyzed
27/05/10 09:46:23 SL5120 JOB STATE CHANGED TO Post processed
27/05/10 09:46:29 CS5411 FORCE OK REQUEST SUBMITTED BY USER MRN10964
27/05/10 09:46:29 SL5410 JOB FORCED OK
27/05/10 09:46:29 SL5120 JOB STATE CHANGED TO Post processed

[icemanCTM]

On Statement Stmt = +EVERY Code = FORCE
Do Set-Var Name = \IDALARMLEVFG1 Value = %%OWDAY.%%OMONTH._%%JOBNAME
Do Set-Var Name = \DESCRIPCIONLEVFG1 Value = ERROR %%APPLIC/%%APPLGROUP/%%JOBNAME
Do Set-Var Name = \SEVERIDADLEVFG1 Value = NORMAL
Do Set-Var Name = \SOPORTELEVFG1 Value = Control-M
Do Condition Name = Test_LevantaFG-ENDED-OK Date = 27/05 Sign = +

[Banshee06]

It looks like it is doing the post processing for the Ok condition?

[icemanCTM]

On Statement Stmt = * Code = OK

[icemanCTM]

im sorry... english limited

I'm sorry for my explicated

[Banshee06]

Can you give more of what you have in yuour steps
for example

On stmt=* Code=OK And
Do Condition Force JobName

[icemanCTM]

On Statement Stmt = * Code = NOTOK
Do Set-Var Name = \IDALARMLEVFG1 Value = %%OWDAY.%%OMONTH._%%JOBNAME
Do Set-Var Name = \DESCRIPCIONLEVFG1 Value = ERROR EN EL JOB %%APPLIC/%%APPLGROUP/%%JOBNAME
Do Set-Var Name = \SEVERIDADLEVFG1 Value = MINOR
Do Set-Var Name = \SOPORTELEVFG1 Value = Control-M
Do Condition Name = Test_LevantaFG-ENDED-OK Date = ODAT Sign = +
On Statement Stmt = * Code = OK
Do Set-Var Name = \IDALARMLEVFG1 Value = %%OWDAY.%%OMONTH._%%JOBNAME
Do Set-Var Name = \DESCRIPCIONLEVFG1 Value = Termino OK JOB %%APPLIC/%%APPLGROUP/%%JOBNAME
Do Set-Var Name = \SEVERIDADLEVFG1 Value = NORMAL
Do Set-Var Name = \SOPORTELEVFG1 Value = Control-M
Do Condition Name = Test_LevantaFG-ENDED-OK Date = ODAT Sign = +
On Statement Stmt = * Code = FORCE
Do Set-Var Name = \IDALARMLEVFG1 Value = %%OWDAY.%%OMONTH._%%JOBNAME
Do Set-Var Name = \DESCRIPCIONLEVFG1 Value = FORCE OK JOB %%APPLIC/%%APPLGROUP/%%JOBNAME
Do Set-Var Name = \SEVERIDADLEVFG1 Value = NORMAL
Do Set-Var Name = \SOPORTELEVFG1 Value = Control-M
Do Condition Name = Test_LevantaFG-ENDED-OK Date = 27/05 Sign = +

[Banshee06]

So it looks like the job didnt have a condition of OK,
It was forced OK by you?
And I am not sure there is a Code = FORCE ?

[icemanCTM]

I want is to run the steps as if the job ended in Ok.

When set to "Force OK" do not run the steps, or is there some way to run dicahs conditions

[icemanCTM]

I want is to run the steps as if the job ended in Ok.

When set to "Force OK" do not run the steps, or is there some way to run dicahs conditions

[Banshee06]

Okay so why do you force it okay?
If it runs and fails " Not Ok" runs the same do statements
If it runs and is successful it looks like it should run the do statements
why would you force it ? It should either succeed or fail which will execute the do statements?
Thank You

[Walty]

Hi,

Don't forget:

FORECEOK can only be applied to inactive jobs (that is, jobs that are not running).

[Banshee06]

Maybe you should create a Dummy job after this job since you seem to want these do parmeters set no matter what.
and it purpose would be if the job is OK, NOTOK or the the job is forced OK
it would set these do contions?