DSXchange

There's no smarts there - those are two completely different paths. On any operating system. What you are seeing is one of the consequences of a 'caseless' filesystem. DataStage has no control over that aspect of its existence on Windows and can't store two files with 'the same name' (where they on...

Ah, yes... Windows. DataStage forces object names to be case sensitive and Windows could case less, happily letting one executable overwrite the other.

Nothing really to fix here other than your naming conventions, it seems.

Ray, you may not be an FBG - but you make the rock'n world go round.

First explain what you meant by your "I don't have the field delimeter" statement. I assumed you meant it was a fixed-width file but let's verify. Is that the case?

Fixed width? You'll need to ensure you have the null handling set properly (i.e. it represents the full size of the empty field) for that field in the file, then it will 'pad' it for you.

Thanks Ray.

And from what I recall - precluded regardless of actual hashed file size, yes?

Some systems use .so files, some .sl so no worries there. And the 'trace.out' file will only be created when you have things working and turn trace on. Again, all fine. Is the 'InstallDir' noted in your post correct? Can you post the section of your dsenv file that shows how you are setting the PATH...

Nothing is stopped any of the other 17,000 members from posting answers to your questions. Problem is most of them tend to shy away from trying to conduct training sessions here, which is what looks to be needed and which is not the purpose of this site. We are a community of users, helping each oth...

and my transformer constraint is If Input.CODE='XXX' Then Input.VALUE Else @FALSE This can't be true. Meaning, this can't be in your 'transformer constraint' but rather must be in the derivation expression itself. That's why you are getting zeroes in your field - @FALSE is a System Variable (look t...

It should be ok to do that, as long as 'that' doesn't change the actual value you put in (and which would be read from) the field.

Funny, mine complain when we do utilize all the available memory.

If you are going to bother to come here and post something like that, at least explain why you believe that to be true. Convict, don't just indict.

Actually, you need one if you want any checkpointing done on the last stage from what I've seen. No output trigger = no checkpoint.

First thought... Why use a script to 'load data into a table', isn't that what you bought this fancy ETL tool for? Why not use a job?

Umm... Daylight Saving Time?