Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


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.

↑ Back to the top


Status

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

↑ Back to the top


References

Learn about the terminology Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kbQFE, kbfix, kbBug, kbExpertiseInter, kbsurveynew

↑ Back to the top

Article Info
Article ID : 3141350
Revision : 9
Created on : 10/27/2017
Published on : 11/24/2017
Exists online : False
Views : 296