DSXchange

First off, I'd suggest rethinking the Function approach. What exactly is it doing and is there any reason you can't recreate the logic in the DataStage job itself? Also curious if you have a proper ODBC entry setup for this instance? That's an 'extra' step you'd need to take if you want to use an OD...

Luckily, I connect via broadband from all of my current locations. Still, I agree that it's time to go back to a more 'normal' home page with, as Roy notes, perhaps a link to a sub-page with the 10K and/or LV who-ha on it.

In other words, we've got an answer now but have no idea what the original question was. :D

Is that what we are discussing? I thought the topic was passing parameters between jobs.

And why do you "need" it?

Kumar - you mentioned one such way in your post - via the UserStatus area.

Me, I'd only use XML exports if the target for them was something other than DataStage. Otherwise, I don't see the point of all that extra work that the import has to do. When you import an XML export, the first thing it has to do under the covers is convert it back to dsx format and then import it....

That is ascending order.

For strings.

More information, please. One job? All jobs? If you are 'releasing' jobs and the job in question is one that has been released, this is the expected behaviour.

Any idea how it got in this state?

You seem to be in a similar boat that I am at the moment.

See if anything in this post helps.

Yes, they are - that's why it says 'Server' as the Job Type in their post.

It sounds like your Project does not have the Row Splitter installed. Any history behind all this, like the job was developed on another server and you've moved it to a new server and now this is happening?

Found it in this post.

No, that starts the DataStage Server itself.

I don't know it off the top of my head, but if you search the forum I'm sure it's bound to turn up.

Awhile? Pushing two years gone... really expect an answer?

I had a chance to nail down my DBA for a moment today and he concurs with your assertation, Arnd. Specifically, he suggests I set this: export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 I've made the tweak to our dsenv file but I'll be damned if I can find a quiet moment that I can bounce the Server. Go...