DSXchange

Ask your SysAdmin what the limits are.

Sorry, don't know anything about SAP personally. You can still help others by describing your job design - list of stages used and the general flow would be helpful information.

How many times are you going to post this?

Exactly - don't re-invent the wheel unless you are extremely bored or have time to properly address the challenge. Ken has already done all this hard work for you and gives it away for free. The only 'limitation' I've found is in the parameter handling which works well 99% of the time but occassiona...

Use one or the other, not both. All dsjob options are explained in the Server Job Developer's Guide in the Command Line Interface section. Note that section is way down near the end of the DataStage Development Kit (Job Control Interface) chapter in said document.

I've pulled data like that into a work table along with the mod value (one query) and then MI jobs pull from the table where their ID = mod value.

ps. Server jobs don't have a BASIC Transformer.

Usually means your XPath expressions are not correct. How were they generated?

Don't "continue" discussions in a new thread, stay in the same thread.

Seems to me the only way to avoid having to type in and match 99 'words' each time would be to load them once into some kind of lookup structure. Then parse your source down and throw each one against that lookup to see if you get any hits. Other than something like that, I don't see how you do it "...

Probably, but I'd be surprised if it's a limit you need to worry about. How many values or loops are you planning on needing?

No - you solve that particular problem by becoming a Premium Member. I really wanted to post that five times, but restrained myself. If you are still having an issue with this, why not state your remaining issues or confusions? This really isn't all that difficult and you've gotten everything you ne...

Welcome. Help us help you - provide more detail about your problem. Simply stating your error isn't enough - describe your job design and what exactly is going on when the error is thrown. I get the impression you are reading a flat file but that would still be a guess.

I asked for the exact version - 9.2.0.4? 9.2.0.8? Makes a difference, some are buggier than others.

What exact version of the Oracle client are you using? I've seen things like this where installing a 'better' client version can resolve it.