DSXchange

SPINTRIES and SPINSLEEP ought not to increase memory demanded by dsprcd by more than a few bytes. Certainly not 6GB.

Command not found means that PATH is not correct.
Library not found means that LD_LIBRARY_PATH (or SHLIB_PATH or LIBPATH) is not correct.
In either case you might also have a permissions issue, but this is less likely.

That looks OK at a glance, but can you compare it with the DSP.Close entry in another project?

What precise version of DataStage?
Please post the derivations of your columns, so we can attempt to reproduce the problem.

Has this always been so? If so, it may be that the project was not installed correctly. If not, it may be that someone has overwritten or deleted the VOC entry for DSP.Close. Inspect this entry in any other project, and mimic it in the project that's having the problem. Before you do that, however, ...

You may, briefly, have hit a limit of the number of dynamic hashed files open at the same time (set by the T30FILE configuration parameter). Or you may have briefly hit a system-wide limit on the total number of files permitted to be open.

If it's a timestamp with "-" as delimiters in the date part, and all you want to do is change these to "/", then the Convert() function is perfect.

It really depends on what tools you have available. Yes, you can issue calls to functions like printf(), but these end up in a file in the &PH& folder. Of course, you can direct any output to a file. Your C programming environment may have its own facilities, such as a debug object. Check; t...

Precision must be at least one larger than scale. Decimal(8,8) is not an acceptable formulation; you need at least Decimal(9,8) to accommodate eight decimal places.

Thanks for posting the solution. It results from the server being set up not to accept inbound FTP requests, requiring secure FTP (SFTP) instead.

Is the debugging option (-d option on command line) used when dsrpcd is started? This certainly seems to be way too much memory. Your support provider will be able to help; they can guide you through configuring malloc tracing. [Note to all others: I will NOT discuss malloc tracing on DSXchange - it...

Hang on, you're the consultant, you're being paid for this POC? But you want us to do your work for you for free? If you are interested in a commercial arrangement, please revert in those terms. Both tools are good - otherwise they would not be where they are in the marketplace. The approach the ETL...

Job logs are only purged if the job completes successfully. The log of an aborted job is not auto-purged.

Start by setting APT_DISABLE_COMBINATION to True so that you can fully isolate the location of the problem. Let us know what occurs under this scenario.

InitializeKey is one of yours, Ramona, it does not come out of the box. It may have been sourced from DSXchange, but it's not part of "standard" DataStage.