DSXchange

It is a tool and skill that a DBA would have, not necessarily that a DataStage developer would have.

That could be done with a single expression; you could store it as a reusable component (as a Transform).

Maybe your Oracle date picture is set up to require an alphabetic month. You can use TO_DATE function in Oracle INSERT statement to "translate" from other formats, or generate a date in the expected format. Find out (perhaps using a SELECT statement) what your default Oracle date picture is.

Create a job that retrieves them from Sybase into a hashed file. Use key names that map to the parameter names. Use UtilityHashLookup() or Trans() - note that the name is case sensitive - to retrieve the parameter values from the hashed file. Use them directly in the job sequence's expressions if yo...

Welcome aboard. :D

This question needed to be posted in the DataStage Server forum. The forum that you chose is for a completely different product, the DataStage transformation extender (TX).

Post in the correct forum, and I'm sure an answer will be forthcoming fairly quickly.

The correct solution is to get a better requirement. You have DataStage, with the ability to connect to Sybase and move data to and fro, built in. Why do you want to write in code what you've spent lots of dollars to buy? It makes no sense whatsoever. Connect via a job. The job can capture the Sybas...

The data are being parsed correctly according to your metadata. You specify quote=none, so the quote characters are treated as ordinary characters. You now have four comma-delimited fields. That's what you've described to DataStage. If your data are coming in in inconsistent format, harrass your dat...

Not according to the presentations about DataStage certification at IOD 2005. All correct or not correct was the story.

Returning to the original topic, the "Best approach for unknown varied source" is, in my opinion to push back hard against such an insane requirement. At least demand a small and finite number of possible formats, and some easy means to detect the format in the first line of the source file.

No it doesn't - it produces its output into the virtual Data Set whose control file name is 'Median_19:ln_op_Median.v' What you have posted is a small piece of the generated OSH. While it is true that this is logged, it is NOT the event that reports any error. Is there any event in the log with a se...

It is possible to create a batch, but all you get there is sequential (consecutive) dependency. Do you really want to execute ALL the jobs in the project? What would that achieve? Far better is to create a job sequence, in which you have all the controls a scripting language has, without the need to...

7.5 applies the rules more rigorously. Earlier versions treated Decimal and Numeric as the same, to all intents and purposes. Correct the imported table definitions, then re-load them into your jobs.

Is the same delimiter used within lists as well as between fields (lists)? If so you have a major parsing problem on your hands. The easiest way would be to employ the multi-value handling capabilities of hashed files or UniVerse tables - write multi-valued fields to, say, a UV stage then read from ...

Have your DB2 DBA enable tracing so as to capture the value that is generating the error.

Do you really have a table called "014"? Do you have a job design that has "014" as the table name in a stage?

Employ a pair of Code tags to make your "ASCII art" appear correct.