Component Builder Incorrectly Maps COBOL Data Types for Unsigned Display

ID: Q230601

The information in this article applies to:

SYMPTOMS

Method parameters defined using automation types of Integer, Long, Single, Double, Currency, or Decimal are incorrectly mapped to COBOL data type of type PIC 9(n) LEADING SEPARATE DISPLAY (or PIC 9(n)V9(n)LEADING SEPARATE DISPLAY) in Component Builder (CB) when you build new COM Transaction Integrator (COMTI) components.

The first indication this problem exists may be a run time error. The first indication of the possibility of this problem is a run time error. The following error message is posted to the Windows NT application event log:

Event ID: 102
Source: COMTI
Type: Error
Category: General

(102) COM Transaction Integrator reported the following exception to the client:
Component: COMTI Component Name
Method: COMTI Method name
Exception description:
(1562) Parameter PARAMETER NAME in method METHODNAME contained an invalid zoned decimal value. Check the mainframe server program. If it is correct, verify that the correct COM Transaction Integrator-created component library is deployed.

EXPLANATION
An Automation exception representing an error condition was returned to a COM Transaction Integrator client. The description shown above contains more information about the exception that was reported.
Because this error message may accurately indicate a problem of the application code, a further step is necessary to demonstrate a COMTI problem exists instead. Export COBOL from the COMTI component library. You can see the variables in question defined with the "LEADING SEPARATE DISPLAY" attribute.


CAUSE

COMTI is not handling the conversion properly for unsigned DISPLAY.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft SNA Server version 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

File name Date Time
Ibmcobol.xml 07/01/99 08:00

NOTE: Because of file dependencies, the most recent fix that contains the above files may also contain additional files.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft SNA Server version 4.0SP2.

Additional query words: 


Keywords          : 
Version           : WINDOWS:4.0 SP2
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: July 21, 1999