COMTI Does Not Support the EZACICSE Security Exit That is Supplied By IBM (321101)



The information in this article applies to:

  • Microsoft Host Integration Server 2000

This article was previously published under Q321101
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SUMMARY

COMTI TCP/IP security information that is sent in a transaction request message (TRM) is not in a format that is compatible with the default security exit, EZACICSE, that is supplied by IBM. To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

328152 How to Obtain the Latest Host Integration Server 2000 Service Pack

MORE INFORMATION

COMTI TCP/IP security information is sent in the following format:

ByteData
1 - 4Transaction Program Name
5'0x6B' (Comma Separator)
6 - 13User ID
14 - 21Password
22 - 40Program Data

Microsoft has updated COMTI to support the default IBM-supplied security exit, EZACICSE. After you apply the update and add the specified registry entry, COMTI TCP/IP security information that is supported by EZACICSE is sent in the following format:

ByteData
1 - 4Transaction Program Name
5'0x6B' (Comma Separator)
6'0x01'
7 - 14Password
15 - 22User ID
23 - 40Program Data

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

This update requires that you add a registry key so that COMTI can send the TCP/IP security information using the IBM format for EZACICSE. To add the registry key, follow these steps:
  1. Start Registry Editor (regedit.exe).
  2. Locate and click the following key in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cedar\Defaults

  3. On the Edit menu, click New, and then click Key.
  4. Type UseIBMTCPSecurityExit, and then press ENTER.
  5. Select the new UseIBMTCPSecurityExit key.
  6. In the right pane of the dialog box, select (Default).
  7. On the Edit menu, click Modify, and then enter the following Value data: Value data: TRUE.
  8. Click OK, and then quit Registry Editor.
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Microsoft Host Integration Server 2000 service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size    File name
   --------------------------------------------------
   20-Feb-2002  17:32  5.0.0.836    106,768 Trantcp.dll
				

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.


Modification Type:MajorLast Reviewed:10/21/2005
Keywords:kbBug kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix kbinfo KB321101