DSXchange

You will find your answer by searching in the correct forum. Do an "all terms" search for View Data decimal

Something is using port #23. Find out what it is and halt it.

Structure of the metadata repository has not really been documented for version 8, though you can deduce the same from the scripts supplied to create it. You might also like to try your working approach with DS_METADATA.

Welcome aboard.

There is not enough information in your specification. For example how are you starting the job, and how are you detecting that its status changes? In particular, how do you detect a status of starting then the transition from that to running?

There is no such utility "out of the box". You need to identify them, and then execute a DELETE.FILE command against each. You can, of course, do this programmatically or in a DataStage job, but you do need to identify which hashed files need to be deleted and which do not. DO NOT delete any hashed ...

current_date()

You don't even need a parameter - a stage variable will do. Initialize it to current_date() and don't put in a derivation expression for it.

DataStage is (correctly) showing that it sent 1039 rows to DB2. DB2 rejected some of them. If 939 were inserted that would suggest that 100 were rejected and, further, that you have 100 warnings in your log showing why.

In the UniVerse SQL Reference Guide (or simply from knowing SQL standards) you would find that the correct function name is CHAR_LENGTH.

You can do it in one job - in an after-job subroutine - but I think after a while you'll see the benefits of the more modular approach you've taken.

Because there is no command on the server that can be used to compile a job.

Some kind of remote shell program on the UNIX machine to run the program on the client?

Wrong, wrong and wrong again. A Search of the forum will find the correct design time table names, which do not include DS_SUBROUTINES or DS_STAGES. No BASIC code has a .o suffix. Such files are more likely to be compiled C++ code (particularly since the job type is marked as "parallel"). Run time m...

Looks like you've set either DB2INSTANCE or APT_DBNAME to the system name rather than to the database name.

Welcome aboard. The code referred to is in the subdirectory RT_BP1045 and in the file called JOB.1109891624.DT.1444474461.TRANS1 - this is the code generated by your Transformer stage (the actual name of the stage is documented within the code). Look in and around line number 394 to see whether you ...