Starting Programs with the Attach Manager

When the attach manager starts a program on a workstation, it uses the load_type field in the defined transaction program list to decide how to run the program. A remotely started program can be configured to start in one of the following ways:
Console
An application that displays a window or runs as a full DOS application.
Background
The program starts in a background (detached) process. A background process should not issue any input or output calls to the keyboard, the mouse, or the display. If your program is completely debugged and requires no interactive user input, this option provides the fastest performance.

If the attach manager cannot start the program (for example, Personal Communications and Communications Server cannot provide sufficient memory), the attach manager rejects the incoming allocation request.

If a transaction program issues a RECEIVE_ALLOCATE call and specifies a transaction program name that has not previously been defined, the system performs an implicit definition of the transaction program and assigns default values to the parameters.

The defaults used are:

Attach timeout = 0 (no timeout is applied)
Receive Allocate timeout = 0 (no timeout is applied)
Attach Manager dynamically loaded = Yes (the transaction program can be loaded by the attach manager)

These defaults mean that if you issue a call to RECEIVE_ALLOCATE as previously described, it will not complete until an attempt is made to attach to the named transaction program, or you can cancel the call.