DSXchange

Oracle 10g is supported for the repository, not 11g... at least not officially.

You really didn't need to start a new post for a question you've already asked:

viewtopic.php?t=129396

In the future, please just go back to your original post and update it so people know you still need help with it.

First suggestion is always to search for your message and see if anyone has discussed it in the past. For this, there's only one so I'll just post the link for you:

viewtopic.php?t=123761

Please try to do a better job of picking your subject lines.

Sure, all kinds of people can.

http://bit.ly/D7RaW

Sounds just like this question, are you two working on the same problem?

viewtopic.php?t=129484

Searching for that message here will reveal all.

I fully understand what you'd like and what "99" means. All I'm saying is, if you check to see what dsjob returns for several jobs in your projects, including Compiled ones, what do you get? Gives you something to do, anyway, rather than sit around and wait for someone who may know the que...

I would think you'd be plenty safe using dsjob and checking for 99 as "compiled". What happens when you test that theory?

It's an environment variable, you set any of them in the job's environment and they apply to the entire job.

Yes, correct, as noted the data. It could care less about the case of the column names, but you have the option to make it care about the case of the key column join data itself.

I would assume they mean the case of the key column data, not of the column names.

PX has quite a number of date related functions so there's no need for I/Oconv to do any date handling. This is one of the more "esoteric" uses of the function, however. Sorry, can't really help with the PX replacement part but perhaps can with the Server part. You're correct about the MX0...

If anyone has anything to contribute, they will. Patience. If you don't want to wait, contact your official support provider, something I think you'll need to do regardless now that you've manually deleted part of the project.

Can you post a link to this "other post" you found?

Not really. Broken pipes can be tricky to track down, things like network issues (as noted), permissions problems where the named pipe is being created, disk space issues there, etc etc can cause them. Perhaps googling for broken pipe trouble-shooting help could turn something up?

Just so you're not feeling so alone and spending all your time talking to yourself, thought I'd stop by. I've only been running PX on a single server so far and don't even have a second box to play with, so can't really add anything relevant to the discussion. :( Well, other than to ask: what exactl...