DSXchange

There was no reason to ask this twice so I removed the stand-alone post on the subject. All the documentation I see only lists two possibilities for the source as you note: DB2 and Oracle. AFAIK, you'll have to take another tack for SQL Server, either just let DataStage generate them (if that is a v...

Read the last reply in this post.

There's some official IBM documentation here on both reading and composing JSON with the stage.

Since they've already said that they "know these stage variables are not written in the best way" I wasn't going to bother to point that out. :wink: And just for the record, no clue why the order would matter here seeing as how one is not dependent on the other. :? Seems like something to ...

Welcome. First order of business is to get your post into the proper forum... this one. Done. And then we need to correct a deficit caused by that other forum - a lack of details, your particulars that are required for a post in this forum. Can you edit your post and let us know what your DataStage ...

Upgrade to at least 9.1 and that functionality is built into the Sequential File stage.

Yay!

:D

viewtopic.php?t=109198

I called him that a couple of times and he adopted that sig.

I'll save Ray a little work the next time he shows up and ask... do you have an actual question for us? Something specific you are looking for or just generic advice on your situation / error?

My assumption would be it is a NUMBER in Oracle with no specified precision which is why you end up with a float. You wouldn't be seeing this issue if it was declared as something more like NUMBER(16,2) for example.

Any files need to be 'local' to the DataStage server in order to be consumed, either via a share mechanism or transportation. Once there, you have a couple of options on reading native Excel files if you don't want to go through converting them to csv first. One would be ODBC for Excel but I don't r...

Support.

A typical solution (and what we do here) is have a DBA created procedure to do the actual task which our functional ETL user is then granted the privleges needed to execute.

That same number is in the back of my mind... 200 to 250MB was our limit on our HPUX system, I do believe. Thankfully, our sources generally were of the mind to flood us with a metric crap-ton of small files.