Chapter 25 DNS (Distributed Name Service) Messages

The messages in this chapter are sent by Distributed Name Service (DNS). These messages are generated when:

DNS is initialized on a system.
A change of state occurs in one of the DNS named processes.
A significant unexpected error is detected.

The subsystem ID displayed by these messages includes DNS as the subsystem name.

DNS generates four types of messages: error messages (ERROR), fatal error messages (FATAL), status messages (STATUS), and warning messages (WARNING). All messages are preceded by the issuing process’s name. A name manager process is represented by the variable mgr-proc. A name exporter process is represented by the variable exp-proc. Refer to the Distributed Name Service (DNS) Management and Operations Manual and the Distributed Name Service (DNS) Management Programming Manual for more information.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

{mgr-proc | exp-proc}: STATUS *0001* { DNSMGR | DNSEXP } - version, Started

Cause A name manager or name exporter process has begun execution.

Effect The process executes.

Recovery Informational message only; no corrective action is needed.

{mgr-proc | exp-proc}: STATUS *0002* { DNSMGR | DNSEXP } - { Normal | Fast | Error } Shutdown

Cause The specified name manager or name exporter process has shut down in the manner indicated:

Normal	indicates an orderly shutdown.
Fast	indicates a fast shutdown, such as is initiated by the DNSCOM STOP ! command.
Error	indicates a shutdown caused by an error; the error had been described in a previous message.

Effect The issuing process has stopped.

Recovery If the shutdown is caused by an error, determine the nature of the error by examining the preceding messages issued by the process. Then take appropriate corrective action. For normal or fast shutdown, no corrective action is needed.

{mgr-proc | exp-proc}: WARNING *0003* { DNSMGR | DNSEXP } - Eventlog Switched to $0

Cause A name manager or name exporter process encountered an unrecoverable I/O error while attempting to write to its configured EVENTLOG.

Effect The process closes the configured log, then opens and sends a message to $0. The process continues to log all messages to $0 until DNS is stopped and restarted.

Recovery Check the device or process that corresponds to the configured EVENTLOG. This message is accompanied by DNS operator message 20 or 21. Refer to the description of message 20 or 21 for more information.

{mgr-proc | exp-proc}: STATUS *0004* (type) (task-number) - Started

Cause A name manager or name exporter process created the specified new task (thread).

Effect None.

Recovery Informational message only; no corrective action is needed.

{mgr-proc | exp-proc}: STATUS *0005* type (task-number) - Stopped

Cause The specified task (thread) stopped executing in a name manager or name exporter process.

Effect None.

Recovery Informational message only; no corrective action is needed.

\system.manager: STATUS *0006* type (task-number) Opened by process-descriptor (group, user)

Cause A name manager process accepted an open message from a requester.

Effect None.

Recovery Informational message only; no corrective action is needed.

mgr-proc: WARNING *0007* #ZSPI (task-number) - Aborted

Cause A processor failed. A DNS requester that is not a NonStop process was running in the processor.

Effect The remaining processors in the system where the failed requester was running display message CPU 101.

Recovery Follow your site’s recovery procedure for a processor failure.

\system.manager: STATUS *0008* type (task-number) - Closed by process-descriptor

Cause A requester closed a name manager process. For requesters that run with backups, the event is generated only when process close messages have been received from both the primary and backup requester processes.

Effect None.

Recovery Informational message only; no corrective action is needed.

mgr-proc: STATUS *0009* type (task-number) - Restarted (restart-type)

Cause A name manager process restarted the specified task after the primary name manager process failed.

Effect None.

Recovery Informational message only; no corrective action is needed.

mgr-proc: ERROR *0010* Checkpoint Failure: errnum

Cause File-system error errnum occurred during a checkpoint operation. Errors 30 through 37 indicate a resource-allocation failure and may indicate that the primary and/or backup name manager’s processor is overloaded.

Effect The backup name manager process stops. The system tries to create a new backup after a 30-second delay. If a new backup process is created, the system displays DNS operator message 16.

Recovery For errors 30 through 37, try to decrease the load on the name manager’s backup or primary processor.

For errors other than those numbered 30 through 37, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: ERROR *0011* Checkopen Failure: errnum

Cause A CHECKOPEN operation failed. errnum is the file-system error number.

Effect Errors 30 through 37 indicate a resource-allocation failure and might indicate that the primary and/or backup name manager’s processor is overloaded.

The backup name manager process stops. The system tries to create a new backup process after a 30-second delay. If a new backup process is created, the system displays DNS operator message 16.

