DSXchange

... unless, of course, you design in partition parallelism, in a similar fashion as you would in server jobs. But please don't go down this path! Stop thinking like a server job designer and wrap your mind around how the Orchestrate engine works - it will look after data partitioning for you.

You find them in 7.5.

Without that you're pretty much limited to explicitly handling failures through Failure triggers and routine activities that log warnings.

Enrol in the Server to Parallel Transition Lab offered by DSXchange from time to time, either instructor-led or through the Learning Center as a set of video tutorials. This will not show you any conversion techniques, but certainly adjusts your mindset away from a "server job" way of thinking.

Yes. The instructions accompany the software.

Yes. Propagate the warnings upwards by checking "Log warnings after activities that finish with status other than OK" and/or "Automatically handle activities that fail" and/or direct all failures to a Routine that executes UtilityWarningToLog. Detect these warnings in the job sequence at each level ...

In a Lookup stage, in version 8, if you check the Range check box you must also double click and enter a range expression. This means that you are doing a range ("between") lookup. If you want just an ordinary lookup, uncheck the Range check box.

How about you try to design it, and offer your ideas for comment? DSXchange is not a substitute for education or support. For example, I am reading that you are wanting a job to monitor its own execution time, which means that you will be making this check - quite expensively - for every row process...

Almost certainly someone does. But without telling us the data type of the target column, it's impossible to advise.

On the other hand, if you want the column name to have a timestamp appended dynamically, that's a whole different bucket of fish, and I would venture to say that it's impossible.

Ignore the green lines for the moment. They are purely cosmetic anyway. Director reports from the RT_STATUSnnn table; for whatever reason your job (if it is in fact finishing) is not updating this table. Open a Monitor from Director and tell us what you see there.

Since you already have a Transformer stage, you can use nested conversion functions there. Thereby you could avoid any need for your Modify stages.

It's whatever the maximum size for an attachement is for your SMTP mail client. This is not a limit set by DataStage.

Notice that the error message was received from SMTPMail. It was not generated by DataStage.

What scheduling tool do you use?

Does the job (not the job sequence) report in its log that it is Completed? Does it have an after-job subroutine?

Sequential is still parallel (one-way parallel). The Lookup stage should be able to handle it. Have you constrained the Lookup stage to operate in sequential mode also?

I vaguely remember that you manage this through the WAS Admin console. But I'm nowhere that I can verify that.