TCP Error Messages
NonStop Pathway/iTS Management Programming Manual—426749-002
12-37
Error-Message Range 3000 Through 3999
3179: ZPWY-ERR-TCP-TOOMUCHDATA
A SCREEN COBOL program unit attempted to execute the TRANSFORM verb, but
there was still data left unprocessed from the source data stream.
This error does not appear in the RETCODE token or in an error list; it appears only in
response to a STATUS TCP or STATUS TERM command.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the SCREEN COBOL program. For
instructions on how to locate the problem within the program, see Additional
Information for Terminal Errors on page 12-3.
3180: ZPWY-ERR-TCP-NOTENOUGHDATA
A SCREEN COBOL program unit tried to execute the TRANSFORM verb, but there
was not enough data in the source data stream to meet the requirements of the
destination data items.
This error does not appear in the RETCODE token or in an error list; it appears only in
response to a STATUS TCP or STATUS TERM command.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the SCREEN COBOL program. For
instructions on how to locate the problem within the program, see Additional
Information for Terminal Errors on page 12-3.
3181: ZPWY-ERR-TCP-BADFIELDSIZE
A field being processed during delimited field processing is larger than the maximum
size specified in the declaration. This situation is disallowed only on output processing
through the message section.
This error does not appear in the RETCODE token or in an error list; it appears only in
response to a STATUS TCP or STATUS TERM command.
Effect. The operation fails.
Recovery. Isolate and correct the problem within the SCREEN COBOL program. For
instructions on how to locate the problem within the program, see Additional
Information for Terminal Errors on page 12-3.
3182: ZPWY-ERR-TCP-DELIMNOTALIGNED
The delimiter’s offset was not byte-aligned during delimited field processing.
Consequently, a delimiter either cannot be appended to the field in an outbound
message or cannot be found in the input data stream of an inbound message.
This error does not appear in the RETCODE token or in an error list; it appears only in
response to a STATUS TCP or STATUS TERM command.
To Next Page
Loading...
Need help?
General