DSXchange

Valid, perhaps... but does it make any sense? What exactly would we be setting Ans to when Club equals 'c'? TRUE?

DS_MJ wrote:If Club = 'c' THEN COUNTRY_CDE = '2' else '0'

Your syntax is invalid... else what is zero?

Plus you need to set the value of Ans as that is what is returned when you call the routine. Are you doing that somewhere?

This was before your version was out there... this is the one by Manoli Krinos, M Ruland and TJ Griesenbrok. All I did was hook WinZip into it. I don't see it doing anything 'special'. It logs the locked jobs error and skips them rather than trying to unlock everything. Kim, is your version on your ...

Interesting... I'm using the DSBackup batch file from ADN which loops through all projects on a server and then exports them using the same command. It doesn't "abort" if jobs are in use, it skips them and goes on.

Perhaps you should grab that and take a look at it.

Basically, the answer is to not perform the update when there is no matching record. Oracle doesn't consider that an event worth noting, which is why you can 'get away' with it, however DB2 does. You need to use the oh-so-common technique of hashing up the current business keys on file and then only...

It's a good idea (and should actually work!) provided your query can always be hacked into four parts like that. In keeping with the DataStage Way, you should really mention all of the fields being selected, not just short-cut it with an asterisk like that. The question about the bug and a possible ...

Excellent, glad to hear that.

Good, .dsx format is best for this and saves an 'extra' step when importing.

Explain to us exactly how you are getting the export file from your desktop to your laptop. Assuming the export doesn't start off life corrupted, something in your transfer process is corrupting it.

Yup, that's exactly what he said... and he didn't mention any 'loop mechanism'.

Excellent.

SP2? Patch? Anything come of that?

You didn't read the whole post. They are passing the entire query as a parameter, not just the piece you've shown and they used to illustrate the problem. Your solution is fine (and exactly what we do) if that was all that was being sent. Sometimes there is no solution as DataStage will strip quotes...

Not sure when it all changed, and I do remember having to validate jobs to get the hash files created 'back in the day', but it definitely works as described nowadays in the 7.x release.

Sending data to a hashed file does not, of itself, create the hashed file. Do you have the "Create" check box checked in the Hashed File stage? Um... sure it does. You don't need to have that option checked for the job to create the hash. Of course, if you don't choose that option, then you get all...

Question for the group as I have no MetaStage experience as of yet. My client made sure they ordered the 'latest copy' of MetaStage after sitting on the license for two years. Now, the problem is the other components we have are all at 7.0.1. Since I don't know how DataStage and MetaStage co-exist, ...