| Event Id | 730 |
| Source | SNA Base Service |
| Description | The Host Integration Server computer was unable to locate an invokable TP TPName, APPC LU Alias APPCLUAlias, Workstation name: WorkstationName. |
| Event Information | According to Microsoft: CAUSE: This problem occurs because the Host Integration Server 2004 client does not correctly initialize an internal flag when the SnaBase service (Snabase.exe) starts. If the internal flag is not correctly initialized, the SnaBase service does not register invokable APPC or CPI-C transaction programs (TPs) with the sponsor server of the Host Integration Server 2004 client. Mainframe applications cannot communicate with invokable APPC or CPI-C applications if they are not registered with the Host Integration Server 2004-based servers in the Host Integration Server subdomain. An attempt to invoke the APPC TP shown has failed because Host Integration Server did not find the TP name registered on any client in the subdomain. If this is an auto-started TP, make sure the TP is defined on the client machine using the Host Integration Server TPSETUP program. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem.Only apply it to systems that are experiencing this specific problem. To work around this problem, run the SNA Trace Utility (Snatrace.exe) on the Host Integration Server 2004 client. Then, enable one or more of the trace settings that are available for the SnaBase service. If the invokable TP is started after you enable SnaBase traces on the Host Integration Server 2004 client, the TP will be registered on the Host Integration Server 2004-based servers. |
| Reference Links | when a mainframe application tries to invoke an APPC or CPI-C application that is running on a Host Integration Server 2004 client |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.