DSXchange

That "nutsvr4.exe" error is coming from MKS NuTCRACKER 4 which brings Unux capabilities to Windows. Somewhat surprised that the latest versions of DataStage include it as the MKS website shows it as a 'legacy' product: MKS NuTCRACKER Professional has been replaced with MKS Toolkit for Ente...

That sounds buggy, I'd report that to your official support provider.

Speaking as someone who was once forced to re-invent this very wheel, I can attest to exactly what a PITA it can be. One trick to avoiding accidental substring matches is to always use a bracketing character like a space and then include that in the pattern to search for and replace. For example, fi...

The names are pretty self-explanatory in my opinion, however it might not be clear when you would use one over the other. 1. Export job designs with executables: Both the 'design time' information (what you see in the Designer) and the 'runtime code' are exported. This way it can be imported into an...

... and the resolution was???

Are you getting this error from DataStage or the source database? Can you post an unedited / complete version of the error please?

Sounds like (at the very least) you are missing the path to that shared object from your "shared library path" in the dsenv file.

GaneshLoganathan wrote:Adding to this I finally got this error. Don't know where the problem is

Nothing you posted is an error, the "I" is an Informational message while the "W" is a warning. Is there an actual "E" record further down?

Delete away - from the GUI, of course. And no, deleting "all" of the projects won't affect the template.

I believe it is a right-click option available from either the stage or perhaps the saved metadata itself...

Can you not generate the schema file? Or at least "a" schema file? Sure seems like that would answer all of your questions.

No, they (the Connector stages) are not available in the 7.x release. Ray and I were discussing the 8.x release, meaning they were there from that outset... the 8.0 release.

For a more serious answer, the first design is doing a direct database lookup to the reference table while the second loads the reference data to a hashed file and then does the lookup against the hashed file. 'Performance' is such a relative term and would be highly dependant on what the reference ...

Sunny, please start your own post and let us know exactly what this "same error" is that you are getting.

Then contact your official support provider.