DSXchange

Looks like question is now different from the one Ray answered.

You 'call' it simply by using it in a Transformer derivation. At the most basic level:

Get rid of the slashes.

Because, as noted, the mask in the supplied example does not match your input format.

Try it and see. Correct the date mask so it matches what you've said is in your file first, however.

Interesting... I''ve always used 'Case 2' without issue regardless of database server location.

During the job that is generating the errors? No. Prefer to build jobs that don't generate errors. When they do, get the information from the log. You'd need some kind of hook into 'oerr', perhaps a web service? Or pull a list from somewhere and populate a hashed file you could look up the descripti...

tsamui wrote:If I run this sequence and one job activity abort, the sequence aborts immediately?

No.

Ah... apparently, you helped yourself by searching the forums.

With no details on the actual design of your Sequence job, all you can get is a generic answer, which is the latter - 'other jobs finish first then the sequence will go in Aborted state'.

More Wurlod humor. :D

A 'gross' is a unit of measure - a 'dozen dozen'. 144.

Ah... that's not 'killing', that would be 'unlocking' - which a search for in the forums would reveal a wealth of information on.

This is a result of setting the Sequencer to 'All'. It is telling you that not all triggers that feed it 'fired' so it did not trigger its output link. That as a result of the jobs 'having warning messages' I'd wager, as that isn't really considered 'Success' if all you are using are 'OK (Conditiona...

Ah... thanks for a real answer. All that popped into my head when I saw that question was a Magic 8 Ball.

Will I get any warnings in future production runs?

<shake shake>

Outlook good

You are missing an important point. Your routine is not failing, at least not in any obvious manner or you would be seeing some of your coded "JobControl" LogFatal messages. Your Sequence job considers it to have failed and treats it as such because of the non-zero return code. That's all. You need ...

Your message obviously isn't coming from this routine. As for whether it returns the 'current' or 'generated' batch number there's no way for me to know and it doesn't really matter. I'm just going to repeat what I've said before and then leave it at that. When a Routine Activity stage does not retu...