Recovery For errors 30 through 37, decrease the load on the processor. For errors other than those numbered 30 through 37, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

\system.manager: ERROR *0012* Unable to Create Backup Process, PROCESS_CREATE_ Error err: detail

Cause A name manager process encountered PROCESS_CREATE_ error err while trying to create a backup process.

Effect If the PROCESS_CREATE_ error indicates that the backup processor is down, the name manager tries to create a new backup process 30 seconds after it receives a CPU up system message from the backup processor.

For errors other than CPU down, the primary name manager delays for 30 seconds and retries. If the retry fails, the name manager delays 60 seconds and retries again. This process continues (the delay increasing by 30 seconds at each failure) until the delay reaches five minutes. Thereafter, the primary name manager attempts to create a new backup every five minutes.

The primary name manager issues this message only when its initial attempt to create a backup fails; unsuccessful retries are not reported.

Recovery Refer to Appendix D, for summary information about the specified error. Refer to the Guardian Procedure Errors and Messages Manual for more detail.

mgr-proc: WARNING *0013* Backup Deleted

Cause A name manager’s backup processor failed.

Effect The primary name manager process tries to create a backup 30 seconds after it receives a CPU up system message from its backup processor.

Recovery Follow the recommended recovery procedure for a processor failure. If the processor will be down indefinitely, stop DNS, change the DNS-manager processors to a pair of running processors, and then restart DNS.

mgr-proc: ERROR *0014* Backup Process ABENDed

Cause A name manager’s backup process terminated abnormally.

Effect The primary name manager process tries to create a new backup after a 30-second delay.

Recovery Although the name manager has created a new backup, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: WARNING *0015* Takeover by Backup Process, cause

Cause A name manager process generates this message after takeover by the backup name manager process.

Effect Unless the takeover occurred as a result of a processor failure, the new primary process attempts to create a new backup after a 30-second delay.

If a processor failed, the new primary process creates a new backup 30 seconds after it receives a CPU up system message.

Recovery If the cause is “Primary Abended,” investigate the event log to determine why the primary process abended.

mgr-proc: STATUS *0016* Backup Created in CPU cpu

Cause A name manager process successfully created a backup process.

Effect The process runs.

Recovery Informational message only; no corrective action is needed.

mgr-proc: FATAL *0017* Unable to RESYNC File filename, Error errnum

Cause A name manager process encountered a file-system I/O error on a call to RESETSYNC after takeover by the backup name manager process. Resource-allocation failures (file-system errors 30 through 37) may indicate that the name manager’s backup processor is overloaded.

Effect The name manager stops.

Recovery Restart DNS. For errors other than those numbered 30 through 37, ask the Global Mission Critical Solution Center (GMCSC), because the name manager may have internal logic problems.

When contacting the Global Mission Critical Solution Center (GMCSC), provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: WARNING *0018* Communications lost with System system-name

Cause A name manager process received a MONITORNET system message. The MONITORNET message indicates that no processors are accessible in the specified system and that the name manager has requesters running on the system.

Effect Requesters on the indicated system may receive file-system error 248 or 249 if they have current WRITEREADs outstanding to the name manager. Requesters that issue WRITEREADs after communications have been restored receive file-system error 60; they should close and reopen the name manager.

Recovery Carry out corrective action as required by the accompanying Expand messages. Refer to Appendix B, for information on file-system errors.

DNSCOM-process-descriptor: STATUS *0019* config-file Initialized by group,user

Cause DNS has been successfully initialized.

Effect A new DNS database was created.

Recovery Informational message only; no corrective action is needed.

{mgr-proc | exp-proc}: {ERROR | FATAL} *0020* File I/0 Error on filename, Error errnum

Cause File-system error errnum occurred on file filename.

Effect Data may be lost.

This error is fatal in the following cases:

The I/O error occurred on the DNS configuration file ($SYSTEM.SYSTEM.DNSCONF) during name manager or name exporter startup.
The I/O error occurred on the DNS-QUEUE-FILE during name exporter startup.
The I/O error occurred when the name exporter opened the name manager.

Recovery Refer to Appendix B, for information on the specified file-system error. Correct the error condition.

{mgr-proc | exp-proc}: {ERROR | FATAL} *0021* File Open Error on filename, Error errnum

Cause A name manager or name exporter process received file-system error errnum when opening file filename.

Effect An important DNS function may be lost.

This error is fatal in the following cases:

The I/O error occurred on the DNS configuration file ($SYSTEM.SYSTEM.DNSCONF) during name manager or name exporter startup.
The I/O error occurred on the DNS-QUEUE-FILE during name exporter startup.
The I/O error occurred on the TFILE (usually $TMP) during name exporter startup.
The I/O error occurred when a name exporter opened a name manager.

