DSXchange

That should be all about credentials mapping from what I recall.

Let's start by ending the thread-jacking and getting your post split out into your own topic... there.

A couple of different ways, off the top of my head. Either using a Sequence job, you can add a Notification Activity after the Job Activity, or a Routine Activity if you need to use whatever routine you wrote. Or from the job itself, run it from the 'After Job' tab. There's also a checkbox there to ...

You're the Watson of our World, Ernie.

IMHO you are well past the time you should be engaging your official support provider, if you haven't already...

Could you please elaborate the meaning of "8+3" format of file path? As suspected, a bit of arcane lore. :wink: https://en.wikipedia.org/wiki/8.3_filename The part you would be most interested in is the 4th section: How to convert a long filename to a short filename. This so you could see...

Kaushik,

Trying to fish your answers out of that single big quoted Andy block was painful enough that I reformatted your post to (hopefully) make them a little bit easier to read.

Pretty sure you'll need to involve support on that one... couldn't find another posting here that mentioned that error.

RiyaNY wrote:We are using DS 8.5 and migrating to 9.1 now.

Why stop there? Not really the right thread for this discussion but why upgrade from a really old version to one that's almost just as old?

Just to clarify, are you looking for the 'design time' parameter values, the values that the job would use if nothing was explicitly passed to it as an override at runtime? Or something else?

That depends entirely on what exactly 'load the fresh records' means.

Only if you're aware that they are still there under the fancy Windows 'long filenames' and how they work... tilde and all.

Is this file... local to your DataStage server?

First thought is that there's no need to quote everything you are replying to. Do so if it makes sense but in general all you need to do is use the Reply to topic link. Second thought is why would you be screwed if this happened in production? Of course, Bad Things happening there are more immediate...

Then you should be involving your official support provider as there's probably not a ton of Big Data / HDFS / YARN users here yet. I'd also be curious if you've done any of the things the errors suggested you 'look into'.