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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 15<br />

Class 15 CENLOG <strong>Message</strong>s<br />

CENLOGs in Class 15 result from recoverable communication line errors.<br />

Event 1 HARDWARE LINE ERROR (NOT A PP STATE<br />

ITEM)<br />

HARDWARE LINE ERROR (NOT A PP STATE ITEM)<br />

Description: A hardware error has been detected on the line indicated by the<br />

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

Action: If the errors are infrequent on a given line, this CENLOG display is<br />

informative only. If the errors on the line are occurring frequently, repair the line<br />

hardware. To determine the repair to the line hardware, you may need to retrieve the<br />

long form of the CENLOG display using the NMS LOGI command.<br />

ALPMCP<br />

Description: This event occurs when the line module detects an error. The<br />

supplemental message indicates whether it occurred on input or output. The<br />

hardware status is shown in the DEVICE–ID field of the short display, and in R15 of<br />

the long display. A high frequency of these events indicates a problem (hardware,<br />

configuration, operational, or device) that should be corrected. <strong>Telcon</strong> generates this<br />

CENLOG.<br />

CARRIER OFF (UNISCOPE)<br />

Description: This status bit is set when the carrier signal has dropped or is no longer<br />

received by the line module during input. R8 contains the value 0080 or 0081 (bit 7<br />

set). This CENLOG is generated by UNILPH. For more information on UNILPH<br />

CENLOG entry descriptions, refer to Section 1 of this manual.<br />

Action: Check modem, DCM, cluster controller, or terminal, and repair as necessary.<br />

The carrier-off condition is treated as an error only for synchronous lines. If logging<br />

this error should cause undue overhead to the system, you can issue an NMS STOP<br />

command for the line, poll group, or terminal, as applicable. When the source of the<br />

problem has been fixed or taken offline, issue an NMS STRT command to restore the<br />

normal operating environment.<br />

7436 0728–303 15–1

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

Saved successfully!

Ooh no, something went wrong!