Recovery Refer to Appendix B, for information on the specified file-system error. Correct the error condition.

{ mgr-proc | exp-proc}: ERROR *0022* Replication of name { to | from } system Failed DNSTYPE: dnstype TYPENAME: type-name

Cause A name manager or name exporter process generates this message when an attempt to replicate a name’s definition fails because of one of the following:

The name’s type (ALIASTYPE or COMPOSITETYPE) is not defined to the importing system.
The name’s type (ALIASTYPE or COMPOSITETYPE) has incompatible definitions on the exporting and importing systems.
The SSTYPE of the name’s REFERENT or one of its COMPONENTs is not defined to the importing system.
The SSTYPE of the name’s REFERENT or one of its COMPONENTs has incompatible definitions on the exporting and importing systems.

Effect The specified name is not replicated to or from the system named in the message.

Recovery If type-name is simply not defined on the importing system, use DNSCOM to add the name.

Once type-name is added, simply enable export to the importing system at the exporting system using the DNSCOM ENABLE EXPORT command.

Refer to the Distributed Name Service (DNS) Management and Operations Manual for information on adding and changing names and for details about the ENABLE EXPORT command.

If type-name has incompatible definitions on the importing and exporting systems, you must perform a logical reload of one of the systems. Refer to the Distributed Name Service (DNS) Management and Operations Manual for information on performing a logical reload.

mgr-proc: STATUS *0023* Import Request from system-name Rejected

Cause A name manager process received a process open message from a remote name exporter process and ALLOWIMPORTS is configured as FALSE.

Effect The message is issued periodically until the problem is resolved.

Recovery If you want all names to be imported, execute the following DNSCOM commands:

STOP DNS, WAIT ON
ALTER DNS, ALLOWIMPORTS ON
START DNS

{mgr-proc | exp-proc}: ERROR *0024* Database Error nnn at %codeseg.P-reg Logical File: name File: filename Key1: high-order-key, Key2: low-order-key

Cause A name manager or name exporter process detected an inconsistency in the DNS database.

Effect The current operation is aborted. If the name exporter reports the error, the operation is retried after a delay of at least one minute.

Recovery Perform a logical reload. Refer to the Distributed Name Service (DNS) Management and Operations Manual for information on performing a logical reload. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Copy of the corrupt database
Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

{mgr-proc | exp-proc}: FATAL *0025* INTERNAL ERROR at %code-seg.P-reg

Cause A name manager or name exporter process detected an unrecoverable internal error. The program reporting the error has a logic problem.

Effect There is a loss of subsystem integrity.

Recovery You can try to use DNS. Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: FATAL *0026* DNSMGR (version) Incompatible with Database (version)

Cause A name manager process is incompatible with the version level at which the DNS database was last initialized.

Effect An obsolete code file has probably been specified as the DNS-MANAGER PROGRAM.

An emergency shutdown of DNS starts.

Recovery Verify that the code file is correct. If the file is correct, the DNS configuration file may be corrupted. You can rebuild the configuration file using the DNSCONFONLY option of the INITIALIZE DNS command.

mgr-proc: FATAL *0027* DNSEXP (exp-version) Incompatible with DNSMGR (mgr-version)

Cause The name manager version is incompatible with the name exporter version.

Effect An emergency shutdown of DNS starts.

Recovery Install the correct version of the DNS software.

system.manager: ERROR *0028* Unable to Start exp-proc, PROCESS_CREATE_ Error err:detail

Cause A name manager process received PROCESS_CREATE_ error err while attempting to start the name exporter process.

Effect The name manager tries to restart the name exporter every 30 seconds. If a subsequent attempt fails with the same error, no additional message is issued. If a retry is successful, the name exporter issues a startup message.

Recovery Refer to Appendix D, for information about the specified error.

mgr-proc: ERROR *0029* exp-proc ABEND

Cause A name manager process received an ABEND system message that references a name exporter process.

Effect The name manager attempts to restart the name exporter after a 30-second delay.

Recovery Contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: ERROR *0030* exp-proc Deleted

Cause A name manager process received a CPU down system message that references the name exporter processor.

Effect The name manager tries to create a new exp-proc process first in the primary and then in the backup DNS-EXPORTER processor.

Recovery No corrective action is needed unless both the primary and backup processors are likely to be unavailable for an extended time. If so, stop DNS and use the command ALTER DNS-EXPORTER, CPUS (new-primary, new-backup) to change the primary or backup exporter processors to available processors.

