DSXchange

There is a routine called DSSendMail and another called DSSendMailTester that calls it that will illustrate things for you. Copy and adapt the latter to your need.

Food for thought... I very rarely use sequences except for 'looping' situations, especially for anything approach hundreds or (shudder) thousands of jobs. Many folks out in the wild have developed some kind of 'job control' code, for us we took the complete solution Ken Bland freely offers on his we...

Or just include a hard-coded set of fields on the link before the pivot that you've set to the column names and pivot that along with the others.

The stage does not support parameters in the body other than the handful of error related variables as documented. You'd need to write your own DSSendMail interface routine to make the body truly dynamic.

Not sure how to make it any simpler - where are you issuing this delete? In the target DB2 stage doing the inserts it seems, but where / how ?

That is correct, that command line function will not import the 'design time information' in your version. As to how useful those jobs would be, that is debatable. It used to be the only option and IMHO made supporting versions outside of the dev environment problematical. Stick with the GUI for the...

Yes, but I'm still curious where exactly this delete is being executed.

Or run on one node.

Meaning it is "hanging"? That can happen when the log contains a bajillion warnings and you may just need to be very patient. Do you want to see what's in it or just empty it?

Any logs or just the log for a particular job? And 'not able to see' means they show as empty or something else? And this is 8.0 or 8.1? For 8.1 you need to look elsewhere, from the console perhaps?

"Too many open files" is a transient resource issue, you could change it back and be fine now, I'd wager... that or just have waited and run it again.

YourFieldName[1,2000]

The Stored Procedure stage won't help you here. The Oracle stages support dynamic loading of their SQL from a file, you may be able to use it there if we're talking about a select. Otherwise, you'll need to script a call to your command line utility (like sqlplus for Oracle) and then run that either...

No, it only converts to a period. But you can play a game - first convert all periods to an unusual character that won't be in the data, then MCP and then convert the periods back.

The CLOB *is* the issue, they are unsupported in DataStage and I didn't suggest you change anything about the database, just how you treat the CLOB in your job. At worst case CAST it to a varchar in your sql or leverage the DBMS_LOB.SUBSTR function to substring out what you need in chunks. And make ...