Originally posted by: jvanboga
The problem is that when reading the file/record/segment and tilde is defined as a segment/record terminator it will assume that any tilde is the end of a segment. So this one segment would be treated as two segments and cause a validation issue when a map tried to read the input.....
NM1*IL*1*VAN~JOHNSON*MARK****34*123456789~
Also, even if you could use 'substitute()' how do you know what the substitute value should be? We get this type of issue a lot. In this case we would reject the file.
If the symbol is defined as a delimiter it may not be as big of a deal but still needs to be addressed.
Here's a possibility. Is the terminator '~' or '~<NL>'? If the terminator is the later and the extra ~ is missing the '<NL>' you could substitute the terminator with another unused character.
#IBM-Websphere-Transformation-Extender#DataExchange#IBMSterlingTransformationExtender