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.

Event 9 IPM EVENT<br />

X.25 SNMP: Received non-connect IPM Contingency (“procedure<br />

name”)<br />

Description: The X.25 PSCS SNMP interface module (PDNSMP) received an interprogram<br />

message (IPM) contingency that is not related to the disconnection of a<br />

pending or existing ICS connection. This type of IPM contingency causes PDNSMP to<br />

re-initialize its connections with ICS and the SNMP Agent’s manager-agent user<br />

interface.<br />

R8: IPM contingency type<br />

Attributes affected: Recoverable error event, supplementary text message.<br />

Procedure: The procedure name, which is internal to the X.25 PSCS PDNSMP<br />

module, is displayed as part of the supplementary text message.<br />

Action: PDNSMP should automatically recover from this event. However,<br />

subsequent occurances indicate an error with either <strong>DCP</strong>/OS, ICS, or PDNSMP. In<br />

this case, you should take a <strong>Telcon</strong> dump and submit a UCF.<br />

X.25 SNMP: IPM queue registration error (“procedure name”)<br />

Description: The X.25 PSCS SNMP interface module (PDNSMP) was unable to<br />

register one of its inter-program message (IPM) queues. This error causes PDNSMP to<br />

become dormant. In this case, no SNMP MIB information related to X.25 can be<br />

retrieved.<br />

Attributes affected: Error event, supplementary text message, and a table of the<br />

IPM Channel (queue) table.<br />

Procedure: The procedure name, which is internal to the X.25 PSCS PDNSMP<br />

module, is displayed as part of the supplementary text message.<br />

Action: You must re-start <strong>Telcon</strong> in order to recover from this error. Subsequent<br />

occurances indicate and error with either <strong>DCP</strong>/OS, ICS, or PDNSMP. In this case, you<br />

should take a <strong>Telcon</strong> dump and submit a UCF.<br />

6–20 7436 0728–303

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

Saved successfully!

Ooh no, something went wrong!