DSXchange

Most likely it is the environment and some missing oracle settings. Could you add a call to the BASIC code and compare the actual runtime values?

Yes, there is. But it depends upon where you wish to get this value. I can't recall the exact function name that you can use in a transform stage, but you will get it shown to you in the drop-down list of functions. You can also shell out to UNIX in many places and retrieve the value there.

No directly; but you could do a

...The rows within the source file have varying lengths and may contain any ASCII value... If the line terminator can be part of the data and is not quoted you really have no means of determining what a "line" consists of. In case like this you usually parse the data in the job according to some ot...

Develop - Your company has bought an expensive and powerful tool and now wishes to perform one of the built-in functions via the scripting funciton of the operating system. This is silly! The COMP-3 is a binary coded decimal format that is very easy to convert in most languages. Doing so in script i...

I know those two are documented in the Programmer's or Advanced Programmer's guide! The APT_RECORD_COUNT variable will, when set, make the actual record counts for all nodes and stages get written to the log file. I've found this quite useful for debugging. The OSH_PRINT_SCHEMAS does the same thing ...

I am sure that the truncation is coming from your job or table definitions and an implicit conversion and not from a bug. Just a thought - do you have NLS enabled (i.e. a double-byte or multi-byte system)?

Glad to hear that you are making progress! Remember that you don't need to explicity use IPC stages if you enable interprocess row buffering

There is an active thread with the same topic going on right now.

Make a copy of the job, delete everything after the Link Collector and replace it with a sequential file stage and see what happens.

What is the link collector output stage - that is more likely to be the cause of a hung condition.

Ray caught my misteak <sic>; I posted the wrong function

I infer from your post that you have ensured that the actual data is 6 character - what if you put a into your job?

sas - please try to output the value of char(In.Column[1,1]) into a peek stage.. what is the value?

If you do a "view data" on your ODBC stage does the data show as truncated already? If not, then I would suggest you check your dataset schema to see if it really is CHAR(6) and not something smaller.