DSXchange

Thanks Mike.

You can provide multiple filters. Try it. You can play with it and come up with your results. Play and learn

DSExecute() is a Basic command and not a routine. You have to encapsulate it in a routine. Do a search on it to find examples.

When you put the entire path of the two files, does the file get renamed?

How in the world can you be on 7.0 px engine and sitting on windows ???

Are you using the same id, both in DataStage and outside DataStage, to connect to the database. If yes then search in google for "SQL0552N" to get more info on the error message. Even your dba can help you with that. It might be as easy as setting a few variables.

50 rows/sec, is that the performance stats for your sql select? That means your network is heavily loaded. The problem does not lie in the hashed file.

Try giving the parameters in the 'Parameter' box. See what happens. For a routine, you just need a few lines to run DSExecute() to run your command at the OS. Read about DSExecute() in DataStage help.

I am one of those who uses hashed files alone for lookups, or database level sql joins. I think hashed files are the essence of server jobs.

WaitForFileTest..JobControl (@Execute_Command_1): Executed: mv #Path#/ OldFile# #Path#/test.arc Reply=1 Output from command ====> Usage: mv [-i | -f] [--] src target or: mv [-i | -f] [--] src1 ... srcN directory Well for some reason its not taking the parameter names. You are also missing a hash si...

Even I am hearing two different things here. If it, in fact is, your machine then a simple re-install should be able to fix the problem.

Trust me, its all well worth it. Welcome aboard, again .

prmuttireddy wrote: Thanks for your reply.Please tell me how to resolve those warnings.

Ray already did. Kumar explained it even more. Now use info in getting your problem solved.

Because its taking the parameter values literally. WHere are you providing the parameters?

Your right Craig. Somehow 'they' got the naming wrong for the function.

Do me a favour, dont type your code out, copy paste it from the buildop. This way we can see the actual code and compare it to the error message. Also surround your code in code tags please.