DSXchange

See this post. You'll need to remove them before you write them out to the sequential file.

Ok... did not anyone check the post I linked to? Seems to be a bug that Ascential has a patch available for.

gateleys wrote:In another post, Arnd suggested that I do it using creating my own loop using the job control code generated via an empty canvas. Will have to try that.

'Fraid that will be your only option in 7.0.

You really should start a new thread on this. You'll need to find a way to stash the return value somewhere it can be picked up. Easiest way may be to use the User Status area of the job, something easily leveraged in a Sequence job parameter. Search the forum, it's been discussed a bajillion times.

To be fair, no-one asked what "doesn't work" meant.

This sounds really familiar. You may need a patch.

Environment. What 'same error message' are you getting? What exactly do you mean by 'upload to Version Control'?

Since you are talking TNS, let's assume you are asking an Oracle question. How did you create a 'proper dsn'? How are you 'importing the proc without problem using that dsn'? If the answer to both questions is via ODBC, you have taken the wrong path. The SP stage when set to Oracle uses the same set...

Typically a problem with Service Pack 2 on Windows XP. You need to log on to the Ascential EService website and download the SP2 Patch from there if that's what you have installed on your PC.

Triggers page: sucesslink=return (=Y)(i can run the job in the sequncer) abortlink=reutn(=N) Meena - please cut-and-paste (do not hand type) your Trigger code here for both links. The syntax shown above, besides containing an obvious typo, isn't valid syntax. Seems like you should be checking the S...

Scroll the Sequential File stage's Columns tab over to the right and change the 'Contains Terminators' column from 'No' to 'Yes' for the field that has the CR in it.

Correct!

Zabeerulla - what 7.x version of DataStage do you have?

As long as you have the 7.5.x version. Before that it gets more... complicated.

There's nothing wrong with the User Status approach - as long as you understand the pros and cons. I've also created a flat file with values like that inside a job and then built a routine that basically echoes it back to standard out and captures that. Run the routine directly in the User Variables...