DSXchange

Floating point numbers can not be accurately represented in computers. There are hundreds of papers out there explaining why. ODBC drivers typically treat floating point numbers as decimal, applying some kind of function to fix the number of decimal places according to the metadata. It's perhaps a "...

Keep a dynamic array of link names that you have processed and only process if the name is not already on the list. This approach will not be appropriate if your job has duplicate link names. * Initialization LinksProcessed = "" * Have we seen this link already (it connects two active ...

Different job, same logic but different Format in the Sequential File stage that reads the file. Delimiter can not be a job parameter. Rather than parsing the fields out of a single string, they will now be parsed automatically for you.

Therefore

No idea. What does your job log tell you about the connection?

Unless you are using Oracle for the XMETA common metadata repository, Oracle connections and performance statistics should be completely unrelated.

No idea. What does your job log tell you about the connection?

With the century break correctly set, %yy for year in the date format string should yield the desired results when you have two-digit years.

What does /appsdb/lvoradb09/opt/IBM/InformationServer/Server/Scratch/ora.6396.205060.0.log tell you?

(a) If you're trying to display fields from the hashed file itself omit the word DICT from the query. In what sense do you mean "fail"? (b) (i) Correct (b) (ii) Incorrect. Without a mask data will "wrap around" in the column when a report is generated. The mask truncates the data, not the field widt...

It's planned for DSXchange version 3.0, which is currently in beta.

IBM DeveloperWorks forum allows for attachments (not quite the same thing).

ProfileStage?

Moderator: please move to Parallel forum

Whatever you specify (as Null Field Value) for a field in a fixed width sequential file must have the correct number of characters for that field. If null comes in out of your job, it will be converted to that value as the row is being exported to the file.

You might be surprised by the answer!

There IS an Aggregator stage in server jobs. It should be in the Processing section of your Palette. You can also drag it from the Server\Processing category under Stage Types in the Repository. You can also do counts using a Transformer stage. Indeed it does them for you, via the @INROWNUM and @OUT...

Do you have a TRUNCATE option available in IQ ? This is a very fast way to delete all rows from a table. If so, you can run it as the Pre-insert command (Properties tab on Inputs page).