DSXchange

It's not recorded in a file. It's recorded in an entry in a database table in the repository.

Oracle can not deal with data with multiple levels - this is a COBOL convention.

If port number 8080 does not work, can you open the WebSphere App Server console (port number 9060)?

The error you posted relates to compiling a job (specifically a Transformer stage), not a routine. The Routine is compiled externally to DataStage. Have you done that successfully? Have you create a "parallel routine" interlude in the repository?

The largest possible signed four byte integer is 2147483647. Unsigned integer can be twice this size only. Prefer to use eight byte integer (BigInt) if your values are larger than the limit allowed for four-byte.

That is not actually the solution. On the run where the job aborts the Exception Handler should fire. On the later run where the job is reset then runs OK the Exception Handler correctly should not fire.

The extra line will always be there, because there's a line terminator at the end of the penultimate line. Perhaps you need to detect it being empty with a simple If..Then..Else expression.

If there are no delimiters, how do you know there are rows and columns?

Do you have any description of the file's alleged format?

Are there separate lines in the file? If so could you post just a few of them?

I would prefer to use the Left() function, as it's self-documenting. If you need to handle upper-case letters too, simply wrap the input column reference with a Downcase() function. Len(Convert("abcdefghijklmnopqrstuvwxyz0123456789", "", Downcase(Left(InLink.TheString,1)))) Here ...

That's not a problem. Do you mean field delimiters or record delimiters? If the sequential file has no record delimiter it contains at most one line, so that's not a problem. If the data structure lacks field delimiters then either there is only one field or the fields are identified by their length...

Get version 8.5 and use a looping construct within a Transformer stage. Easy! Until you do that, the easiest way is simply to write to a text file (the Char(13) characters become line terminators. Then (in a separate job, if you're using a parallel job) read back from that file. Otherwise you can pa...

The project default NLS map can be overridden in the Job Properties in the NLS tab. I suspect you need UTF16_PlatformEndian (or perhaps UTF16_OppositeEndian), but make sure that it is the compatible map for the NLS setting used for Oracle. It will need to appear in the mapping file.

Have you tried using a Complex Flat File stage?

Just passed it. At IOD. Same level of difficulty as the previous one - after all, not too many changes to DataStage between 8.0 and 8.5. Needless to say, many of the questions relate equally to 8.0, 8.1 or 8.5. But, yes, there were some questions about the new version; I faced one each on looping in...

Integers are stored in binary form. You can not expect leading zeroes to be preserved. Only the value is stored. To display with leading zeroes you must use a string data type.