Joel McIntyre [MSFT]
Guest
|
 Posted:
Fri Mar 18, 2005 1:25 am Post subject:
RE: TI Designer COBOL Import Type Mapping |
|
|
Dana,
Yes, this is indeed a product bug, and I have no trouble reproducing the
behavior. The TI Designer COBOL Importer is only recognizing the decimal
type based on the 'COMP-3' string (or COMP-1 and COMP2) rather than further
investigating the S9(n)V9(n) display type, as you point out. It should
honor the scale value even in DISPLAY types.
As a work-around, you can manually change the type within the Designer
itself after the Importer completes. If you have the option, you may also
consider adding COMP-3 to your COBOL, though that will depend on your
situation.
Please contact Microsoft Product Support Services (PSS) at
support.microsoft.com if you wish to work with them for a fix in HIS 2004.
I have entered a bug so this issue will be tracked for future HIS releases.
Best Wishes,
--
Joel McIntyre
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: Dana <a@b>
Subject: TI Designer COBOL Import Type Mapping
Date: Mon, 14 Mar 2005 21:31:27 -0800
Organization: .
Message-ID: <apsc311afe61i2viir2100209huqn4p73a@4ax.com>
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: ip68-4-148-188.oc.oc.cox.net 68.4.148.188
Lines: 1
Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp1
3.phx.gbl
Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.hiserver.general:4841
X-Tomcat-NG: microsoft.public.hiserver.general
Using the following COBOL data decs:
01 V-DISPLAY-IMPLICIT-REC.
02 PICS99V99DEFDISP PIC S9(2)V9(2).
02 PICS99V999DEFDISP PIC S9(2)V9(3).
02 PICS9-9V9-9DEFDISP PIC S9(9)V9(9).
01 V-COMP3-REC.
02 PICS99V99COMP PIC S9(2)V9(2) COMP-3.
02 PICS99V999COMP PIC S9(2)V9(3) COMP-3.
02 PICS9-9V9-9COMP PIC S9(9)V9(8) COMP-3.
HIS 2004 generated some surprising (to me) mappings
for example:
PICS99V99DEFDISP PIC S9(2)V9(2).
was mapped to SHORT/INTEGER whereas the documentation states this should be
CURRENCY. Seems like the correct choice would be DECIMAL given that we are
living in a .NET world these days (although this was a COM Client). What
happened to the scale?
With
PICS99V999DEFDISP PIC S9(2)V9(3).
the mapping was to a LONG and the documentation states it should be a
"4-byte Real". Assuming the documentation is wrong how is this conversion
handled at run-time? Specifically what happens to the scale?
When the above examples are changed to COMP-3 the Windows type is changed
to DECIMAL. Why the difference? How does this really work? |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in