Windows Server

Ananth Krishna · Guest

Hello;

I am importing from a copy book into my HIS 2004 project .NET client library
in VS.NET 2003 and i have the following datatypes. PIC 9(7), PIC 9(03),
PIC 9(02) etc. I get the warning that

"NAM-HGT PIC 9(03). is a non-signed data type which
is not supported by Transaction Integration. It has been imported as a
signed data type.
"

I cannot do signed data type. It doesn't work for me. Can you please
clarify that non-signed data types are not supported ? What is the
workaround for this?...I really cant change my COBOL programs to support
this...

Help!

Thanks~
Ananth Krishna
Interlink

Ananth Krishna · Guest

More information:

1: PIC 9(n) :- These are numeric datatypes. All my cobol programs have
unsigned data type inputs and outputs
2: I am upgrading from HIS 2000 to HIS 2004. Looks like i was able to do
this in HIS 2000 with the wizard. Why can't i do unsigned with HIS 2004?

Am I missing anything?

Thanks~
Ananth Krishna
Interlink

"Ananth Krishna" <ananth_krishna@hotmail.com> wrote in message
news:e3DxGHrxEHA.2788@TK2MSFTNGP15.phx.gbl...

Rob Beardsworth [MSFT] · Guest

HI Ananth,
I think that you will find that it is only the Windows side which is
signed, not the host side. The reason that this change was made is that for
CLS Compliancy unsigned data types are not used. VB .NET does not have
unsigned data types, so we do not create an interface for the client which
includes unsigned data types.

You should be able to just ignore the warning. If you run into any
problems at runtime, don't hesitate to tell us about them.

Rob Beardsworth
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
--------------------

More information:

1: PIC 9(n) :- These are numeric datatypes. All my cobol programs have
unsigned data type inputs and outputs
2: I am upgrading from HIS 2000 to HIS 2004. Looks like i was able to do
this in HIS 2000 with the wizard. Why can't i do unsigned with HIS 2004?

Am I missing anything?

Thanks~
Ananth Krishna
Interlink

"Ananth Krishna" <ananth_krishna@hotmail.com> wrote in message
news:e3DxGHrxEHA.2788@TK2MSFTNGP15.phx.gbl...

Ananth Krishna · Guest

Hey Rob;

Thanks for a quick reply. However i do have problems with data going in
(runtime) since i see it in a dump that i have put in my COBOL program. I
see them coming in as unsigned still. a number that is PIC 9(7) for example
5649984 is coming in as 564998D.

I have the same setup running with HIS 2000 and those come fine in my dump
with those signed characters...for the same field.

Cheers~
Ananth

"Rob Beardsworth [MSFT]" <rob_beardsworth@online.microsoft.com> wrote in
message news:qbRELJ0xEHA.2916@cpmsftngxa10.phx.gbl...

Ananth Krishna · Guest

Oops~..should say without those signed characters when i try them through
HIS 2000 and it works fine. Basically i have HIS 2000 and HIS 2004 running
in parallel...everything is same except the signed and the unsigned
datatypes....signed datatypes being TI VS.NET projects and HIS 2004

"Ananth Krishna" <ananth_krishna@hotmail.com> wrote in message
news:e%23koTi0xEHA.3908@TK2MSFTNGP12.phx.gbl...

Ananth Krishna · Guest

Rob;

I did trick it for the moment. I modified my copy book in notepad changing
all the PIC 9(n) fields to the alphanumeric data type Pic X(n) fields. I
then imported it into TI .NET Client Library project and they come across as
PIC X(n) fields. It just means i have to check my data to make sure its
numeric before i send them through this client to the mainframe.

My client does not used signed data types in their COBOL programs. From
what i am seeing in the mainframe dumps taken after calling a CICS program
my HIS 2004, the TI WIObject is passing them as signed datatypes. I
understand your reasoning about .NET data types. However since i am seeing
problems at run-time; what is the resolution/cause for this? Am i missing
anything?

My model is TRMLink, I have the MSCMTICS.cbl and the IBM supplied listeners
EZACIC02. All the stuff works nicely in the HIS 2000 setup.

Again; thanks for any help.

Cheers~
Ananth Krishna
Interlink

"Rob Beardsworth [MSFT]" <rob_beardsworth@online.microsoft.com> wrote in
message news:qbRELJ0xEHA.2916@cpmsftngxa10.phx.gbl...

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1