RECEIVE_ALLOCATE Hangs on Windows NT SNA Server Client

SYMPTOMS

When you run a 32-bit Windows APPC application on an SNA Server Windows NT client, the following symptoms occur:

NOTE: These symptoms do not occur when you run the application on the SNA server.

• A transaction program name of SASRMT is registered as an autostarted invokable transaction program (with a service type of 0x05). An incoming attach is received which starts up the application.
• This application then issues a RECEIVE_ALLOCATE on the SASTP62 TP name, which is configured as a queued operator started transaction program (with a service type of 0x1A). However, this receive allocate hangs indefinitely.

The SNA Server receives the attach request on the SASTP62 name, though it is never routed to the Windows NT client computer.

This problem does not occur with autostarted invokable transaction programs.

NOTE: It is possible to configure a Timeout value for the invokable transaction program within the Windows NT registry (for Win32 applications) or WIN.INI (for Win 3.x applications) so that the RECEIVE_ALLOCATE does not wait forever. See the SNA Server APPC and CPIC Programmer's Guide, Chapter 2 for information about the Timeout parameter.