Follow these steps for exception responses.

1. Determine if the error indicator reflects an error in the RU portion of the PIU (sense = 1003 or 1005).

   If so, continue with this step.

   Otherwise, go to step 2.

   1. See what TPUT was issued. (This is shown in the flag byte of the TPUT trace entry.)
   2. For a NOEDIT TPUT, TSO/VTAM should not change the data provided by the application program. Compare the data in the TPUT trace, which starts at X'2C' into the trace record, with the VTAM® buffer contents trace.

      If TSO/VTAM has not changed the data, contact the group responsible for the application program that issued the TPUT.

   3. For a full-screen TPUT, determine whether the data that is causing the error was generated by the application program. (Data generated by the application program is present in the TPUT trace entry.)

      If so, contact the group responsible for the application program that issued the TPUT.

      If not, go to Reporting the problem to IBM.

2. Look at the error sense code.

   If it is X'800A', the PIU is too long.This is probably a definition error. In this case:

   1. Look in the TH portion of the buffer contents trace entry to find out the length of the PIU that caused the error.
   2. See how MAXDATA is defined on the PCCU definition statement in the NCP definition deck. The MAXDATA value that you code should be as large as the largest PIU that is sent to the terminal by an application program.
      Note: If you increase the value of MAXDATA, this value should not exceed the product of the MAXBFRU and UNITSZ operands. See z/OS Communications Server: SNA Network Implementation Guide for more information about defining the MAXDATA, MAXBFRU, and UNITSZ operands.

      If you have more than one PCCU definition statement, check to see that the right one is being used.

3. If there are other error indicators, get the documentation shown in step 5 and continue with that procedure.
4. If you have not resolved the problem, go to Reporting the problem to IBM.