What is the design and objective of your job? Are there any other surrounding warning messages? Provide more information.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
It means that there is at least one field in your job design defined as VarChar but without a Precision (maximum length) value.
While this is legal in some places (for example Data Set stages) it is not legal in others. Whichever operator governed by your particular combined operator controller is complaining about an unbounded string can not be determined without disabling operator combination. But you can just check for VarChar fields without a precision value and provide this value.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod wrote:It means that there is at least one field in your job design defined as VarChar but without a Precision (maximum length) value.
Didn't know that. Thanks! Ray.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
swades - the APT_DISABLE_COMBINATION switch is used in this case to help locate the stage that is causing your problem. But there is no need to do so, since your original error is telling you that it occurs in the ODBC stage.
Is this the source stage? What are your column definitions? At least one of these is incorrect for DataStage.
Additional error messages would help. Did you try setting it back to "generated sql"? See if that works, once you get that part working then you can analyze how different is your sql and the generated one. Analyze in regards to any syntax or data type conversion being done.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.