DSXchange

You need to get the job to run through before you can attempt to tune it; but with 4000 and 5212 records you should be finished in less than a second - unless your ODBC connection is slowing things down. What is your speed reading ODBC into a peek stage or a dataset? That is going to be your speed l...

Why not declare your output to have no delimiters, then in a transform check if the line begins with "BEGIN HEADER" or "END HEADER" and perform the appropriate string function. Or keep it as 2 column, but in a transform change the text BEGIN HEADER CharacterSet "CP1252" to BEGIN HEADER "CharacterSet...

The sequential stage delimiter definitions are for the whole file. If you need to do this you are best served by creating the file without any delimiters at all and using a transform stage to put them in manually for those rows where you need them.

In the output stage change your CHAR(7) to CHAR(8) and run the job. Is the data still truncated or does it work (or do you get another error message)?

This is certainly an odd problem. If you add that one character to the PX job definitions does it work? Also, do you have NLS enabled (I'm just "shooting in the dark" here, looking for a possible cause)?

Can you confirm that you are using Server or PX? You posted in PX but mentioned BASIC code and the two tend to be incompatible. The answer to your question depends upon which job type you are using.

A Char(7) field cannot have the value "profil". It might have the 7th character set to space or char(000) and not display that - could you check what that value actually is? Also, does the error go away if you write this to a sequential file? Are there any warning messages in the log files when you ...

Your scripts assume a cwd; but when called from DataStage this will always be the project directory and this might be causing problems.

Could you tell us what the column definitions are and what length the truncations are occuring at (i.e. VarChar(4) but only 2 characters loaded). Also, since CHAR fields are fixed length, what kind of truncation is occurring there and what are the pad characters?

Your PX installation might not be using /tmp for temporary files, check your configuration file for the actual scratch space. Monitor this during runitme to make sure it doesn't actually fill up and then empty itself after the abort.

No labor day weekend here (but the UK has so many bank holidays that I won't complain). Have fun. I still can't figure out why the deadlock daemon is turned off by default; just by adding that one little change you could get rid of (almost) every DS lock problem/question by answering "Just wait 15 m...

Have you compared the defaults and paths between both projects in the ADMINistrator? Perhaps they don't match. What is the exact compiler error message that you are getting?

There is a known issue with Designer sessions aborting that is fixed by installing a patch from IBM/Ascential; the ecase number is 72758. The RT_CONFIG file issue is something else completely. Each Job (be it Server/PX or a Sequence) will have one RT_CONFIG<nnn> file. You should compare the number o...

Do you know which the suggestions worked for you and could you post that so that this thread can help future DSXchange users?
Thanks!

Narasa, did my previous suggestion not work?