DSXchange

You have already been provided with a solution to this problem using a Sequential File stage. If you insist upon using a Complex Flat File stage please post the record schema that you are using. You will need more than one level of definition.

Can't you simply delete it using Designer?

Have you installed Fix Pack 1 for version 8 ?

Are you sure that there is code for this routine?

In versions prior to 8 the Code tab was empty (and, indeed, disabled) until a routine name had been entered but, as you report, you do have a routine name, so this is not the cause.

Guess not!

Welcome aboard.

A good start point would be to Search DSXchange. This will give you pointers and links to other sites where you can learn more.

I actually wrote more than that, as any premium member would be able to see. The diaresis (...) at the end of the truncated view indicates, just as it does in Director log view, that there is more to be seen.

It doesn't matter what forum you post in, nor how many times, for anyone to accede to your request would violate their licence agreement. You MUST request this information through your support provider or vendor.

Incitement to commit a crime is itself a crime.

I described fully in my earlier post how it works. Premium membership costs less than 30c per day, and allows one (among other things) to read all of what premium posters have to say. Premium membership is totally allocated to helping to defray the hosting and bandwidth costs incurred by DSXchange. ...

That would be violating licence conditions. Incitement to commit a crime is itself a crime. If you want documentation, ask your support provider or vendor.

Look Harder.

The words Post new topic are writ large at the top of each forum.

Etiquette Note
Do not direct questions to specific posters. This is a forum, with all that that implies.

Search will find answers to your question.

Use a Num() function to trap non-numeric data. Also look at the code in RT_BP5132/JOB.1850638995.DT.145306556.TRANS5 to see what's being processed in and around line number 346. This may assist you to identify the column that is throwing the exception.

$PROJDEF is one of three special tokens that you can use to set the default value of a job parameter that is an environment variable. It means that, unless some other value is supplied when the job run request is issued, that DataStage should obtain the value from the project; that is, from the envi...

Have you specified DOS-style as the record terminator string, rather than UNIX-style as the record terminator?

Get to the TCL prompt on the server in the DataStage Engine directory (also called the UV account). Execute the following commands and describe the outcome. SELECT @ID FMT '18L', PATH FMT '72T' FROM UV.ACCOUNT WHERE @ID = '<<Project>>'; SELECT SCHEMA_NAME, PATH FROM UV_SCHEMA WHERE SCHEMA_NAME = '<<...