DSXchange

That could very well be. It may have gotten "pulled" or delayed to a later release due to last minute issues.

From what I heard, something like that happened to the rumored Stored Procedure Stage.

Let us know what you find out!

I believe you'll find that this is for PX jobs only.

More information. I can't execute any scripts in any jobs on this particular server right now. Even if I create a job that does nothing other than call a script - any script - it coredumps. Too much going on to allow me to restart DataStage right at the moment and I can certainly move on to other th...

Suggest you pick up CompileAllPlus from the old site:

http://www.datastagexchange.com/compileall.php

Still free from there, as far as I know.

What kind of error messages were you getting? Database errors from your source/target or internal DataStage type errors? Sounds like your log file for the job is corrupted - any chance you ran out of space where DataStage is installed? Hint - this is very high on the list of official Bad Things.

Zed, That could be one cause. And yes, it is generally a good idea to manage the Phantom directory so that the number of entries in it doesn't get out of hand. Instead of manually clearing it (which you certainly can do) you might also want to consider an automated process. If you search the site, I...

Yep! As close as possible to actually running under a job and it works fine. It actually runs just fine in many other jobs, across multiple servers and projects... there seems to be something magically wrong with this instance of it.

Maybe I'll try the old delete and re-add the Stage trick...

Any help out there for tracking one of these down? What I've got is a Command stage in a Sequence that (at the end of the process) runs a Korn shell script. It and others like it have been running fine for months in a number of different jobs. Today I added it to a new job and I get the following er...

A good place to start is with the online help available from the Director. Bring up the Index entry for "Multiple Job Instances" and go from there!

Is something misconfigured, is this a bug, or am I misunderstanding what "multiple instances" should do ?? You can't just simply start the same jobs multiple times. You need to start the job and specify a different Invocation ID for each run - this is what allows them to run simultaneously. For exa...

One question would be - are you A) upgrading an existing 5.x server to 7.x or are you B) setting up a new 7.x server and need to get all of your jobs over to it? First thing to do, regardless, is get a current export of all your projects for safe keeping or to fall back to if Something Goes Wrong. I...

Try clearing the status of the original job name, not the entry with the Invocation ID associated with it. They are, after all, in essence the same job. Either that or simply recompile or reset the original job and that will clear all Invocations, from what I remember.

Also note that just because you can "View" the data doesn't mean the syntax is absolutely correct and the job will actually run! One thing I've found, for instance, is that prototyping SQL in another tool and then pasting it into DataStage can sometimes bite you in the rear. That lowly little traili...

Are you sure about that, Ken? The server part, that is? While you certainly can install two copies of the Client now (and switch between them) as long as one of them is Version 7.x, I'm not all that sure about the Server side. Perhaps if the older one is pre-code split and still using uvhome and uvr...

A little bit to add to what Ken wrote. Something to realize is what happens when a Reference Lookup fails - i.e. does not return a row. When that happens, all fields in the link are null - all of them, including the keys that you specified and populated from the input stream. So even with a compound...