Follow these steps if data is misplaced on your screen or page.

1. Does data wrap around the screen?(Wrapping means that data fills the line and splits inappropriately between lines.)

   If it does, continue with this step.

   Otherwise, go to step 2.

   1. Find out which TPUT option was issued. Bytes X'12' and X'13' of the TPUT trace entry contain the option flags.
   2. For a NOEDIT TPUT, TSO/VTAM does not edit data, and therefore does not change any SBA sequences that may be issued by the application program. Contact the group responsible for the application program that issued the TPUT.
   3. For a full-screen TPUT, TSO/VTAM does not generate SBA sequences to place the data on the screen.

      If the symptom is incorrect screen size, go to Screen size problems. Otherwise, contact the group responsible for the application program that issued the TPUT.

   4. If the data was sent without a full-screen or NOEDIT option, go to Reporting the problem to IBM.
2. If the problem is not on a display terminal, go to Reporting the problem to IBM.
3. Are SBA sequences correct? Check the type of TPUT that was issued. Bytes X'12' and X'13' of the TPUT trace entry contain the option flags. For full-screen and NOEDIT TPUTs, the application program usually generates the SBA sequences that determine where data is placed on the screen.
4. Is the buffer address incorrect?
   • If the buffer address is not valid for the screen size, contact the group responsible for the application program.
   • If the buffer address is valid for the terminal in its present screen size, go to Reporting the problem to IBM.
5. If this is the first nonfull-screen TPUT following a full-screen TPUT, look for an SVC 94 trace entry for STLINENO.This macro may be issued by a full-screen application to indicate which line the next nonfull-screen data should appear on.

   If the data was placed by the STLINENO macro, contact the support group for the application program that issued the macro.

6. If you have not resolved the problem, go to Reporting the problem to IBM.