FIX: Transaction Integrator truncates incoming strings that end in embedded null characters or spaces

Symptoms

You run a Transaction Integrator application that retrieves string data from the mainframe. When an incoming string is read, the TI runtime may truncate the string if there are embedded null characters or spaces at the end of the string.

Cause

This issue occurs depending on the settings of the Strings are Null Terminated or Space Padded option. These settings are set in the TI Designer tool for the string parameter. The settings affect how the string is read.

Resolution

The fix that resolves this problem is included in the following cumulative updates for Host Integration Server:

Cumulative Update 2 for Host Integration Server 2016

Cumulative Update 4 for Host Integration Server 2013

Note After you apply this update, you can set the new Conversion Behavior (Convert Received Strings As Is) to ignore the settings and receive all bytes of an incoming string.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×