Interacting With Applications › Receive Data from the Application › Problems with the WINP Command

Problems with the WINP Command

Two problems can occur with the WINP command.

• If the application sends no data, the ACL/E program will go into an infinite wait.
• If you use WINP to wait for data to be displayed and SEARCH to examine the data after it has been displayed, it is possible for the program to go into an endless loop. For example, a program might have code similar to the following:

  LOOP1   WINP             WAIT FOR DATA FROM APPLICATION
          SEARCH 'Ready'   IS THE READY PROMPT DISPLAYED
          BRANCH NE,LOOP1  NO, WAIT LONGER
  

If the string "Ready" is never sent from the application, the program will go into an endless loop waiting for it to be displayed. Even if the application sends data that the program does not use, the WINP command will tell the program to continue execution. Unless you take measures to prevent an endless loop, the program can go into one if unexpected data is sent from the application.