Sequence jobs - Sequencer

[Kirtikumar]

Hi,

In my job sequence, there are many jobs. If any of the job fails or generats warning, I need to call an Abort job that updates one of the process status table as 'Failed' for the process.

The sequence has many job and from each we have added a custom condition (Abort or Warn) to the abort job.

To improve the readability of the job can we have back to back sequences?

E.g. Job1--->seq1--->seq2--->Seq3

Would it cause any prob? I tested it in some seq and was running fine. But just wanted to know if there is any well know prob in this.

[kwwilliams]

No problem having sequences calling sequences, or having sequences running back to back within another sequence.

[Kirtikumar]

Keith, it is Sequencer stage in job sequences I am talking about.
I should have mentioned it clearly in the first place itself. Sorry for that.

[kwwilliams]

That is a little different than what I was answering. What would be the purpose of having a sequencer stage back to back with another sequencer stage? If your job literally looks like:


job --> sequencer 1 --> sequencer 2 --> sequencer 3


What benefit are the sequencers providing?

[kwwilliams]

That is a little different than what I was answering. What would be the purpose of having a sequencer stage back to back with another sequencer stage? If your job literally looks like:


job --> sequencer 1 --> sequencer 2 --> sequencer 3


What benefit are the sequencers providing?

[Kirtikumar]

job does not exactly looks like this.

I have many stages in my jobs some called parallelly and sequentially.

If I just put one sequecer then many links cross each other as well as go over stages. To make the job readable I was thinking adding more sequencer stages.

[chulett]

Do whatever you like as long as it works and you get the 'all' versus 'any' setting correct in the Sequencers.

[Kirtikumar]

Thanks Craig!