DSXchange

Did you search here for that message? I ran into the same issue but for us it was from an increase in the number of web service calls and the defined invocations were overrunning their queues. Haven't seen any other reason for that message, personally. Hopefully IBM will shed some light on it, or Er...

I for one have no SAP experience, so my only thoughts would be to wonder what IBM / your official support provider had to say on the subject of SAP support in the various releases.

Assuming your syntax for 'dsrecords' is wrong, you might want to search the forums for the proper syntax. For example, this post is one of many that came up for me when I searched.

So... one stage doing both things at once? Two stages? The former would be a problem. For #2 you'd need to post the syntax you are using for anyone to be able to help.

The technique that Pagadrai mentioned is discussed in this FAQ post by the way.

That would be my first guess as well. There's one in each project directory and since "&" is a metacharacter you'll need to do something like this to get into it: cd \&PH\& Pretty common to have a cron script that keeps this pruned, deleting anything there over X number of days...

previously all my jobs are running fine now I am getting this warning for all the jobs. Well... that certainly would have been a good thing to mention in the first post rather than making it seem like an isolated incident with a particular job. :? All the what jobs? All jobs that deal with any flat...

That's a "range lookup" and if you do an exact search on that phrase you should find all kinds of conversations on the topic.

Good as that was going to be the suggestion. And this gives other people who need to know the answer when they search, so thanks.

It would help if you detailed the settings and file path/name you are using in the stages and if you had any idea if the problem was on the source or target end. Otherwise we're totally left to guess.

Not sure why something like this would be "urgent". :? First thing you'd find searching here would be an error from "CombinedOperator" gives you no clue as to the stage giving the error. Disable Operator Combinality and then post the error. In the meantime, search for a generic p...

Why not just go to the third job in the Director and press the "stop" button?

So... what was the resolution?

Pretty hard to make any judgments with no evidence before the court. Post the syntax you are using in your script to run the jobs.

What are you putting as the Server to login to? If you haven't already, try 127.0.0.1 rather than any name or network IP. Or you may also need a "loopback connector" but I'm not positive about that, not sure if they are needed nowadays.