DSXchange

I would tend to disagree with you that the Oracle connection or stage is not the culprit. Do you have any specific SQL you use in the jobs, or nonstandard stage settings? I don't think that SuSE is a supported platform, otherwise you could approach your support provider. Have you tried using ODBC fo...

What does the job do (i.e. which stages) and does it have before/after logic in the job or any of the stages?

Those are your devices. the man pages of "iostat" will help you understand the output, as would using google to search for "UNIX devices".

Make a test copy of the job with just the Oracle read and a write to a sequential file. Does the error still happen? What sort of SQL are you issuing? Have you successfully read any data from this stage in this project?

DataStage is not a SMTP client, but fortunately on Windows the MKS toolkit contains "smtpmail" which you can use.

This has not only been answered many, many times on the forum but is also clearly documented in the Parallel Job Developers Guide in the chapter 12 titled "The Parallel engine configuration file" on pages 599 through 615. After you've read those pages and have specific questions, please do...

Perhaps the log is very large or corrupt or both. This can be fixed if you "Job -> Clear Log -> Immediate Clear all entries" from the director.

Craig, I agree with you - I would program it that way but expanded the logic to make the statement more understandable.

The execute command stage will almost certainly not have any bug of the type you assume it has. We are asking about the problem so that you can located the actual cause. The "0" or "1" return value is due to the command line setting stderr. Since you stated that there is more log...

Ray - I corrected the original post, but you slipped in earlier

So far almost every project that I've worked on has created a set of standard naming rules for everything from links and stages to variables and parameters.

No two projects have had the same rules, and only a few have had rules similar to another project.

What we call "Routines" in DataStage server jobs are actually functions. A Job Before/After routine is a real routine and does not have a variable, user-defined, list of parameters. It has 2 parameters, the first being input to the routine and the secod is the return code. Any return code ...

2 Stage Variables: constraint "svDuplicate=0"

Message handlers only apply to PX jobs, not to server jobs (job sequences are server jobs).

"cat file1 file2 > wc -l" should be sufficient without having to create a file. Is the "0" or "1" supposed to be the line count or the return code?