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 always converts PIC 9(1) to 0 regardless of the value that's being returned


View products that this article applies to.

Symptoms

When you run a Transaction Integrator transaction where a numeric value is defined as PIC9(1) at the mainframe, a value of 0 is invariably returned. This behavior occurs even when the actual value is greater than or less than 0.

This problem occurs when the conversion behavior acceptNullZoned option is set to True in the App.config file. If acceptNullZoned is set to False, the correct value is returned for the variable.

↑ Back to the top


Cause

A value of 0 should be returned only if all bytes are NULL for both Packed and Zoned Decimal values and when the appropriate “acceptNull<xxx>” conversion behavior is set to True in the application’s App.config file.

↑ Back to the top


Resolution

Cumulative update information

This update is included in cumulative update package 2 for Host Integration Server 2013. For more information about how to obtain the cumulative update package, see Cumulative Update 2 for Host Integration Server 2013.

↑ 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


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kb

↑ Back to the top

Article Info
Article ID : 2955434
Revision : 4
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 331