DSXchange

You are correct, out of the box. It would be possible, of course, to define a business process within the Stewardship Center that checks who the author is and not to allow acceptance of the approval task unless different from the logged in user.

Yawn

A silent scream for coffee.

On a twos-complement machine 9999999999 would have wrapped around, setting the sign bit for an Integer, which is why it would be interpreted as being less than 111.

Actually these properties can be used with delimited files, though it's not as efficient as with fixed-width format files.

One of the changes for version 11 was the use of HTTPS for connections.

True, but there is a certain minimum patch level that you have to have for 11.3. I don't have those details with me at this time.

The date is stored as a date.
What it looks like depends on the Oracle date picture set for your session. You could change that, or you could use TO_CHAR() functions when reporting.

It's in the presentation layer entirely. Your data have almost certainly been loaded correctly.

Why are you using the ",5" piece? Your numbers do not appear to have any decimal places. Have you tried using Decimal as the data type? According to IEEE standards, Double can never be assured to stored with perfect accuracy, even though you've clearly specified a large enough mantissa. Ma...

Without addressing your particular problem, I observe that 2.14748364700000000E+09 is the largest 32-bit signed integer value.

And also that 999999999 can be represented as a 32-bit integer byt 9999999999 cannot.

Use the Server Job Sequential File stage, possibly within a server Shared Container. This stage type has the ability to handle internal line terminators (in quoted fields) out of the box.

I had the thought that maybe they (IBM) could put something like NOWARN into the properties of the Transformer stage, but my second, better, thought was that that would lead to too much lazy programming.

In version 11.5 there is a business process management layer one can add to Information Governance Catalog to provide the mechanism I was seeking. It's part of the Stewardship Center. DSXchange ran a couple of webinars about it earlier this year. Stewardship Center for Information Governance Steward...

Typically you would run a character investigation over the unhandled patterns, specifying a few (I use 5 usually) in the sample size. The frequency distribution will immediately suggest where the most benefit for your effort would likely obtain.

It's not a bug; it converts both to Integer before performing the comparison.

Use a data type conversion function in the comparison expression to force DataStage to compare both as decimal data types.

My guess would be that the last line of the script lacks a line terminator.