TCP/IP Management Programming Manual

Event Management
HP NonStop TCP/IP Management Programming Manual—529636-001
7-31
16: ZTCI-EVT-CONF-FILE-ACC-ERR
(ZEMS-TKN-) CONSOLE-PRINT, CPU, CRTPID, GENTIME, LOGTIME, PIN,
SYSTEM, and USERID
are automatically placed in the header when the EMSINIT procedure is called and
the event message buffer is initialized. For a description of these tokens, see
Section 5, Common Definitions. For details on any of the EMS tokens, see the
EMS Manual.
ZTCI-TKN-SEV
contains the value ZTCI-VAL-SEV-WARN when this event is generated by the X.25
interface and the value ZTCI-VAL-SEV-FATAL when this event is generated by
SMTP or the Domain Name Server. The WARN value indicates that
ZTCI-EVT-CONF-FILE-ACC-ERR is only a warning message. The TCP/IP process
continues to function, but some functionality has been lost; for example, the
network may be going down, or a device accessed by the TCP/IP subsystem may
be experiencing errors. The FATAL value indicates that
ZTCI-EVT-CONF-FILE-ACC-ERR is fatal to the SMTP and Domain Name Server
processes. These processes halt when this error occurs, and they must be
restarted.
ZTCI-TKN-FNAME
contains the name of the file where the access error occurred.
Event-Message Text
In the text message, fname corresponds to the value in ZTCI-TKN-FNAME.
Cause. A configuration file has been secured incorrectly. This error is generated by
either the X.25 interface, SMTP, or the Domain Name Server.
This error is generated by the X.25 interface when the IP-to-X.25 address file has been
secured incorrectly. Because the IP-to-X.25 address file is not required, the TCP/IP
process continues to function and uses the default DDN IP-to-X.25 address mapping
instead.
This error is generated by SMTP or the Domain Name Server when one of these
programs cannot access one of its configuration files. The program that detected the
error exits because it cannot access the configuration file.
Recovery. If this error is generated by the X.25 interface, the IP-to-X.25 address file
should be secured so that it is readable by the person starting the TCP/IP process, and
the TCP/IP process should be restarted.
If this error is generated by SMTP or the Domain Name Server, the file should be
secured so that it is readable by the person starting the TCP/IP process, and the
process that detected the error should be restarted.