TCP Event Messages
3063: ZPWY-EVT-TCP-BADDBCSKKDATA2
Translation routines were unable to correctly translate data from the internal format to
the external format required by the device. inst-addr identifies the SCREEN
COBOL operand that encountered the problem.
This is the same error as reported by 3062, except that, for internal reasons, the data
descriptor number is not available for reporting in the message. The offset can be
mapped to the SCOBOLX verb that failed if the compiler ?MAP directive is used.
For a description of tokens that are present in this event message but are not listed or
described here, see the TS/MP Management Programming Manual.
Unconditional Tokens
ZEMS-TKN-EMPHASIS
ZEMS-TKN-EVENTNUMBER
ZEMS-TKN-SUBJECT-MARK
ZPWY-TKN-TERMNAME
ZPWY-TKN-EVENTCLASS
Conditional Tokens
ZPWY-TKN-INSTRUCTION
ZPWY-TKN-PUNAME
ZPWY-TKN-PUOFFSET
ZPWY-TKN-PUVERSION
ZPWY-TKN-TCLPROGFNAME
Event-Message Text
*3063* INVALID KATAKANA OR DBCS DATA - INST ADDR inst-addr
--- INST CODE:
unit(version) IN TCLPROG tclprog
Token Descriptions
ZEMS-TKN-EMPHASIS
has a value of ZSPI-VAL-FALSE.
ZEMS-TKN-EVENTNUMBER
contains ZPWY-EVT-TCP-BADDBCSKKDATA2 (3063).
ZEMS-TKN-SUBJECT-MARK
indicates ZPWY-TKN-TERMNAME, which contains the name of the TERM object
that is the subject of this event message.
NonStop Pathway/iTS Management Programming Manual—426749-002
token-type ZSPI-TYP-BOOLEAN.
token-type ZSPI-TYP-INT.
token-type ZSPI-TYP-SSCTL.
token-type ZPWY-TYP-TERMNAME.
token-type ZSPI-TYP-ENUM.
token-type ZSPI-TYP-ENUM.
token-type SCOBOL-PUNAME.
token-type ZSPI-TYP-INT2.
token-type ZSPI-TYP-INT2.
token-type ZSPI-TYP-FNAME32.
instruct AT OFFSET %offset IN PROGRAM UNIT
11- 107
Need help?
Do you have a question about the NonStop Pathway/iTS and is the answer not in the manual?
Questions and answers