DSXchange

Forgive me... it's 5:30 in the morning, the coffee isn't ready yet and I haven't had much sleep... but I think what you'll find is that it isn't DataStage that is case sensitive, just UNIX.

Ah... that's what BOM stands for. Duh. :wink: There are many resources available online regarding the conversion from one 'endian' to another, for example this one. I'm wondering how the file gets 'downstream' from the Linux system, perhaps this transfer mechanism (something like Connect:Direct I im...

mandyli wrote:just AIX team upgrade os level 6.1 to 7.1 and upgraded C++ compiler 12.1

That's one pretty big "just". Did you confirm before this went forward that your version of DataStage is certified to run on/with those?

Which approach, he did mention two after all.

If you were on a UNIX system I would suggest checking to see that your kernel parameters are all properly set as it sounds like something is on the low side. No clue how that translates over to the Windows side of the world.

Short answer? Yes. Assuming none of the derivations are 'global' or could be used across multiple fields or easily combined. It's about style and readability, I'd use as many stage variables as it took with self-documenting names in order to make the cooking up of something complex much easier to un...

Welcome.

For the record, routines that are used in the Before/After Job areas or in Sequence jobs are written in BASIC not C++ so there's no need to throw that compiler at it. Where are you planning on using this?

Scroll down to the third box on the right-hand side labeled "Document information".

Okay, wasn't sure when they came into being but the link I posted does say "Software version: 8.1, 8.1.0.1".

Well... still obviously some kind of codeset issue, though I couldn't tell you what you got there on the LINUX side. For both input and AIX, this: "f1f0 f6f1 e3c1 40d4 4040 f0f0 f0f5 f0f0" = "1061TA M 00500" This, the alleged equivalent on the LINUX side: "bfef efbd bdbf bfe...

devsonali wrote:Secondly in the following conversion - Isn't the format we mention after the actual column refers to incoming data (in this case timestamp) format ?

TimestampToString(lnk.TS, '%yyyy/%mm/%dd %hh:%nn:%ss')

No, it always refers to the format of the string.

Sorry but are you saying you don't have the tool installed and are looking for it or are you wondering if it will work for certain stages? It lives under: Start > Programs > IBM InfoSphere Information Server > Connector Migration Tool according to the docs located here. Not really sure what stages f...

Doesn't that need to be a Range Lookup?

Perhaps this is something you've already looked into but there are 48 other posts that mention lookup stage partitioning and that "could not map table file" error message and the things people have done to resolve it. For whatever it is worth, here are my adventures with the problem from b...