DSXchange

Unfortunately, 7.5X2 does not support NLS.

I am currently running 7.5x2 with NLS enabled.

Can a network name legally begin with a non-alphabetic character?

And thank you - anyone who has the same issue in future can now find a solution, with reasoning to convince their DBA.

I can see that Collection, Location, Package, Package Owner and TCP Port have changed. Can you shed any light on why the new values are good and the old values are bad?

Do you mean PX or TX? You've posted in the parallel (PX) forum, but asked a question about TX (Mercator). The answer will be different in each case. In a parallel job I'd use a Transformer constrained to output only when CODE is 2. I'd store the code 1 column values in stage variables conditionally ...

Some examples of values where it succeeds and, particularly, where it fails may aid the diagnostic process! You should be able to capture these via a Peek stage connected to the Transformer stage's Otherwise/Log output.

Ocean wrote:Look like I've been running out of time.

Don't worry too much - server jobs will be around for a long time yet.

All of that is entirely predictable given the differences in data types.

Try an explicit CAST when selecting the data. That is, instead of selecting the Decimal(6,0) column called Col3, select CAST (Col3 AS DECIMAL(6,0))

Welcome aboard. :D The answer is no. The only version of DataStage that supports execution on a Windows platform is 7.5x2 (not the same as 7.5.2). Even this release is not supported on Windows XP Professional server; it can be installed and will work, but you're on your own if you need support. Data...

It would be better if you research this yourself. The mainframe.pdf guide is part of the standard DataStage manuals. Read about the various file handling stage types, particularly Chapters 3 and 4.

The first match "consumes" the 100 10 x row from the second Data Set. Therefore other "matches" are reported as inserts.
Try identifying both COL1 and COL2 as keys.

Is it Decimal(6,0) or Integer in SQL Server? You are not generally allowed to lie about the metadata when connecting to database tables.

No. Even with DS 390 you would use an FTP stage to transfer data to the UNIX server.

Start with one row per transaction. This should work.
Increase it to 1000. This should work also, since DB2 can easily handle 1000 row transactions.

Ask your DBA whether the database can handle a transaction containing 1 crore records, and be prepared to run for cover!

No practical limit.

There may be a limit to the length that you can enter as a default value, imposed by the grid control rather than by the underlying technology.