DSXchange

All the best, Wolfgang!

In other words, the same scheduler that DataStage would leverage. You could script the whole process and schedule it through cron, or if you're more comfortable with DataStage, use a Sequence job to run the file transfer then check and do the notification if there are problems.

Does the job (which includes the 'after job' logic) show that it completed when it triggers the downstream job? Or are you literally saying the job still shows a 'Running' status when the second job gets kicked off? Perhaps the sqlplus session itself is returning control to DataStage right after it ...

YES - you need to reference an active stage, i.e. the transformer each time, and then the link either from the source or to the target.

The difference should be pretty apparent from thier names - it is the order the actions are taken. In either case, the first action must fail for the second to fire, so you typically choose which to use based on which of the operations you'll have the majority of. Unique keys can be critical to how ...

And just to be clear, in both cases the 'stage name' you pass is the transformer's name?

Welcome! Did you try searching for "DSR.ADMIN: Error creating a schema"? I got two other hits, perhaps one of them might help you?

That function is applicable to both types of jobs. Are you giving it an active stage name, i.e. a transformer stage's link to check on in the Server job?

This is similar to connecting to any database with a command line sql tool (like sqlplus and Oracle) - it gets you a shell where you can issue queries against the repository / database. From your operating system, execute the "dssh" executable in the $DSHOME/bin directory. I can't check th...

Wait, what the heck? There was another reply here I was replying to but when I actually posted my response, it was gone.

And now it's back but after mine. Odd.

Hmmm... obviously, something is different or there wouldn't be a change in behaviour of a job between environments. Sounds like it's not an obvious difference, however. :? Start with one job, verify that your changes will indeed allow it to work in both environments without change, then go all cookb...

You'll need some form of job control for that. Simplest would be to build the Sequence jobs you'd need, even if that is 300. Or if you have a generic dsjob wrapper script, perhaps one Sequence job that takes two job names as parameters and uses the Execute Command stage to run them, one after the ot...

You run jobs from the command line using 'dsjob'. Search the forums here for the syntax or read the Command Line Interface chapter of either Designer Guide pdf.

So, errors writing to a hashed file. Posting the complete, unedited errors from the log may help. Is your install NLS enabled?

You can't trim a CHAR.