DSXchange

In other words, as noted before - pawn it off on your DBAs.

Why would mput need to be in anyone's path?

It's an ftp command and needs to be executed inside your ftp session, not outside of it as you have it now. And that requires a little 'here document' action.

You double-click on it and it should tell you why it aborted.

Also suggest you Reset the job and see if a 'From previous run...' entry shows up in the log.

NO NEED TO SHOUT.

You'll need to set the exit status of the script appropriately based on what happens inside your sqlplus session. And that will also depend on how your proc reports out problems. We do this by echoing all activity during the session into a tmp file and then grep'ing the file for Oracle errors. If an...

The jobs stay in the ready stage even after the scheduled time. It remains as such for a long time. It is not giving any errors. Then it sounds like you don't have any kind of a DataStage issue but more of a Tivoli problem - and it sounds like you simply don't have it setup properly if the jobs nev...

kjaouhari wrote:My question is what is the best choice for replce these PX jobs ?

A DBA? Sounds like a simple exp and imp could be a better choice if there's no transformations going on. Or as Ray notes, sqlldr.

Interesting... I guess I should just go back and delete my posts.

You are meant to Test the routine directly in the Manager to 'run' it, you don't really need a control job.

You could always write a job - source from the hashed file and write to a flat file.

Hmmm... I just got a replacement PC running XP SP2 (my old one went up in smoke - literally), just installed the 7.5.2 client and don't have a problem with Sequence jobs. And the patch doesn't mention that 7.5.2 needs it, but then it was probably put together before it existed. Just saying I've seen...

Restate the question... I have no idea what you are fishing for.

How exactly is your scheduler launching DataStage jobs? Via a script? I'd suggest you ensure that, regardless of how you are doing it, you capture any errors or output from the attempt. You'd have to let us know what error(s) were being generated with a job is not 'triggering' - otherwise we'd just ...

Keep your answers relevant to the 4.x version of the product, kids. First anachronism - it no got Sequence jobs.