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 (886300)

MORE INFORMATION

Depending on the result that you want, one of the following methods of type library conversion must be performed:

• Open and Save: This method updates the Remote Environment class. No changes are made to either the type library GUIDs or the default conversions.
  
  You can open and save a type library either by dragging the type library to the project or by clicking Library on the Import submenu on the File menu. After you import the type library, click Save on the File menu.
• Open and Save As: This method updates the Remote Environment class and generates new type library GUIDs. No changes are made to the type library default conversions.
  
  You can open a type library either by dragging the type library to the project or by clicking Library on the Import submenu on the File menu. After you import the type library, click Save As on the File menu. When you are prompted to replace the file, click Yes.
• Manual Import: This method updates the Remote Environment class, generates new type library GUIDs, and adds Host Integration Server 2004 defaults to the new library.
  
  Important Remember to back up your original type library files before you run the Microsoft Host Integration Server Transaction Integrator (TI) Designer because you cannot revert to the previous format, SNA 4 or Host Integration Server 2000, after the files have been modified.
  
  Note These steps import a LU 6.2 CICS Link component; other Remote Environment types will look slightly different. Additionally, these steps suggest that you use the same library name and the same interface name as the original type library. By using the same library name and the same interface name, the ProgID of the new component will be the same as the original component.
  
  To perform a manual import, follow these steps:
  1. Start Visual Studio .NET 2003.
  2. On the File menu, click New, and then click Project.
  3. In the New Project dialog box, click HIS Projects, and then click TI Project.
  4. In the Name box, type ProjectName (where ProjectName is the name of your project), and then click OK.
  5. In the Solution Explorer pane, right-click ProjectName, click Add, and then click either Add COM Client Library or Add .Net Client Library.
  6. In the Name box, type the library name from pre-Host Integration Server 2004 type library, and then click Open.
     
     Note You can use Component Builder to obtain the library name.
  7. When the New COM Client Library Wizard opens, click Next.
  8. In the Interface Name box, type the interface name from pre-Host Integration Server 2004 type library, and then click Next.
     
     Note You can use Component Builder to obtain the interface name.
     
     Note Click the Support Visual Basic 6.0 decimal type option if you want the component to permit applications that are written with Visual Basic 6.0 or an earlier version to use early binding to access TI components that reference types. For most cases, this option should be clicked.
  9. On the Remote Environment Configuration page, make sure that you have selected the correct options, and then click Next two times.
  10. Click Create to finish creating the COM Client Library shell so that you can import your pre-Host Integration Server 2004 type library.
  11. To import your pre-Host Integration Server 2004 type library with the new definition selected, follow these steps:
      1. On the File menu, click Import, and then click Library.
      2. Locate and then click your pre-Host Integration Server 2004 type library.
      3. Click Open.
      4. If you receive a "CICS_LINK.TLB: "" is not a valid Mirror Tran ID" build error, follow these steps for each method that is defined in the type library:
         1. Click the method name.
         2. In the Properties pane, type CSMI in the Mirror Transaction ID box, and then press ENTER.
         Note CSMI is the default Mirror Transaction name. For some mainframes, this entry may be different.
      5. On the File menu, click Save All to save the project.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: