Is there a tutorial similar to Cedrbank / HIS2000 for SNA LU6.2 te

Is there a tutorial similar to Cedrbank / HIS2000 for SNA LU6.2 te

We have been using HIS2000 for 8 years - COMTI  for 2PC Transaction 
(APPC/LU6.2 CICS Link) across SQL Server 2000 database and on the mainframe 
via CICS to read and update DB2 and IMS databases.

We are migrating from ASP to ASP.Net 2.0, VB6 to VB2005, SQL Server 2000 to 
SQL Server 2005, and HIS2000 to HIS2006.

I have installed HIS2006 and set up SNA and the CICS_Link RE.

When I drag the COMTI component (tlb) into a COM+ package and try to test 
the connectivity to the mainframe it doesn't work because there is no 
tagen.dll in HIS2006.

Next I created a server export package from the 2000 environment so that I 
would have a dll with both tagen.dll and the tlb.  

Next on the WIN2003 box with HIS2006 installed I double clicked on the 
server package msi.  Still the test didn't work.  There is no tab on the COM+ 
component to specify the RE.  When I tried to add the RE using the TI tool TI 
couldn't find the RE I created.

Next I looked through the HIS2006 SDK to see if I could find a detailed, 
step by step tutorial to test this specific situation, similar to the 
CEDRBank tutorial that came with HIS2000.  

I found several tutorials but none that dealt specifically with testing 
connectivity to a real mainframe (CICS) via SNA LU 6.2 and CICS_Link.

Please let me know if there is such a tutorial available and, if so, where I 
can find it.

Also, we use the Oleview.exe on our Win2K boxes all the time.  Will this run 
on a Win2003 Box?  If not, is there an oleview tool that will work on Win2003?

Thanks for your help.

date: Thu, 27 Mar 2008 10:27:01 -0700 author: HISUser

Re: Is there a tutorial similar to Cedrbank / HIS2000 for SNA LU6.2 te

First, I am curious how you installed HIS 2006 because tagen.dll does exist 
in HIS 2006. Transaction Integrator (TI) is a server feature that has to be 
installed by selecting the Transaction Integrator component under the Server 
component when installing (or modifying via Add or Remove Programs) HIS 
2006.

As far as migrating typelibs from previous versions of COMTI, you might have 
a look at the following article:

886300	How to migrate type libraries from SNA Server 4.0 Service Pack 4 and 
Host Integration Server 2000 Service Pack 1 to Host Integration Server 2004
http://support.microsoft.com/default.aspx?scid=kb;EN-US;886300

This article also applies to HIS 2006.

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.


"HISUser"  wrote in message 
news:22727D50-8D52-41FF-943B-9CCE1D9C24B7@microsoft.com...
> We have been using HIS2000 for 8 years - COMTI  for 2PC Transaction
> (APPC/LU6.2 CICS Link) across SQL Server 2000 database and on the 
> mainframe
> via CICS to read and update DB2 and IMS databases.
>
> We are migrating from ASP to ASP.Net 2.0, VB6 to VB2005, SQL Server 2000 
> to
> SQL Server 2005, and HIS2000 to HIS2006.
>
> I have installed HIS2006 and set up SNA and the CICS_Link RE.
>
> When I drag the COMTI component (tlb) into a COM+ package and try to test
> the connectivity to the mainframe it doesn't work because there is no
> tagen.dll in HIS2006.
>
> Next I created a server export package from the 2000 environment so that I
> would have a dll with both tagen.dll and the tlb.
>
> Next on the WIN2003 box with HIS2006 installed I double clicked on the
> server package msi.  Still the test didn't work.  There is no tab on the 
> COM+
> component to specify the RE.  When I tried to add the RE using the TI tool 
> TI
> couldn't find the RE I created.
>
> Next I looked through the HIS2006 SDK to see if I could find a detailed,
> step by step tutorial to test this specific situation, similar to the
> CEDRBank tutorial that came with HIS2000.
>
> I found several tutorials but none that dealt specifically with testing
> connectivity to a real mainframe (CICS) via SNA LU 6.2 and CICS_Link.
>
> Please let me know if there is such a tutorial available and, if so, where 
> I
> can find it.
>
> Also, we use the Oleview.exe on our Win2K boxes all the time.  Will this 
> run
> on a Win2003 Box?  If not, is there an oleview tool that will work on 
> Win2003?
>
> Thanks for your help.
>
>
>

