DSXchange

In DataStage, KB is always 1,024 bytes, MB is always 1,024,576 bytes, and GB is 1,073,741,824 bytes. Never bits.

Or 1,024; 10,24,576 and 1,07,37,41,824 on the sub-continent!

I wasn't asking you to; I was suggesting how you can make the data easier to view for yourself.

Separate jobs. To truncate a table, generate just one row (to trigger the operation) and use user-defined SQL. Or, if the stage type permits, choose "truncate table then insert rows" as the load method, so that you don't need to re-invent the wheel.

Only one version of DataStage can be used to execute parallel jobs on a Windows system; that is version 7.5x2. You need to obtain a copy of that specific version (the "x" really is part of the version number), and a licence for it. If you have a DataStage client installed, then it will be able to di...

It's not possible. Passive stages, like the ODBC stage, only expose methods for performing tasks. Active stages, like Transformer stages, generate processes that actually invoke those methods.

This is a tab-separated report obtained by enabling stage tracing from the Job Run Options dialog when issuing a job run request and checking the Statistics check box. Copy it from there and paste it into a tool like Excel. You can use it to identify the "hot spots" within stage execution. Your stat...

The behaviour of the control suggests that the upper limit is 1024KB. In a quick survey I can not find a limit documented.

You need to specify the correct number of delimited columns on the Columns grid. You can, indeed, specify more than exist in the record, and use the Missing Columns property to handle those situations. What happens when you try to import the table definition from that sequential file and specify 168...

Lookup keys are disabled in the Lookup stage (a) when the reference input link is fed from a Lookup File Set stage or (b) when the reference input link is fed from a directly-connected DB2 Enterprise or Oracle Enterprise stage. In both these cases the key is already known. The stream input link must...

Are you convinced by now that the FTP stage can not use environment variables in the way that you want? Every test you've conducted has verified that this is the case. If you want the product changed, you will need to make a business case to the manufacturer.

Have DataStage dump the actual schemas that were used. Set the OSH_PRINT_SCHEMAS environment variable.

As I noted, Nvl() may not have been directly used in the job - it may be called from some other routine that is used in the job. In such cases you will not find it in an export of the job.

What are you doing to the date in the Transformer stage?

Is the date actually populated in the DB2/390 table? Could it be null (for example date of death is often null)?

What's the data type? You can't effectively Trim() a Char data type; it is immediately padded to length. You probably need to effect the lookup using VarChar data type on both inputs, or identically padded Char. You also need to ensure that the inputs are identicatlly partitioned or that the referen...

First find out whether your employer has any documented naming standards. If so, adhere to those.