DSXchange

No. If the database server does not send DataStage any information then there's no way that DataStage can act/react. And there are no settings within DataStage that govern which errors/warning are or are not sent from SQL Server. At least none of which I am aware.

Routines run from the test grid are executed by dsapi_slave. It is that user whose data stack size is limited. You can not infer anything from this. You need to execute the ulimit -a command from within a running job (perhaps as a before-job subroutine via ExecSH) to find out what's really happening.

There must be no space between the activity variable name ($CommandOutput) and the "<" character.

It isn't C:\Test.txt though, is it? The error message complains about /PROD/etl/Prod_Folder/CLIENT/LH/holdings.TXT as the file that could not be found. Presumably it is the file created by the first job - can you confirm whether this is the case? Then you will need to diagnose why and how the second...

You've all missed the vital Len() function. Assuming the target is a string data type: The conversion to string for the Len() function will occur implicitly.

Define "efficient" in this context. Each stage performs a different tasks - that's why more than one stage type exists.

Is this an interview question?

What about "E" ?!!

You will probably find that the Visual Studio C++ compiler needs to be installed before DataStage server. So you're probably looking at uninstalling DataStage server too.

Redirection within DataStage/SQL is not permitted. The required permutation is

It's a reasonable assumption. Only Transformer and Build stages require the C++ compiler. The fact that /opt/SUNWspro/bin/CC was not found suggests that the compiler is not actually at that location. Find out where it really is, and set APT_COMPILER and APT_LINKER environment variables accordingly.

These will be speific to your site. We can not advise. Consult your network administrator.

Whenever a BCI function returns SQL.ERROR you must remove the error information from the handle. It is pointless proceeding until you have done this. Repetitively call SQLError() until it returns SQL.NO.MORE.DATA. Search the forum for examples. You can not simply assume that everything works when us...

I suspect that the job itself had been deleted but the index(es) had not been updated. DS.REINDEX does not remove deleted jobs from the Repository, but will remove out-of-date references to deleted jobs from Repository indexes.

The command to remove partially deleted jobs is DS.CHECKER.

Not possible. And what you're doing has to be done in a stored procedure; the ODBC stage only permits regular DML statements. In DataStage you would be easier selecting week (and year) and performing the transformation to quarter within a Transformer stage. Use a single query. SELECT W_wk, Y_YR FROM...