30.01.2013 Views

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

DCP Series Telcon Message Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NTRLPH<br />

Event 2 COMMUNICATIONS LINE PROTOCOL ERROR DETECTED<br />

Description: This event occurs if the NTR PP program (NTRIOP) detects a line<br />

protocol error. A supplemental message specifies what type of error was detected.<br />

Recovery is initiated as per NTR/FDR protocol. This indicates a possible<br />

configuration, software, or hardware error. Other information logged:<br />

R8: status-flags (from SDT)<br />

R9: NAK–1 detail code<br />

01 <strong>Message</strong> too long<br />

02 <strong>Message</strong> too short<br />

03 Input message time-out<br />

04 <strong>Message</strong>-number sequence error<br />

05 Response-time-out (idle-site handshake)<br />

07 Parity/LRC error<br />

08 1st character not SOH or G<br />

R13:<br />

0A Input overrun/output underrun<br />

0C No buffer for input<br />

0D Too many inputs without acknowledging outstanding output<br />

0E Wrong FDX/HDX sign-on for line configuration<br />

Least significant byte of transfer count<br />

R14: PP ID<br />

<strong>Telcon</strong> generates this CENLOG.<br />

NTRV2R<br />

Description: This event occurs if NTRV2R detects a line protocol error. A<br />

supplemental message specifies what type of error was detected. Recovery is<br />

initiated as per NTR/FDR protocol. This indicates a possible configuration, software,<br />

or hardware error. Other information logged (for BAD CONTROL case):<br />

R15: The device number the bad control message was for.<br />

<strong>Telcon</strong> generates this CENLOG.<br />

7436 0728–303 15–7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!