The OMVS command ended because incorrect data was received
from the terminal. This is a terminal or system error. No data bytes
were received from the terminal. Function = TGET,
return
code = return-code
The first character
(X'aid-byte')
was unexpected. Function
= TGET,
return code = return-code,
data
count = data-count
The location of
the cursor was
partly missing. Function = TGET,
return
code = return-code,
data count = data-count,
data
= incomplete-cursor
Unexpected control
information
was received from the terminal.
Function
= TGET,
return code = return-code,
data
count = data-count,
data = unexpected-order
Data
describing the screen location
of the input field was
incomplete.
Function = TGET,
return code
= return-code,
data count = data-count,
data
= incomplete-address
The input data
came in from an
unexpected screen location.
Function
= TGET,
return code = return-code,
data
count = data-count,
data = unexpected-address
Input
data came in from more
than one location on the screen.
Function
= TGET,
return code = return-code,
data
count = data-count,
data from second
field =
second-field
Input
data was received when none
was expected. Function = TGET,
return
code = return-code,
data count = data-count,
data
= unexpected-input
The final character
of input data
was missing. Function = TGET,
return
code = return-code,
data count = data-count,
data
= incomplete-input
An unexpected character
was
found in the input data.
Function =
TGET,
return code = return-code,
data
count = data-count,
data = unexpected-bytes
Too
much input data was received.
Function = TGET,
return
code = return-code,
data count = data-count,
data
= starting-data
An incorrect DBCS
mixed string
was received. Function = TGET,
return
code = return-code,
data count = data-count,
data
= mixed-data
Explanation
The
OMVS command received incorrect data
from the 3270 terminal. This error is probably caused by a terminal
or system problem, and not by what the user entered. The second-level
message describes the specific data stream error seen by the
OMVS command:
- FSUM2092I
- The OMVS command issued TGET and received no data from
the terminal. In full-screen mode, the terminal should always send
in at least 1 byte of data (the AID byte).
- FSUM2093I
- The first byte of data from the terminal was not one of the expected
3270 AID bytes.
- FSUM2094I
- Only 2 bytes of data were received from the terminal in full-screen
mode. This indicates that the second byte of the cursor address was
missing in the data stream.
- FSUM2095I
- An unexpected display order was received from the terminal. The
first display order in the data stream should be the 3270 SET BUFFER
ADDRESS (SBA) order.
- FSUM2096I
- Exactly 5 bytes of input data were received from the terminal.
The second byte of the screen address of the first input field is
missing.
- FSUM2097I
- Input data was received from some location other than the usual OMVS command
input area at the bottom of the screen. This error can be caused
by repeatedly entering data while the normal OMVS command screen
is not being displayed.
- FSUM2098I
- Input data was received from two or more input fields on the same
screen. This error can be caused by repeatedly entering data while
the normal OMVS command screen is not being displayed.
- FSUM2099I
- Input data was received while the OMVS command did not
have an input area on the screen. This error can be caused by repeatedly
entering data while the normal OMVS screen is not being displayed.
- FSUM2100I
- The data stream received from the terminal ended with a graphic
escape (GE) character, but there was no character following the GE.
- FSUM2101I
- The data stream received from the terminal contained one or more
of the following unexpected characters:
- SET ATTRIBUTE (SA)
- START FIELD (SF)
- START FIELD EXTENDED (SFE)
- SHIFT OUT (SO)
- SHIFT IN (SI)
- NULL
- FSUM2102I
- Too much data was received from the terminal. The data was too
long to fit in the normal input area at the bottom of the screen.
This error can be caused by repeatedly entering data while the normal OMVS command
screen is not being displayed.
- FSUM2103I
- An odd-length DBCS subfield in a mixed DBCS string was received
from the terminal. In addition, the final (odd) byte was out of range
for DBCS data. The terminal should never send in odd-length DBCS
subfields or incorrect characters in DBCS subfields.
In the message text:
- return-code
- The return code from TSO/E.
- aid-byte
- The first byte of data, in hexadecimal, from the terminal. This
is the unexpected 3270 AID byte.
- data-count
- The number of bytes of data received from the terminal.
- incomplete-cursor
- The 2 bytes of data, in hexadecimal, received from the terminal.
The last byte is the incomplete cursor address.
- unexpected-order
- The first few bytes of data, in hexadecimal, received from the
terminal. These bytes contain the unexpected 3270 display order that
was received.
- incomplete-address
- The first 5 bytes of data, in hexadecimal, received from the terminal.
The last byte of data is the incomplete screen address of the first
input field.
- unexpected-address
- The first few bytes of data, in hexadecimal, received from the
terminal. These bytes contain the unexpected screen address of the
input data.
- second-field
- The first few bytes of data, in hexadecimal, received from the
second input field on the screen.
- unexpected-input
- The first few bytes of data, in hexadecimal, received from the
terminal. These bytes contain the unexpected input data.
- incomplete-input
- The last few bytes of data, in hexadecimal, received from the
terminal. The last byte of data is the start of an incomplete graphic
escape character.
- unexpected-bytes
- A few bytes of data, in hexadecimal, received from the terminal,
The first byte of data is the unexpected character.
- starting-data
- The first few bytes of data, in hexadecimal, received from the
terminal,
- mixed-data
- The last few bytes of an odd-length DBCS subfield received from
the terminal. The last byte is the usually the Shift In (SI) or Shift
Out (SO) character that ends the incorrect subfield.
System action
The OMVS command ends and returns to TSO/E,
ending the shell session.
System programmer response
Examine the bytes of data from the
terminal in the second-level message. If there is a terminal data
stream error, determine the cause of this error.
If there is
too much data or data from unexpected input fields, there may be no
terminal or system problem. It is possible that the user repeatedly
entered data while the normal OMVS command screen was not being
displayed. In these cases, use the DEBUG(DATA) keyword on the TSO/E OMVS command
to trace the data from the terminal.
User response
Report this problem to the system programmer.