DCP Series Telcon Message Manual - Public Support Login - Unisys

Event 8 ABNORMAL LINE TERMINATION FUNCTION
NTRLPH
Description: This event occurs if an NTR site is terminated abnormally. The
supplemental message identifies the source of the abnormal termination. The NTR
site is signed off, with any active output files being requeued. If any input device is
active when this occurs, all of the input file is discarded. The LINE/SITE DOWNED, or
RE-SIGNON case need not be investigated further. The FATAL INPUT/OUTPUT
ERROR case should be investigated for a possible hardware problem, as should the
MAX OUTPUT RETRY case. The NO RESPONSE or NAK-SEQ OVERFLOW cases
indicate that the DCP cannot communicate with the remote site either because of a
hardware problem, or because the remote site has crashed or has hardware problems
of its own. The NAK-LOOP case indicates that the same message is being affected by
NAK, but the recovery process is working without any hardware error. This is usually
caused by a configuration error (wrong buffer sizes), or a protocol handling error in
the software. Any preceding recoverable error CENLOGs should also be examined for
any of these cases. Other information logged:
R9: Nak-1 detail code
01 Message too long
02 Message too short
03 Input message timeout
04 Message-number sequence error
05 Response time-out (idle-site handshake)
07 Parity/LRC error
08 First character not SON or S
R10:
0A Input overrun/output underrun
0C No buffer for input
0D Too many inputs without ACKing outstanding output
0E Wrong FDX/HDX sign on for line configuration
The active device counts word (NS$ADC) from the SCT
R12: The NS$STAT1 flag word from the SCT
R13: The NS$STAT2 flag word from the SCT. All NS$ equates are defined in
AANTRDEF.
Telcon generates this CENLOG.
14–16 7436 0728–303