Pathway/iTS Management Programming Manual

TCP Error Messages
NonStop Pathway/iTS Management Programming Manual—426749-002
12-19
Error-Message Range 3000 Through 3999
3068: ZPWY-ERR-TCP-NOTDBCSDATA2
The TCP encountered a data field that did not contain only double-byte (Kanji)
character data. The SCREEN COBOL programmer has attempted to display mixed or
single-byte characters in a PIC N only screen field, or to display a mixed field on an
IBM 3270 device that does not support mixed fields.
This is the same error as reported by 3067, except that, for internal reasons, the data
descriptor number is not available for reporting in the 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.
Effect. The program terminates abnormally.
Recovery. Abort the terminal from the Pathway subsystem and either upgrade the
terminal to support the application data or modify the requester-server application to
conform to the device environment.
3069: ZPWY-ERR-TCP-UNILATERALABORT
A terminal task has been suspended because the backup TCP encountered a backup
open error for the terminal task identified by term-name. This message is logged
when the following sequence of events occurs:
1. The backup TCP marks the terminal task as suspended but does not delete it until
the ABORT TERM command is executed.
2. The backup TCP sends a request to the primary TCP to suspend the
corresponding primary terminal task.
If the backup TCP becomes the primary TCP before the terminal task is deleted, the
terminal task remains suspended and this error is generated.
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 new primary terminal task is not in a valid executable state.
Recovery. Abort and restart the TERM object.
3070: ZPWY-ERR-TCP-BACKUPOPENERROR
A TERM task has been suspended because the backup TCP encountered a backup
open error for the TERM task identified by term-name. This message is logged when
the following sequence of events occurs:
1. The backup TCP marks the TERM task as suspended but does not delete it until
the ABORT TERM command is executed.
2. The backup TCP sends a request to the primary TCP to suspend the
corresponding primary TERM task.