DSXchange

... suddenly today ... What's different today from other days? Track that down and you are well on your way to figuring it out. What kind of stage is on the other end of DSLink18? (Why don't you give your links meaningful names?) Line 42 performs a "get next row" from link DSLink18. This is where t...

How would you do it in SQL if you didn't have DataStage? That will give you some idea of what you need to do in DataStage. A lookup has to have some mechanism to search. You might write user-defined SQL. Do you need to return all rows? Surely finding just one would match the criterion in your origin...

Certification is not yet available; it is expected sometime this quarter, but the best laid plans of mice and men gang aft a'gley. Certification questions are the intellectual property of IBM; publishing them would bring down the wrath of the IBM copyright police (which I'm informed is not pretty). ...

You haven't identified a key column for the lookup, so the generated WHERE clause is empty.

They're in the DSParams file in the project. Copy the appropriate lines and paste them into the DSParams file in the other project.

I prefer to propagate using UtilityWarningToLog() in a Routine activity. This means that I can retain control right back to the top level, which can instigate some diagnostic activity if required. Never abort! To answer the actual question, the second argument to subroutines like DSLogInfo and DSLog...

It's complaining about the SQL that's being generated in the ODBC stage. Check this SQL to verify that it's valid. Are you using generated SQL? Stage variables are not the problem. BCIOpenRef is a function that opens a reference input link. Since the reference input link is connected to an ODBC stag...

Zero is not valid to be represented as a packed decimal. Search the forum for "PACKED" "zero" (all terms) to find an environment variable that allows this behaviour to be overridden.

In 12 years you, too, can have 12 years worth of experience.

You could interpolate a Routine activity after job 1. You would need to write a small interlude routine that attached job 1, got its start time (using DataStage macro or DSGetJobInfo() function), detached the job and returned that timestamp. The Routine activity return value can be used to supply th...

Only ODBC and UV stage types support multiple row returns from a lookup. You can not effect your design using an OLEDB stage type.

Yes, depending on your version of DataStage. Search the forum for "export" and "server" (all terms).

A Solaris patch is more likely to affect UNIX RPC mechanism (port number 111?) rather than the DataStage RPC daemon (which listens on port 31538).

You can enable automatic purging based on date. Choose Job > Clear Log as if you were going to do a manual purge, but instead set the auto-purge settings. Perhaps to purge events more than one or two days old. This happens at the end of each successful job run.

Welcome aboard! :D
Just use the expression Michael showed you in the post prior to yours as a constraint expression in the Transformer stage, on a separate output link that is for handling rejected rows. Of course, that link must lead somewhere, such as another flat file.