DSXchange

Seems to me you'd have to handle that via the ODBC drivers themselves somehow, a setting perhaps. Not really any way to have DataStage 'time out' inside a job that I've ever seen.

Did you get this one wrong in the interview? Seriously, these 'fishing' type questions of yours don't really have a place here. Now, if you have an actual problem with your repository and let us know what you've tried to do so far to fix it and ask some specific questions then we'd be glad to chime ...

Parallel jobs don't support hashed files.

Just wanted to check to see if your case was the 'crossing midnight' case. I'd suggest you take this to your support provider, see what they have to say... could be a bug in your version. Or it could just be you are using it in the wrong place. Based of the reference to DSJ.ME, I'm guessing you are ...

Give it a try... the OCI Bulk stage works fine with 10g from my experience.

Ok... you need to go through some documentation, it would seem. Open up the Designer Guide pdf manual and read the chapter on Job Sequences. Not only will you find sections on Triggers and Expressions but each stage is discussed individually and usually has a pictorial example of how it would be use...

Does this post apply?

You have control over what happens whenever a stage has problems. What are the trigger values out of the Notification stage? Are you allowing the Sequence to automatically handle failures? Are you using an Exception Handler?

First suggestion would be to read as much of the supplied documentation as you can stand - there is both an Administration Guide and a Users Guide. This isn't something you can just pick up and start whipping stuff out with, you need to read. Before you can register anything, the RTI Server must be ...

You mean other than the approaches you've already been given in the other posts in this thread?

As far as I know, the XML stages function the same in Server and PX. However, most of the techniques discussed in the guide leverage hashed files for chunk storage, hence the mention of Server jobs in it. Not all do, it's well worth going through regardless...

jvmerc wrote:Did they also refer to the most recent release of DS as Hawk?

Yes they did.

Many factors go into figuring that out... or you can just use the numbers Chuck or Bill or whatever in the heck his name is pulled out of his whazoo.

Yes.

Remove the appropriate .rc file. What O/S? Typically it is /sbin/rc2.d/S999ds.rc which links back to the 'sample' under the DSEngine directory. Sure you really want to do that?