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 />

IPM EVENT<br />

Event 9 IPM EVENT<br />

Description: An event occurred concerning an interprogram message (IPM) queue<br />

and may have involved two independent <strong>Telcon</strong> runs. <strong>Telcon</strong> generates this CENLOG.<br />

Action: None.<br />

DTPIPM - INITIALIZATION ERROR<br />

Description: DTPIPM failed IPM registration because there is a duplicate IPM<br />

receiver name. This can occur when multiple <strong>Telcon</strong>s are executed with the same<br />

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

Action: Change the node ID on the <strong>Telcon</strong> execution statement.<br />

DUPLICATE NODEID DETECTED BY NMSOS<br />

Description: The <strong>DCP</strong> is running multiple <strong>Telcon</strong>s. Your <strong>Telcon</strong> has a duplicate<br />

node ID specified on the <strong>Telcon</strong> execute statement, or no node ID specified. If no<br />

node ID was specified, your <strong>Telcon</strong> is running with the default node ID (N1) and<br />

another <strong>Telcon</strong> is also running with the default node ID. <strong>Telcon</strong> generates this<br />

CENLOG.<br />

Action: None, unless IPPs are configured. If IPPs are configured, restart <strong>Telcon</strong> and<br />

use a unique node ID on the <strong>Telcon</strong> execute statement.<br />

NMSOS<br />

Description: This event occurs when a duplicate node ID is detected (<strong>Telcon</strong><br />

execute statement). <strong>Telcon</strong> generates this CENLOG.<br />

7436 0728–303 6–19

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

Saved successfully!

Ooh no, something went wrong!