Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

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.

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.

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.

Status

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

Need more help?

Expand your skills

EXPLORE TRAINING >

Get new features first

JOIN MICROSOFT 365 INSIDERS >

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×