DSXchange

In this case you ARE converting from WVarChar to VarChar, and since you are doing a generic job using RCP you cannot get rid of the message. But you can deprecate the warning message to an informational one either at a job level or at a project level using the DataStage message handlers.

You are probably correct - but if the code is there to "chop off" at the word limit then it shouldn't be much work to add a character or modify the color (or perhaps a slightly different font). We'll see...

Craig - I asked for this enhancement to avoid having to do that. If a small graphic character or even if the first "un-readable-as-non-premium" character were to get a different color it would be enough.

Not only same name, but same data types, lengths & nullability.

Have you checked your source to see which character is present there, if any? If it were 0x0 then no padding would be performed .

Would it be possible to insert some small character or sign in premium posts showing where the text is cut off for non-premium members? This can be helpful to see which part of a message a user might not have been able to read.

No, not before we know what the padded values are. How are you converting from CHAR to VARCHAR in the transform stage? You can use the STR() function to see what a given character is, so in your case make a debug output from your transform, output STR(In.Col[8]) and see if it is indeed 0x0 or some o...

Can you use a server job for this? If so, there are server routines to perform COBOL type conversions which you can use.

If you cannot change the job then look at the source code to see if there are any CALLs or other steps between the job beginning and the DSLogInfo() call that might trigger an abort of the before-job routine.

I'd be surprised if the BeforeJob isn't called. Can you put "CALL DSLogWarn('Testing...','')" as the first line in the routine and see if that gets printed?

It is possible that DataStage has "tuned" the job at runtime. Set $APT_DISABLE_COMBINATION to "true" in this case to test that.

At my site I couldn't get the windows authentication to work and thus used a specific user id.

And if you remove the field from you query does it work? I googled "SQL Error (2027): Malformed packet" and got many hits.

Are you doing 2 explicit sorts with different keys/sort order? 1. Use sort stages for better control, not inline-sorts 2. Put in a modify stage or a transform and convert the character fields to VarChar (with no specified maximum length) 3. Set $OSH_DUMP_SCORE to "true" and examine the sco...

A 2-node configuration won't help you. How many Gb is your source file? Are you reading from a sequential file or a table or a DataSet? Does the data have lots of varchar() fields declared much larger than the contents (i.e. VarChar(32) when only 2-3 bytes are used)? Have you checked to see if your ...