DSXchange

Welcome aboard.

At a first guess you have a "memory leak" problem in your routine, leading eventually to a memory access violation (SIGSEGV).

I don't know why this was not picked up in your earlier environment; maybe more memory, maybe less data.

I can't recall whether it was 8.5 or 8.7 that introduced null-tolerant stage variables. If it was 8.7 then this is the underlying cause of your misery, and why the second formulation works.

Possibly, but with the Change Capture, Difference or Compare stages there's no scope at all. Which is better odds than "pretty darn small" imho.

Only one .odbc.ini gets used, the one in DSEngine (or pointed to by ODBCINI environment variable).

You might like to check the same thing in the uvodbc.config files. There is one in DSEngine and one per project.

Variable RtnValidateLinks has not been assigned a value. You use this variable as the second argument in your DSLogInfo() calls. Were you to double click the Result cell in your Test you would see the same error messages.

No. Not least because there's not really any such thing as a DataStage executable in the manner you are envisaging. Server jobs are stored as components and dependencies in a database table, which are read by the DSD.RUN program at run time. Parallel jobs are stored as generated OSH which is read by...

Thanks for that. Would you happen to have tried using a password encrypted using encrypt.sh in this situation?

I'm going to guess that it wouldn't work, since WAS <> IIS.

We have not tried this. However hyperlinks to published reports stored regularly on the file system are easily implemented in Business Glossary.

Worse than that. It will produce at most 2^31-1 values, but only if your data provide that many distinct combinations. (You can improve this to 2^32 values using uint32, but the same caveat applies.)

Are you getting any other error messages? IS your job writing to anything else, such as a sequential file or a Data Set?

How are your data partitioned on each of the input links?

sonal wrote:You might need to rebuild the indexes on the XMETA repository.

Please advise how to do that.

I have two customers about to implement BGA who would like this more detailed information. Can you please post it here or, if you prefer, send it to me via PM or email. Thanks.

The error message may pertain to the XMETA repository rather than to the local project repostiory.

Please mark this thread as Resolved.