DSXchange

Use DSSendMail, that's what it's there for, Windows or UNIX. Use DSSendMailTester to makes sure it all works for you and to iron out any kinks.

In other words, it's a manual process. Export both to a .dsx and compare using your favorite tool. This is automated in 8.x.

Again, what exactly are you putting in the stage that it won't accept?

A DataStage "node" is a logical concept and not something you can include in a SQL query. What exactly are you trying to accomplish?

But when I call the routine in a job activity it is not accepting if I dont supply quotes to the values. Two problems here. One is you don't call a routine from a Job Activity stage - do you mean a Routine Activity stage? And what does "not accepting" mean, what exactly are you putting in...

Post your SQL, then perhaps we'll have a clue what your "failed to compare" statement means.

Please don't start multiple posts on the same subject. Why not stick with your original post on the problem?

viewtopic.php?p=335270

Not true. If the job aborts they get 3. If it finishes with warnings they get 2. If they used -mode RESET they get 21. And so on. My statements have been based on my assumption that their Sequence job is always running to completion 'without error' and the errors mentioned are when jobs under the c...

Sequence restartability is completely different from the restartability you mean at the job level. It will simply start the job over again and without anything specific to handle previously committed rows will just attempt to load everything again. You may be OK with the upsert mode, however, as ins...

dstage2006 wrote:I am able to get it in the sequential file but not in the xml output.

First suggestion would be to explain this statement, I for one am unclear on what it is you are trying to say.

Assuming the queries are identical, there are a couple of reasons I can think of - they are sourcing from different instances or perhaps the source is 'dynamic', i.e. records were added before the second one was run.

At the moment, your [ParamValue/Limitvalue is not appropriate] error is being caused by the fact that it cannot cat the file you've asked it to: Output from command ====> cat: 0652-050 Cannot open /etl/PDAODS_Dev/temp/text.txt You need to solve the your 'cat' problem first. Does the filename as logg...

And then they'll always get a one rather than a zero.

Seems to me that is what was posted.

That just means the Sequence job itself ran to completion without issue. Look into the use of the Terminator stage after the email notification if you want the Sequence to abort as well.