DSXchange

It is not possible by any other means. A plsql function must be invoked from within an SQL statement. Therefore any stage that needs to use it must run some SQL. The stages that connect to Oracle are the only ones that can run Oracle SQL. (One exception: you could set up a command that runs sqlplus ...

DSUtilityRunJob has returned 1. Look in its job log for warnings.

I doubt that a version 7.5 dsexport would work properly with a version 8.1 DataStage.

Please expand on "for some reasons". Post the error message. If it's only permissions, find a location - on a shared drive perhaps - where you have write permission and export to there.

manikandan.kulanghat wrote:As part of our new requirement...

<rant>Resist stupid requirements!</rant>

It's called a brain.

It's a tool that can be, and usually is, manufactured using unskilled labour initially but which needs to be tuned by the best possible practitioners.

"If you can read this, thank a teacher!"

Maybe the database wasn't ready, or another process had a lock, or some other condition that had been cleared by the time you re-ran the job. There's probably some diagnostic information in the database's logs.

It depends on a number of factors. As a starting value use then experiment.

When you are importing the table definition you give the column widths on the Format tab. These are kept (and displayed) in the Display Width column of a Columns grid in a saved table definition. All you need to do on the Define tab is provide column (field) names.

Would you please share the resolution? I have been thinking about your question today, but was not ready to post an answer when you marked this thread as resolved.

It's in the source code. You do not have the source code. You cannot obtain the source code.

VLIST is also for helping you to debug your own routines, where you DO have the source code.

It's variable, but usually faster than that. An email to editor@dsxchange.com may help.

Which part of "you don't get the source code, which is IBM's intellectual property" is unclear?

It should be quite possible to use DSUtilityRunJob from a routine activity, and to construct its parameters string either in that routine or in a User Variables activity.

It won't. You need checkpoints for that. Or you can create the same logic in your sequence. Before every activity check whether (a) the sequence failed to finish successfully and (b) whether that activity finished successfully and, based on those results, make the decision whether to invoke the acti...

If you're not using checkpoints then the job (sequence) status will never be "restartable". Therefore if it aborts, it will need to be reset. But a top-level sequence should be written so that it never aborts.