HIS 2006 DLC on x64
Lomas@discussions.microsoft.com Francisco Lomas
I have an app that uses .NET assemblies and COMTI (LU 6.2) over SNA with HIS
2006, but I want to use an x64 Server, when I was installing HIS on the x64
server it tolds me that DLC is not supported!!
I read on a previous post that HIS 2006 will support all in x64, not IA64,
there is a driver for DLC on x64??
Charles Ezzell (MSFT)
probably be never supported with Host Integration Server).
We do support the "IPDLC" link service on x64 systems.
--
HTH,
Charles Ezzell
Microsoft Host Integration
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. Any and all views expressed are
those of the writer and not Microsoft. There is no such thing as a free
lunch. Peach is not a color. Violets are not blue.
"Francisco Lomas" <Francisco Lo...@discussions.microsoft.com> wrote in
message news:D0CCE338-42D1-4B94...@microsoft.com...
Francisco Lomas
IP-DLC link??
Sorry the question but I'm a begginer with Host Systems...
The Host is an OS/390 with CICS...
Francisco Lomas
Well based on that how can I use my .NET COMTI's with an IP-DLC link??
Sorry about the question but I'm a begginer with Host Systems, my Host is an
IBM 390, OS/390 with CICS...
Francisco Lomas
Well based on that how can I use my .NET COMTI's with an IP-DLC link??
Sorry about the question but I'm a begginer with Host Systems, my Host is an
IBM 390, OS/390 with CICS...
Charles Ezzell (MSFT)
COMTI or any other application won't care what the link service is.
--
HTH,
Charles Ezzell
Microsoft Host Integration
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. Any and all views expressed are
those of the writer and not Microsoft. There is no such thing as a free
lunch. Peach is not a color. Violets are not blue.
"Francisco Lomas" <Francis...@discussions.microsoft.com> wrote in
message news:5F20E6B8-8CCE-4EDB...@microsoft.com...
Neil Pike
As well as Charles's answer, check with your CICS guys whether CICS on your
mainframe listens on tcp-ip or not. If it does then you can use COMTI (WIP/HIP)
directly over tcp-ip to the host and you then won't need an actual HIS Server at
all.
> Thanks for the answer, well based on that how can I use the COMTI with an
> IP-DLC link??
> Sorry the question but I'm a begginer with Host Systems...
> The Host is an OS/390 with CICS...
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
Charles Ezzell (MSFT)
Yup - if they have IP on the host, you don't even need a link service. Just
go IP.
Otherwise, you are going to have to use a 32bit install on x86.
--
HTH,
Charles Ezzell
Microsoft Host Integration
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. Any and all views expressed are
those of the writer and not Microsoft. There is no such thing as a free
lunch. Peach is not a color. Violets are not blue.
"Neil Pike" <neil...@compuserve.com> wrote in message
news:VA.000064e...@compuserve.com...
Francisco Lomas
Well I would like to stay in x86 but I use a Biztalk 2k6 with the TI, and
you know to use the adapters, or the TI directly your HIS and Biztalk must be
in the same server and we need to move out, well maybe do you have or know
here a guide can be found to use the TI with only an IP?
Chris Mason
As I understand what is being suggested here - knowing next to nothing
about the "insides" of HIS - on a "64 bit system", data link controls
(DLCs), other than what HIS calls "IP-DLC", otherwise known as
Enterprise Extender or HPR over IP, are not supported. Thus, if
Francisco wants to use a "64 bit system", he will be obliged to use
what I believe is called the "IP-DLC Link Service", in layman's terms,
the HIS implementation of an APPN End Node using Enterprise Extender
as its DLC. As Francisco is a beginner I think he needs that level of
precision.
Even getting used to working with an APPN End Node is going to be
something of an upheaval compared to working before with a Low Entry
Networking (LEN) End Node, isn't it? Perhaps I need to do some more
research into HIS to know just what the changes are when using the "IP-
DLC Link Service".
But all this is just a prelude. Francisco is going to need to acquaint
the folk who look after his networking partner, the IBM "mainframe",
with the proposed change from supporting a LEN End Node to an APPN End
Node and necessarily as an APPN End Node - that is, no "tricks" trying
to pretend it's really still a LEN End Node in a subarea networking
environment - and using Enterprise Extender as the logical link over
the IP network.
Thus the folk responsible for VTAM (and NCP?) are going to have to sit
up and take note of the change to Enterprise Extender - using language
the VTAM folk will understand - from whatever was the medium used upon
which the link between HIS and some component in the rest of the SNA
network leading to the VTAM node supporting the CICS application.
The change at the HIS end may appear to be a simple change of DLC.
However at the "mainframe" end, assuming that the conversion from
subarea to APPN hasn't already been performed, this conversion is
going to be a major - if not a massive - upheaval - simply to be able
to accommodate this apparently simple change of DLC.
I think this change to the SNA network to APPN needs to be emphasised
very strongly when otherwise the impression given is "just change your
DLC to IP-DLC".
"COMTI or any other application" may not "care what the link service
is" but VTAM most certainly does when it's Enterprise Extender!
Incidentally, if you are proposing that HIS use IP-DLC, isn't it going
to be an unusual SNA network - not impossible but unusual - which
would not also require that there was "IP on the host"?
Chris Mason
On May 25, 2:42 pm, "Charles Ezzell \(MSFT\)"
<charl...@online.microsoft.com> wrote:
> Neil trumped me with the simple response <G>
>
> Yup - if they have IP on the host, you don't even need a link service. Just
> go IP.
>
> Otherwise, you are going to have to use a 32bit install on x86.
>
> --
> HTH,
> Charles Ezzell
> Microsoft Host Integration
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of any included samples are subject to the terms specified athttp://www.microsoft.com/info/cpyright.htm. Any and all views expressed are
> those of the writer and not Microsoft. There is no such thing as a free
> lunch. Peach is not a color. Violets are not blue.
>
> "Neil Pike" <neilp...@compuserve.com> wrote in message
>
> news:VA.000064e...@compuserve.com...
>
>
>
> > Francisco,
>
> > As well as Charles's answer, check with your CICS guys whether CICS on
> > your
> > mainframe listens on tcp-ip or not. If it does then you can use COMTI
> > (WIP/HIP)
> > directly over tcp-ip to the host and you then won't need an actual HIS
> > Server at
> > all.
>
> >> Thanks for the answer, well based on that how can I use the COMTI with an
> >> IP-DLC link??
> >> Sorry the question but I'm a begginer with Host Systems...
> >> The Host is an OS/390 with CICS...
>
> > Neil Pike. Protech Computing Ltd
> > Microsoft SNA/HIS MVP
> >https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E...- Hide quoted text -
>
> - Show quoted text -
Neil Pike
Yes, it would. But some shops have, for reasons best known to themselves, a policy against allowing direct
tcp-ip access to IMS/CICS. In that situation, connecting to CICS/IMS on an IP-enabled host, can only be done via
IP-DLC (enterprise extender) as then CICS/IMS just see a normal SNA LU6.2 connection.
> Incidentally, if you are proposing that HIS use IP-DLC, isn't it going
> to be an unusual SNA network - not impossible but unusual - which
> would not also require that there was "IP on the host"?
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
Neil Pike
The below section in the HIS2006 doco explains it. You'll need to get your
mainframe/CICS folks to read it.
ms-help://MS.HIS.2006/HISMain/html/15b24c06-62c3-4109-94c7-d331d528395a.htm
The various methods of connecting to the mainframe with TI don't change how you
code your application.
> Well I would like to stay in x86 but I use a Biztalk 2k6 with the TI, and
> you know to use the adapters, or the TI directly your HIS and Biztalk must be
> in the same server and we need to move out, well maybe do you have or know
> here a guide can be found to use the TI with only an IP?
Charles Ezzell (MSFT)
Not that unusual at all either. Customers have hundreds (thousands) of
APPC/CPIC applications on the PC side that would require re-writing to
communicate straight IP to the mainframe. Just pop in an IP-DLC link
service, and the application doesn't even hiccup.
--
HTH,
Charles Ezzell
Microsoft Host Integration
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. Any and all views expressed are
those of the writer and not Microsoft. There is no such thing as a free
lunch. Peach is not a color. Violets are not blue.
"Neil Pike" <neil...@compuserve.com> wrote in message
news:VA.000064e...@compuserve.com...
Syed
Is there any offical Microsoft link/ Documentation available which supports
this claim:
DLC protocol not supported on x64 based systems. ??
Thanks...
Stephen Jackson [MSFT]
Known Issues and Limitations
Network Integration
The following is explained:
DLC Driver - Versions of Windows beyond Windows 2000 do not contain a driver
for the DLC network protocol. To ensure that users of Host Integration
Server 2009 can continue to use 802.2 Link services for SNA communication on
those versions of Windows, the DLC driver is provided in the Host
Integration Server 2009 installation. This version of the DLC driver is only
supported for use with Host Integration Server 2009 on x86 platforms. The
x64 version of DLC is not currently available. Please check
http://go.microsoft.com/fwlink/?LinkId=30978 for updates.
The DLC driver is now a selectable feature in the Host Integration Server
2009 server Setup. It appears under SNA Application Support, SNA Server in
the Windows Installer feature tree.
You can download the HIS 2009 Readme at
http://go.microsoft.com/fwlink/?LinkID=141188.
Also, you might want to check out the deprecated features for HIS 2010 at
https://connect.microsoft.com/HISERVER/content/content.aspx?ContentID=10997.
You will see here that DLC is not being included in HIS 2010 (was to be
called HIS 2009 R2, but the name was changed).
Network Integration
Microsoft Data Link Control (DLC) Link Service will be removed in HIS 2009
R2. The HIS team recommends that customers use Internet Protocol-Data Link
Control (IP-DLC) Link Service that is based on the industry-standard High
Performance Routing over Internet Protocol (HPR/IP).
Thanks...
--
Stephen Jackson
Microsoft® HIS Support
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.
"Syed" <Sy...@discussions.microsoft.com> wrote in message
news:B7F65E09-D6D6-44CA...@microsoft.com...