DSXchange

So... 'Not very helpful', eh? Silly me, I made an assumption based on your statement that you "don't have this version installed on my machine" that you actually have Version 8 somewhere, just not installed on your machine. If that's not the case, it would have been nice if you'd been more explicit....

I'd be surprised if it actually takes all that time to do the physical compile. We've seen situations like this in the past, where the compiler license limits the number of concurrent compiles - sometimes even restricting it to one user at a time. This seemed to translate into long wait times for th...

Contact your official Support provider and ask if the Sybase OC stage is certified for use with 15.0 release of the database. If so, I would think it should just require a change to your dsenv file to include the path to the new client in the appropriate environment variable (which I don't recall of...

Yeesh... why log all that? Why not redirect std out 'somewhere else' when you execute these beasties?

So, instead of considering the last part as an SQL statement, it considers it as the file name that contains the SQL. Because you told it it was a file through the use of the '@' symbol. Try removing it and see what happens. Not saying it will work, but worth a shot. Still think you are better scri...

cosec wrote:how can I fix my problem ?

This is a Server job, so... use a hashed file for the lookup, preloaded with any matched business keys from your input set. Update it as the job runs.

Probably worth your time to check out Vincent McBurney's blogs over at ITToolbox. This link should get you started. I recall a series of posts there on the past, present and future of DataStage, plus other goodness including much insight into the latest release...

If it's anything like they've done in the past, you should be able to find them on the client cdrom.

Your 'reference link' is a lookup? If so, when you get a hit on the lookup, include the reference data values in the output column. When you get a 'miss', set the derivation of the column to null.

Or just always include the results of the lookup without checking and the above will follow.

vnspn wrote:I think the format of this statement has been framed should be sightly different for executing it on Windows!

Nope, it's exactly the same.

Huh... I guess our definitions of the phrase 'most recent' differ.

And? What exactly have you tried? What are the bold values supposed to represent? They don't seem to be the 'most recent' effective dates in the bunches, hence the question...

I'm not sure how many Solaris users are here, let alone ones with experience with Solaris 10. You'd be better served by contacting your official Support provider and asking them if that operating system is supported and if they are aware of any issues with running DataStage on it.

Does your syntax work from the command line? Call DSLogInfo() with your ResultText to see what's going on...

You did? Well, umm... you're welcome!