DSXchange

First bit of light shedding should come from a forum search. For example, I got 40 hits when I did an exact search for "Fault type is 11", something out there should help. FYI - The "Fault types" are the same as UNIX signals, so 11 is SIGSEGV or a Segmentation Violation: http://w...

Ah... while you could mark the second as a Reject link, you probably don't want the warning that will log. For "Link2" use "Link1.REJECTED" as the constraint to catch everything that didn't go down Link1.

As long as the same hashed file has already been created on the other server, since it is an account-based static hashed file you can simply copy the file named SDKSequences that you'll find inside the source project to the target project. If it's not in the target project yet, simple 'Test' the rou...

Trust me, my pretty. [rubs hands together slowly]

What 'otherwise' option would that be? Do you mean perhaps an 'else' in the constraint expression? An example or more detailed question would help here.

Timedate output is in the form of "hh:mm:ss dd mmm yyyy", so separate the time and the date using Field, convert the date with an IConv/OConv pair and then glue the two pieces back together.

Right, deleted is deleted. So, no project exports, file level backups, nothing? If that's the case, you could lose more than one job if something really went south.

Seeing as how it's not a parameter per se but rather an evironment variable, it doesn't really suprise me that it affects all jobs run by a Sequence job when it is set at that level.

Yup, the next 7th day of the month.

Wasn't sure what "load" meant here - read it and load the results into another source, like a database or did you mean write / create a file in this format? Regardless, I don't see why not. Not going to be quite as straightforward as a 'normal' file but should be perfectly do-able. What ki...

Hell, it takes me longer than that to come up with a new job's name.

Did you try searching for "unable to return an attached job"? Several existing discussions out there on the subject.

You seem to have misunderstood the "10 minutes" comment - that was how long it took Ernie to build the job.

For a guess of Oracle issues, check the Oracle client version installed on both machines. They may be different.

No, this is forensics work. Reset (not recompile) the aborted job and let us know if there is any new information logged 'From previous run...' otherwise we have no idea what is going wrong.