DSXchange

Now, if you mean tell you the difference, then I respectfully suggest you Google up the two terms or just 'outer join' in general as they are bog standard relational database / sql terms and nothing specific to DataStage. If you have a more specific question about the stage, please come back and ask...

Of course.

I have no idea if this would work properly by the time it gets to your SQL, but try a string where your inside quotes are just data: "'A','B','C'" Double quotes on each end, single quotes around each letter. Or if your SQL needs double quotes, reverse them. Of course, your whole point of u...

No can do inside a job. You'll need to check outside the job for that condition and then act accordingly, typically leveraging a Sequence job for that.

Didn't say they weren't there.

Didn't say they weren't there.

No, it doesn't cause a problem... unless your table names change in the process. And no, there's no need to remove them either. Best, however, would be to understand the difference in behaviour with regards to your generated SQL when a value is there versus when there is no value there. The Load opt...

Let's see... it works fine for some users and not for others... hmmm... methinks you have a permissions problem.

Or maybe the server had an antivirus program running on it, slowing everything down?

Not a PX guy, so haven't handled your situation in a Parallel job. We do, however, handle that kind of thing quite often in Server and I've had no such issues as you've noted in (3). It has been nothing but consistent and proper link ordering, division of labor across links and action choice are the...

theverma wrote:One more observation to add on is that when we execute dsjob command without parameter from TWS,it works fine.

Ah... then - as you've discovered - your syntax was wrong.

Once the first job completes, it commits the changes. You would need to do both in a single job if you want the failure of one to roll back the other.

Build an routine that calls the script and checks the result. Call DSLogFatal() if the script fails.

What 'problems' does it give? Can you post the actual errors?

ps. I would never have an Enterprise Scheduler execute dsjob directly, it should always be wrappered in a script that sets up the proper environment. Etc. IMHO.

It returns the 'standard' status values as documented in the $DSHOME/include/dsapi.h file and elsewhere: /* 'jobStatus' values... */ #define DSJS_RUNNING 0 /* Job running */ #define DSJS_RUNOK 1 /* Job finished a normal run with no warnings */ #define DSJS_RUNWARN 2 /* Job finished a normal run with...