DSXchange

Welll... you could add an "exit 0" to the end of the script but how will you know when it has a real problem? Why would you want a bad/incomplete load to be considered good?

That makes no sense and seems like something to me that you should take to your official support provider. Perhaps there is a patch or fixpack available that addresses that.

In your $BULKLOADPATH there should be a .log file and possibly a .bad file as well. If you don't see them there, check locally, i.e. where you were when you ran the command.

So what exactly does your script return, what value? Is there anything intersting in your bulkload's .log file?

Hashed files columns are referenced positionally, not by name. Ever wondered why the 'column names' you use in the stage don't really matter? That's why and I assume part of the answer.

When you say it is 'not populating' do you mean sometimes it is blank? Or that the text is there but the status variable is missing/unresolved?

Nope, not really something in the cards as I have a full-time gig consulting for the Department of Defense.

Or just build a mapping... err, job... to do that.

So... throw us a bone here. Are you using the actual Email Notification stage in your Sequence jobs or something else? How are you populating the subject?

Search here for a significant piece of your message, it has been discussed quite a number of time.

Ah... true.

What happened to the "which should be more than or equal to 5" part?

As noted, stop trusting the 'view data' utility for multibyte characters - what does the data look like in your target using a tool other than DataStage's viewer?

... and here we are.

Server or Parallel job? You marked it one way and posted in the other forum, hence the question.