DSXchange

If I may address the second of your problems first, a full save can take a substantial amount of time but it does get there (at least in my experience). For the first of your problems it looks like something you really need to take up with your official support provider (who may advise a fix pack or...

I just tried it here, and 007 does work when the delimiter is BEL. This is during Import > Table Definition > Sequential File ?

Then it looks like you DO have nulls. Please check again.

Ah. of course. BEL = "alert". Missed that nuance. So, back to the original question - when importing the metadata from the (target) sequential file, specify the field delimiter character as 007. It must have three digits when in decimal format.

Welcome aboard. Short answer: it's not easy. Column names are not stored in DS_JOBS, they are stored in DS_JOBOBJECTS in a multi-valued field. And even then the collection of column names may be in a different field number for different job object types. Stick with using Advanced Find since you're a...

Does the stored procedure work outside of DataStage?

It's interesting that your target files from the sed commands have \a as their delimiter, not \007.

Review the code and look for where PUT.Pin%%V0S277P5 is actually defined. My guess is that this is the GCI subroutine call in question. This is a call that transfers a row to an output link - work out which output link it is and, from there, possible causes for the exception.

dcsmdexport exports the entire project. dsexport supports options for exporting a single job.

Go for it.

Most of what you need is in the ETLstats package which you can download (for free) from Kim Duke's website.

How good are your developers?

The Join stage requires that its inputs be sorted on the Join keys. Other stage types have similar requirements. The reason is efficiency. The Join stage needs to process only one value at a time from the Left input (or Right if a right outer join) and compare that with only one value from the other...

What would be really cool would be if the Match Frequencies stage had the ability to maintain match frequencies, assuming that the incoming stream of tokens are all new values, so that the effect on frequencies is purely additive. For example, one might capture the additional names being added to th...

Within the Balanced Optimizer dialog you can specify the range of stages to push into the source/target database. Have you investigated this feature which, I believe, is new in version 9.1?

Or &H07