DSXchange

chulett wrote:Dang, another Wurlod Word I had to look up.

http://en.wikipedia.org/wiki/Prolixity

At the risk of seeming tendentious, I feel that the Wikipdia entry doesn't really pick up the negative connotation as well as the dictionary.com entry.

Not the home directory, the project directory.

In the project directory the file you need to check is called uvodbc.config.

There is one in each project directory as well as the one in the DSEngine directory; the latter is a "catch all" in case there isn't one in the project directory.

Nah. Mine is simpler. Eschew prolixity.

Which pull-down menu?

The pull-down menu in an ODBC stage only shows data sources from which you have imported at least one table definition. It is driven by the Repository table in which table definitions are stored.

"To eschew all reference to mission statements, stakeholders, strategic plans, corporate aims, goings forward and all other verbal paraphernalia of a verbose, litigious world, to avoid the humbug of irrelevant aspersions and render the reader a somewhat happier and contented soul with funny musings ...

And this is my fault how, exactly?

Folks, premium membership is a way to help pay for the bandwidth charges for this site. If we can't pay for the bandwidth, the site disappears. It's only a few cents per day.

Add more directories (on different drives) to the resource disk in your configuration file.

Convert the comma-delimited field into columns using a Column Import stage.

It's possible that DSHOME is not set, in which case cd $DSHOME will put you in your home directory, which is not where you want/need to be. After the cd command, issue a pwd command to determine to which directory you are currently attached. If you're going to do a lot of work at the server command ...

abc123 wrote:I tried to load the dataset using the Dataset Management utility. It was giving an "Unrecognized error". It would then load a blank file. I tried deleting it but it couldn't.

Did you specify the pathname of the ".ds" file to the Data Set Management utility?

If that's the case (I have not have a chance to check yet) you need to report the bug through your support provider. They will also demand a reproducible case, so have that ready so they can't stall you.

In he Sequential File stage have you set the column extended data type to Unicode?

Create another job with an Oracle Enterprise stage and an output link. Use View Data there.

Please post the entire error message.

Forget JobMonApp on this thread - it's irrelevant. Open a new thread for that or, better, Search for it.

Now check your uvodbc.config file for an entry for the DSN.