DSXchange

Confusing. Are you saying that each record in the master job triggers another job that runs a proc for just that row? If so, no wonder it is horribly slow. What does the proc do that is so important you can't do it directly in the 'master' job?

First thing would be to check if the process is running, typically running is a big part of "up", if server means DataStage here.

ps -ef |grep dsrpcd

Note the correct spelling.

It's $PROJDEF and the job just knows what that means - go get the Project Default value for this environment variable that you set up in the Administrator. So, create the variable first and assign it a value then add it to your job and change the default there to $PROJDEF.

You show as a charter premium subscriber, did you let it lapse? Regardless, nothing worth marking that way so I unset it.

Add AND NAME NOT LIKE '\\\%' to your query, see if that helps.

You are selecting both job name and category in the query, is that not what you want?

If you are seeing the "category" records as jobs, then you need to filter those out, something about where not "\\\" or some such - a search should turn the exact syntax up.

I don't think price really is the issue here. My current client is running 8.1 on a 32bit version of RedHat and had some interesting experiences getting it up and running before I got here. Their biggest complaint was that the Linux port seemed to get short shrift, meaning things that had been fixed...

Guess I'll put together a FAQ, getting tired of explaining this over and over.

OK, I guess I'll just step aside, then... here I was thinking you were asking about an automated solution. Ah well.

Not sure, perhaps it ignored them or wasn't bothered by them. Still you need to know what they mean as you will run into them everywhere when syntax is being documented.

OK... do you have a supported compiler installed on the DataStage server? Have you configured DataStage properly for it?

Good! Now please mark the post as Resolved using the button at the top of the screen.

Remove Duplicates stage, more than likely.

"There is an error in XML document (3, 490). ---> System.FormatException: The string '' is not a valid AllXsd value." Looks to me like you've sent an invalid message to the service. Verify that you can produce valid XML before you add the actual service call to the job.

Those square brackets are a documentation convention to denote an optional part of the command. Thus they are not an actual part of the command.