Sequence skips job execution

[audev]

Hello,
I have a situation I do not fully understand. A sequence scheduled and run by TWS skips the executon of the last job.

This is the summary of the sequence run when scheduled by TWS:

SEQUENCE..JobControl (@Coordinator): Summary of sequence run
23:50:24: Sequence started (checkpointing on)
23:50:24: Job_1 (JOB Job_1) started
23:50:31: Job_1 (JOB Job_1) finished, status=2 [Finished with warnings]
23:50:31: Job_2 (JOB Job_2) started
23:51:43: Job_2 (JOB Job_2) finished, status=1 [Finished OK]
23:51:43: Job_3 (JOB Job_3) started
23:51:47: Job_3 (JOB Job_3) finished, status=2 [Finished with warnings]
23:51:47: Sequence finished OK


While instead, if run manually from Datastage Director, the sequence runs also the Job_4 (all of them are executed):

SEQUENCE..JobControl (@Coordinator): Summary of sequence run
17:20:53: Sequence started (checkpointing on)
17:20:53: Job_1 (JOB Job_1) started
17:20:54: Job_1 (JOB Job_1) finished, status=2 [Finished with warnings]
17:20:54: Job_2 (JOB Job_2) started
17:21:11: Job_2 (JOB Job_2) finished, status=1 [Finished OK]
17:21:11: Job_3 (JOB Job_3) started
17:21:13: Job_3 (JOB Job_3) finished, status=2 [Finished with warnings]
17:21:13: Job_4 (JOB Job_4) started
17:21:15: Job_4 (JOB Job_4) finished, status=2 [Finished with warnings]
17:21:15: Sequence finished OK


Does anyone have any idea?
Thank a lot in advance,

[chulett]

Well, that's... interesting. Can you share with us a couple of things?

1) Trigger expression for Job_3 to Job_4
2) TWS command used to run the Sequence

[audev]

Hi Craig,

1)



Where 110 aborts the job, 100 triggers the Job_4.

This is the info in the log of Job_3: "Job_3.AfterJob (TD000setJobUserStatus): HDP_CHECK:100".

Here, it does not abort nor continue, it just ends.

2)

"dsjob -run -warn 200 -jobstatus -param parameter_1 parameter_2 SEQUENCE"

Where parameter_1 is a date and parameter_2 is a string.

The point is that I have 5 identical sequences (read 5 different input data, but are configured exactly the same way, or at least I have not found any differences), but only this has this issue

Thanks

[chulett]

Hmmm... seeing as how this is one of five sequences with the same configuration and it's the only one exhibiting this behavior, I would think you are in Official Support Provider territory.

[ray.wurlod]

Before you do that, try re-compiling the aberrant sequence job.