DSXchange

Perhaps they could make it "nearly 50000".


It is, rounded to the nearest 50000.

Technically, though, "over 20000" remains correct. The actual number can be found on the right hand side of the page (you may need to scroll down).

Yes. Easy from Sequences, you can use the SDK routines such as UtilityInfoToLog(). Less easy from parallel jobs; what did you have in mind? One way is through before-job or after job subroutine but, if you want row-by-row logging, you will need to implement this yourself by creating a C++ function t...

Now it's even more confusing. Is it 10,000 or 100,000 ?

It is more usual to use the target as the "before" input, because that's what's there before you attempt to apply the new data from source.

Add a Peek stage immediately after the Difference stage to determine precisely what the Difference stage is reporting.

They can be edited in the Administrator client by a user who is credentialled as a DataStage Administrator.

There are only three possibilities: DB2 version 9, Oracle version 10g and SQL Server 2003 (only on Windows platforms).

Assuming that CLAIM_AMT is a string, and that the "$" you wish to remove is in the first character position:

The requirement is decidedly unclear. Which 100,000 records do you load into the output file? The first 100,000 for the day, the last 100,000 for the day, or is it based on some other criterion? What is supposed to become of source records not loaded into target on any particular day? Will the same ...

Not on the table itself, but on the SYSTEM TABLES where the table and column definitions are stored. Check with your DBA.

What if the fatal error is of the kind "can not load into Oracle"?

Fair comment. But "fix" may be difficult in all cases unless your rules are rigidly designed.

Does "Hi" performance mean your job generates a "Hello" message?

Please strive for a professional standard of written English on DSXchange. It helps those whose first language is not English.

Look at the log for the sequence itself. Right near the end is an event called "summary of sequence run". This event alone will provide the information you seek.

Nirdesh has taken the trouble to type out the horizontal pivot example from the manual, whereas what you want is a vertical pivot. As noted, you can find solutions via Search of DSXchange.