DSXchange

I didn't say that these would occur, just that they could occur. If the initial load uses a different method from the recurrent one then there is a chance that the two methods won't synchronize (particularly after problems such as job aborts or retries with new data). If you only use one method then...

It would seem that the "$" character is not liked by the compiler. This would imply that you need to create a job parameter without a $-sign and fill it at runtime with with the project level variable, or use the function GetEnvironment("$EnvVar")

Pivot stage would solve this nicely

Did you delete it from the correct instance of the database? I've spent time trying to solve similar issues, only to discover that I deleted the test data instance table contents instead of the development instance.

This is more of a design question than a DS implementation one. Using a generated key from the beginning ensures that there are no duplicates and less "holes".

Did you add the instance name to the job name when you did this?

vinodbp - do you really expect a faster answer by posting the exact same question many times on different threads?

If it is a parallel job, please post it there, not in the server forum.

Moderator - Please move this post to the PX Forum

sanjumsm wrote:...There is no online help available in Dstage 8.0 like Dstage 7.5.1. That is the problem and hence I put this question...

Odd, I have V8 and on-line help.

Did you declare this as a routine or a before/after job routine? There is a big difference. What is your compiler error?

The server probably didn't restart correctly. Shut down the server again. Do a "netstat -a | grep dsrpc" and there should be NO entries. Then restart the server.

With RCP enabled, only columns explicitly dropped are not propagated. So the answer is a, b, c, d, e.

Yes, you can do this. DataStage hashed files have various types, and a type 19 file is stored as directory. Each "Key" in this hashed file is stored as an OS file, and each hashed file record contents is stored as a row in that file. In your case the key (and file name) would be the "Country_cd". Yo...

The routines you need to use are:

DSAttachJob()
DSGetJobInfo()
DSGetLogSummary()
DSGetLogEntry()
DSDetachJob()

That entry means that it took approximately a second to start up all the processes necessary to run the PX job, and less than a second to actually process the data.