DCP Series Telcon Message Manual - Public Support Login - Unisys

Event 2 EVENT/ERROR DETECTED AT L2 (LINK)
Event 2 EVENT/ERROR DETECTED AT L2 (LINK)
EVENT/ERROR DETECTED AT L2 (LINK)
Description: A procedure that transfers information across a physical link detected
an error. Such errors may be either recoverable or fatal. For fatal errors, a system
dump may be initiated or the procedure may be blocked. Telcon generates this
CENLOG.
Action: This may be a symptom of problems of a particular physical link the user
encountered. This message may signal the operator to take a system dump when
attempting to trap such a problem. Frequent occurrences of such errors/events may
indicate that corrective action should be taken.
ALPMCP
Description: The ASYNCH link service has detected a software error. The error
severity code is in R10, and the error code (6Fxx) is in R11. Severity codes are as
follows: 0 = fatal, 1 = serious, 2, 3, 4 = trivial. Telcon generates this CENLOG.
ASYNMLCP
Description: The ASYNCH link service has detected an input error.
R8 = 0024
R9 = 8000 No buffer - the port processor could not obtain a buffer for message
4000 Input limit - more input came in that there is buffer space
0400 Message timeout - input came in without an end of message character
0200 DSR off - data set ready has been dropped and the line will disconnect
0100 Parity error - configured line speed, parity or character length does not
match what the hardware or software in PC is set up to
0040 Data overrun - the port processor cannot keep up with the rate at which
the input is being received
PDNSVS
Description: The X.25 line initialization module (PDNSVS) was unable to successfully
complete the connection of an enabled line. This event includes the LINE name.
R15: Error reason code
Attributes affected: Line event, Configuration event, Line Control Block (LCB)
address in register R11. The X.25 PSCS program product generates this CENLOG.
Procedure: PDNSVS.
7436 0728–303 13–3