Diagnosis
1. For interactive output, R/3 with WINDOWS Frontend must not beexecuted in full-screen mode since WINDOWS is not a genuinemultitasking system. When R/3 is executed in full-screen mode adeadlock is created since the R/3 screen waits for the end of M/TEXTprocessing and M/TEXT waits for the user's entries. WINDOWS does notallow you to switch between windows in this configuration.
2. R/3 M/TEXT communications program not started.

System Response
1. Endless wait.
2. Output unsuccessful.

Procedure
1. The UNIX process must be stopped. To do this, the R/3 Systemadministrator adm must login and stop the M/TEXT process.
To avoid this situation, the M/TEXT output must not be carried outin full-screen mode. There needs to be at least one other window inthe foreground so that the computer does not totally freeze. Thisshould be the UNIX window in which the R/3 M/TEXT communicationsprogram runs.
2. Under UNIX, logon to the M/TEXT server and start the R/3 M/TEXTcommunications program.