SAP ABAP Message Class 69 Message Number 268 (No full screen. Can UNIX window be seen ? R/3 M/TEXT-Comm. initiated ?)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       FVV (Package) R/3 application development for Financial Assets Management
Attribute
Message class 69  
Short Description Central Functions of Financial Asset Management    
Message Number 268  
Documentation status      
Authorization check Error Message      
Changed On    
Message Text
No full screen. Can UNIX window be seen ? R/3 M/TEXT-Comm. initiated ?
Help Document

Diagnosis

1. For interactive output, R/3 with WINDOWS Frontend must not be executed in full-screen mode since WINDOWS is not a genuine multitasking system. When R/3 is executed in full-screen mode a deadlock is created since the R/3 screen waits for the end of M/TEXT processing and M/TEXT waits for the user's entries. WINDOWS does not allow 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 System administrator <sid>adm must login and stop the M/TEXT process.

To avoid this situation, the M/TEXT output must not be carried out in full-screen mode. There needs to be at least one other window in the foreground so that the computer does not totally freeze. This should be the UNIX window in which the R/3 M/TEXT communications program runs.

2. Under UNIX, logon to the M/TEXT server and start the R/3 M/TEXT communications program.

History
Last changed on/by 19970523  SAP 
SAP Release Created in