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.

Event 14 CONFIGURATION FILE ACCESS / REQUEST ERROR<br />

SNA: 256 – Configuration access error<br />

Description: This message occurs as a result of not being able to access the<br />

configuration file.<br />

SNA: 1820 – SNMS Move –Cfaccs error move incomplete<br />

Description: This message occurs as a result of errors in SNMS, the part of SNA/net<br />

that processes operator commands. The probable cause is a software problem.<br />

SNA: 2204 – Config access error, code= &&&&&<br />

Description: This message occurs as a result of errors in the trunk used to connect<br />

DCA traffic across an SNA network. The & represents a decimal number. The<br />

probable cause is a software problem.<br />

SNA: 2406 – Config access error, code= &&&&&<br />

Description: The new boundary function (NBF) handles all of the management<br />

messages for 3270 connected devices, IBF connections to NCPs, and connections to<br />

NT 2.1 devices. The & represents a decimal number. The probable cause is a<br />

hardware problem.<br />

SNA: 2625 – (PS) CFACCS error<br />

SRC<br />

SRC<br />

SRC<br />

Description: This message indicates internal software exceptions. Useful for<br />

network analysts in determining status of environment.<br />

Description: SRC is processing a connect indication from DTP. The attempt to<br />

convert the from-name to a <strong>DCP</strong> ID by locating it in the configuration ID table is<br />

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

Description: SRC is processing an UPDATE TS STATUS command from the<br />

alternate <strong>DCP</strong>, or is trying to send one. The attempt to locate the appropriate DCATS<br />

configuration statement in the configuration is unsuccessful. <strong>Telcon</strong> generates this<br />

CENLOG.<br />

Description: When SRC receives the first resilient LINE configuration statement for<br />

a particular <strong>Telcon</strong> node, it cycles through the RCM configuration statements in the<br />

configuration looking for the one that corresponds to that <strong>Telcon</strong> node. This RCM<br />

configuration statement cannot be found. <strong>Telcon</strong> generates this CENLOG.<br />

5–72 7436 0728–303

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

Saved successfully!

Ooh no, something went wrong!