DSXchange

If your job is cratering early in the process then perhaps it hasn't gotten that far yet. From what I recall, the score is dumped just after the config file contents are logged and say "main_program: This step has".

And you're certain this job is compilable in the original project? Perhaps you are missing user-defined environment variables, they are not included in a Project export.

My assumption was that "sequence of jobs" meant a "Job Sequencer" or "Sequence job". If you meant something else, please let us know.

Your documentation should verify, but the current stages officially support up through 10g and pretty sure people here have reported using them with 11g.

Mine was with UNIX server, so cron scheduled via Director.

Has anyone had any success with using the XML Input stage with the Column Content option set to URL/File path and actually sending it a URL? I've always used it as a "file path" to a source local to the DataStage server and now I'm tasked with sourcing from files that have been "poste...

As far as I know, that answer would be... no.

No, by 'directly' I meant directly in the Surrogate Key Generator stage. Now granted, I've never done this myself as of yet, so just going by what I've read posted here but my understanding is that the stage can directly access the sequence and thus the fact that others may be using it at the same t...

Using the sequence directly would mean all that is already handled by the database.

sumanth.punyamurthula@etr wrote:But we use Datastage Enterprise Edition also called Parallel Extender (PX).

You marked your Job Type as Server in your post, hence my answer.

I didn't ask you to show me what it does look like but rather what it should look like, as in with the values properly substituted. Sounds like you want to select that date as a literal, yes?

Yes, for Server jobs. The debugging menu is available from the Designer.

Suddenly we're a warez site? WTF.

On the off chance you are a legitimate user and just confused as to where to go for that information, check with the company you work for, the one that legitimately provided you with their licensed software - they'll have the appropriate credentials.

"Unusable" indexes are a common result of a failed bulk load (typically dups in a unique index) and need to be resolved before running another.

I've seen that myself years ago but Ascential support could never pin down a cause and it "went away" on its own. Perhaps by now they might have a clue.