DSXchange

Yes. You need to get the two values into the job sequence - typically via a job that selects them and loads them into its user status area or writes them into a file. Having retrieved them, you would use a Nested Condition activity with a custom trigger expression to make the decision.

Take a look at the shell script Craig mentioned. It's complex only because it must take into account that there may be other instances of DataStage server installed on the same machine. With only one, it suffices to remove all the DataStage objects - the install directory, the hidden files in the ro...

Try reinstalling the DataStage client. The SAP client installation may have added/moved some critical DLLs, possibly the Microsoft Foundation Class.

Did you regenerate and restart DataStage after changing T30FILE? Execute the command analyze.shm -t | grep T30FILE to find out whether T30FILE has indeed been increased.

Most (if not all) stage types have a Help button. You could have clicked this and gotten the answer sooner.

Most (if not all) stage types have a Help button. You could have clicked this and gotten the answer sooner.

There was an unexpected network error.

This is not a DataStage issue, nor is it an ODBC driver issue.

Get your network administrator onto it.

I assume that the statements that idiot-proof the arguments are OK. The main logic converts the delimited string to a dynamic array (which in one sense is just a delimited string with a different delimiter, but one for which there are some useful tools). The delimiter I used is a field mark, which m...

In your version of DataStage the only type of stored procedure that is supported is one that returns a SmallInt (SQL type 5). Apparently your stored procedure does not fit that model.

Apparently you can browse the MQ Series queue rather than destructively reading it.

Information Analyzer uses osh scripts to do its work; they run in a dedicated DataStage project called ANALYZERPROJECT. The DataStage jobs that it runs can be viewed using DataStage Director. However, it is not possible to delete these jobs using DataStage Director: the following message is displaye...

DataStage is a 32-bit application. It must find the 32-bit client libraries. If both 32-bit and 64-bit client libraries must be in the shared library search list, for DataStage the 32-bit libraries must appear earlier.

Eschew the OCI stage if this is critical - the OCI stage doesn't do microseconds properly. Prefer Oracle Enterprise stage.

For DataStage it definitely does. DataStage is a 32-bit application and must find the 32-bit libraries (and must find them before the 64-bit libraries if both are in the shared library search list).