date: Fri, 28 Mar 2008 14:31:22 -0500 author: Stephen Jackson [MSFT]

RE: Is there a tutorial similar to Cedrbank / HIS2000 for SNA LU6.2 te

I found tagen.dll in the HIS2006 folder.  When I tried dragging the 
cedrbank.tlb into a COM+ package, I didn't see tagen.dll  in the properties 
of the component as I do in HIS2000.  But when I looked in the oleview I did 
see tagen.dll

I have installed the TI component of HIS2006.

Since I already have the mainframe CICS/Cobol programs set up for the 
CEDRBANK tutorial, I am going to work through the KB article you referenced 
to see if I can get the old CEDRBANK tutorial to work.  All I want to do at 
this point is test the connectivity to the mainframe from the new computer 
and new version of HIS.

By the way - I am getting an error message from SNA Service, Connections.  
In the event viewer the error is called SNA DLC Link Service TEST 
"Remote station not responding to TEST commands" the remote system is 
located across a bridge or router which is not forwarding DLC frames.

Note that this is the exact same SNA connection we are using from our 
Windows 2000 computer with HIS2000.  

Do you have any suggestions about why we are getting this error message?

We are using SNA because according to the Microsoft literature IBM does not 
support 2PC across IP.  

We are using this architecture:

ASP --> VB6 COM+ and MSDTC to support transactions, HIS2000 to communicate 
to mainframe via CICS LU6.2 SNA using the CICS Mirror Transaction to invoke 
CICS Cobol DPL programs which read and update both IMS and DB2 databases on 
the mainframe.

THe COM+ components also update SQL Server 2000 tables.

We need 2PC to ensure that all databases on all platforms are updated 
correctly.

"HISUser" wrote:

> We have been using HIS2000 for 8 years - COMTI  for 2PC Transaction 
> (APPC/LU6.2 CICS Link) across SQL Server 2000 database and on the mainframe 
> via CICS to read and update DB2 and IMS databases.
> 
> We are migrating from ASP to ASP.Net 2.0, VB6 to VB2005, SQL Server 2000 to 
> SQL Server 2005, and HIS2000 to HIS2006.
> 
> I have installed HIS2006 and set up SNA and the CICS_Link RE.
> 
> When I drag the COMTI component (tlb) into a COM+ package and try to test 
> the connectivity to the mainframe it doesn't work because there is no 
> tagen.dll in HIS2006.
> 
> Next I created a server export package from the 2000 environment so that I 
> would have a dll with both tagen.dll and the tlb.  
> 
> Next on the WIN2003 box with HIS2006 installed I double clicked on the 
> server package msi.  Still the test didn't work.  There is no tab on the COM+ 
> component to specify the RE.  When I tried to add the RE using the TI tool TI 
> couldn't find the RE I created.
> 
> Next I looked through the HIS2006 SDK to see if I could find a detailed, 
> step by step tutorial to test this specific situation, similar to the 
> CEDRBank tutorial that came with HIS2000.  
> 
> I found several tutorials but none that dealt specifically with testing 
> connectivity to a real mainframe (CICS) via SNA LU 6.2 and CICS_Link.
> 
> Please let me know if there is such a tutorial available and, if so, where I 
> can find it.
> 
> Also, we use the Oleview.exe on our Win2K boxes all the time.  Will this run 
> on a Win2003 Box?  If not, is there an oleview tool that will work on Win2003?
> 
> Thanks for your help.
> 
> 
>

date: Mon, 31 Mar 2008 06:40:01 -0700 author: HISUser