DCP Series Telcon Message Manual - Public Support Login - Unisys

Event 3 EVENT/ERROR DETECTED AT L3 (NETWORK)
PDNL3 CALLED BUT X.25 IS NOT UP
Description: The PDNL3 module was activated, but X.25 PSCS has not (yet)
initialized. An item, such as a Call Request primitive from a layer 4 module, has been
placed on the PDNL3 queue, but no X.25 PSCS tables have been built for processing
the item.
Attributes affected: Supplementary text message. The X.25 PSCS program product
generates this CENLOG. Procedure: PDNL3.
Action: Verify that at least one of the X.25 PSCS lines is enabled on a valid line
module using an NMS UP LINE command. If a line has already been enabled, then
X.25 PSCS may currently be initializing; or an initialization error has occurred and has
been recorded with a CENLOG class/event of 5/15 with a supplementary text message
of: “PSCS initialization error.”
PDNURS - PSCS NOT INITIALIZED, MESSAGE DISCARDED
Description: An NMS TERM command was entered and the TERM name is
associated with either a UTS 4000 cluster controller workstation or an X.29 PAD
terminal running over an X.25 network. Because the X.25 program product is not yet
initialized the command cannot be processed.
Attributes affected: Supplementary text message. The X.25 PSCS program product
generates this CENLOG. Procedure: PDNURS.
Action: No action required. Because X.25 PSCS is not initialized, no internal run-time
terminal table exists for updating.
SNA: 808 - no actid match for ACT/TEST REPLY
Description: This message occurs as a result of errors in Path Control (ERVR), the
network routing portion of SNA/net. The probable cause is a software problem.
13–60 7436 0728–303