{mgr-proc | exp-proc}: FATAL *0031* TRAP #nn, %code-seg.P-reg

Cause A name manager or name exporter process suffered from a hardware-related or software-related trap.

Effect The process stops executing.

Recovery Contact the Global NonStop Solution Center (GNSC) if trap is one of the following:

0	Illegal address
1	Instruction failed
2	Arithmetic overflow
3	Stack overflow
4	Loop timer

When contacting the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

{mgr-proc | exp-proc}: FATAL *0032* SEGMENT_ALLOCATE_ Failure nnn:detail, Volume volume

Cause A name manager or name exporter process cannot allocate its extended data segment.

Effect The process stops executing.

Recovery Refer to Appendix F or the Guardian Procedure Errors and Messages Manual for recovery information for the SEGMENT_ALLOCATE_ error.

mgr-proc: FATAL *0033* DNS NOT INITIALIZED

Cause The DNS configuration file specified as the name manager process’s IN file does not exist.

Effect A name manager cannot proceed without the configuration file.

Recovery Create the DNS configuration file using the INITIALIZE DNS command in DNSCOM.

exp-proc: WARNING *0034* BEGINTRANSACTION Error errnum

Cause An error occurred on a call to BEGINTRANSACTION.

Effect The message is generated periodically until the problem is resolved.

Recovery If the specified error is error 82, indicating that transaction processing is disabled, refer to the NonStop TM/MP Reference Manual for corrective action. Otherwise, contact the Global Mission Critical Solution Center (GMCSC). Debug the name exporter with the Inspect debugger and create a SAVE file to accompany the report.

When contacting your Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.

mgr-proc: STATUS *0035* Initial Import from system-name is Complete

Cause A name manager process received its first import request from another node in the network.

Effect The task executes.

Recovery Informational message only; no corrective action is needed.

{mgr-proc | exp-proc}: {ERROR | FATAL} *0036* Invalid logical-filename - GUARDIAN90-filename

Cause While opening a DNS database file or the DNS configuration file, a name exporter or name manager process detected an error. One of the following may be incorrect:

File code. The DNS configuration file must have file code 849. DNS database files must have file code 850.
Device type. The file must be a disk file.
File type. The file must be key-sequenced.
Key offset and length. The file must have key offset 0. The key length varies by file.
Record length. The maximum record length must be greater than or equal to the longest record that can be stored in the file.

Effect If this error occurs during an attempt to start DNS, DNS does not start. If this error occurs during an attempt to open a database, the file is not opened.

If the configuration file is incorrect, the process issuing the event abends.

Recovery If the configuration file is incorrect, rebuild it by issuing the INITIALIZE DNS, DNSCONFONLY command.

If the database file is incorrect, replace it using the File Utility Program (FUP) or correct the file reference by issuing the ALTER DNSFILE command.

process-name: STATUS *0037* Export to System { \system | * } { Enabled | Disabled } or process-name: ERROR *0037* Export to System \system Disabled

For STATUS message:

Cause An ENABLE or DISABLE export DNSCOM command has been executed.

Effect Exporting of names to the indicated system has been enabled or disabled.

Recovery Informational message only; no corrective action is needed.

For ERROR message:

Cause An export error has occurred to the indicated system.

Effect Export to the indicated system is disabled until the cause of the error is corrected and export is re‑enabled using the ENABLE EXPORT command in DNSCOM.

Recovery This message is preceded by DNS message 38. Follow the recovery procedure for that message, and then issue an ENABLE EXPORT command using DNSCOM.

process-name: ERROR *0038* {Add | Alter | Delete} Failure at \system, Name: name, Err: error

Cause An unexpected error occurred when an attempt was made to add, alter, or delete a name definition at the specified remote system.

Effect The add, alter, or delete operation failed. Export to the remote system is disabled and DNS message 37 is issued.

Recovery DNS errors are described in the Distributed Name Service (DNS) Management Programming Manual.

Check the importing system to see whether a DNS name manager process is issuing error messages; if so, correct the situation and issue an ENABLE EXPORT command to re‑enable export.

If the importing system appears normal, contact the Global NonStop Solution Center (GNSC) and provide all relevant information as follows:

Descriptions of the problem and accompanying symptoms
Details from the message or messages generated
Supporting documentation such as Event Management Service (EMS) logs, trace files, and a processor dump, if applicable

If your local operating procedures require contacting the Global Mission Critical Solution Center (GMCSC), supply your system number and the numbers and versions of all related products as well.