Originally posted by: SystemAdmin

I need help with the type tree definition for reading data coming from a mainframe COBOL program. I have a system that picks up MQ messages, and it has worked fine when the source COBOL program gets its data from DB2. They just started passing data that they're reading from files, and I don't think I have the definition right.

When the source is DB2, I use UltraEdit to view the string in Hex mode.

‘H25010<spc><spc><spc>’ = '48 32 35 30 31 30 20 20 20'

With the low-values from the flat file:

‘H25010<null><null><null>’ = '48 32 35 30 31 30 00 00 00'

This change in the input doesn't generate a failure on validation, but when I use that field later to build in INSERT statement for the database, the hex value '00' seems to be acting as an end of file or end of string indicator. The string is truncated at this first low-value.

Is this something I can change at the type tree to see the low-value as a space or will I need to use a SUBSTITUTE statement in the map rule? Is there another method for working with this?

Thanks.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: janhess

This is a result of bad Cobol programming. The data should contain hex 20 if it's a pic X field. I would suggest that the Cobol is corrected.
However if this can't be done then you could use substitute.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Thanks janhess.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender