DSXchange

Invocation IDs (which can be parameterized) and other job parameters "decided at runtime" are easily accomodated in the Job Activity stage. IMHO, you'd be best served by going that route.

If you really want to go the ExecSH route, post the routine code.

OK... you are wrong. And welcome.

Keep in mind the Job Type being discussed when replying. This is the Server forum so no "Remove Duplicates" stage and hence the recommendations to use a Transformer.

Same topic as this?

You just repeated information you've posted before and didn't answer my question. If you need to match on COMPANY_NAME then you'll need to build a different hashed file with that field as the key.

Asked and answered many times here. Do an exact search for "Controller problem: Unhandled failure".

From inside uvsh (or dssh nowadays) I would try doing a LOGTO to the project in question if you don't start off there and then launch 'DS.TOOLS'. From there you'll find an entry to 'manage locks' from what I recall and a dozen tools under that. See if anything there helps.

samyamkrishna wrote:what am i doing wrong?

Running a job using ExecSH from a routine activity stage. Any particular reason you can't use the Job Activity stage?

You do realize that you've just repeated information you've already posted and didn't address at all the question that Ray asked you, yes?

:? I'm a little lost here. Hashed files do not allow duplicates per key and thus operate on a "destructive overwrite" basis - a.k.a "last one in wins". So you can't have five records in the hashed file lookup for the same key value. Can you expand on what I assume is your workaro...

From what I think I recall, you should separate the two portions of the file when using a pattern, so for the filename just put the path parameter there and then in the file pattern just the "pattern" itself - Test*.txt.

Is there a way wherein I can include a dynamic query in the ODBC stage, wherein the query would fetch records for only the selected Employee Ids, and not the entire table? I don't see why not. I'm not sure I'd go the 'dynamic sql' route but perhaps look into loading the IDs into a work table and jo...

Pandeesh, why not search the forums for JOBTYPEIND? All that you seek is already here.

Let the stage generate the SQL, what you have right now is invalid for your purposes. To "join" on the ID field, it has to be marked as a Key and properly included in the where clause.

Do you have anything 'official' for the target XML? Say, for example, an xsd that defines all aspects of the elements? If not, can you get one?

The Internet has all the information you'd ever need, make use of your search engine of choice. As noted, your System Administrator is the only one capable of actually making any changes, you'd have to get this by them first. Go talk to them.