Chapter 26 DSC (NonStop Kernel Configuration Services) Messages

Cause  A software or hardware fault prevented the Configuration Utility Process ($ZCNF) from launching $ZPM.

This could occur either at coldload or during normal functioning of the system. The process launch errors reported in the event log indicate the reason for failure.

Effect  If a coldload is in progress, $ZCNF will halt the processor with %7703 halt code; otherwise $ZCNF will retry up to three times. If it still fails to start $ZPM, $ZCNF will wait for 10 minutes before attempting to restart $ZPM again.

Recovery  $ZCNF attempts to restart $ZPM at regular intervals, and once $ZPM is started, a corresponding EMS event is logged. But if this doesn’t happen or a processor halt occurs during coldload, contact your service provider and provide the following information:

Cause  $ZPM stopped for some reason, and $ZCNF received a process death message for $ZPM. $ZPM might have abended, or a user might have stopped it manually.

Effect  If a coldload is in progress, $ZCNF will halt the processor with %7703 halt code; otherwise $ZCNF will restart $ZPM.

Recovery  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. If the error persists, or in case of a coldload and a processor halt, contact your service provider and provide the following information:

Cause  The configuration utility process ($ZCNF) attempted to start $ZPM three times in the last 10 minutes.

Effect  $ZCNF will wait 10 minutes, then attempt to start $ZPM again.

Recovery  If the error persists, contact your service provider and provide the following information:

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.

Cause  $ZCNF has waited for 10 minutes and is attempting to restart $ZPM. If this attempt fails, $ZCNF will attempt to restart $ZPM again after another 10 minutes.

Effect  $ZCNF is attempting to restart $ZPM.

Recovery  No recovery is needed. However, if, after this event, event numbers 1024 through 1026 are generated and they persist, contact your service provider and provide the following information

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.

Cause  $ZCNF received a CRU deletion event from the service processor via the Maintenance IO Process (MIOP) for a CRU that is not present in the $ZCNF hardware configuration tables.

The most likely cause of CRU information not being present in the hardware tables is that certain events were dropped at coldload time. The events might have been dropped because they were stamped with a time that preceded the coldload time; hence, the events were considered stale. The missing CRU information could also be caused by some other SP-MIOP-Config problem that resulted in the information not being communicated to $ZCNF.

Effect  $ZCNF will not update its hardware configuration table for this event. However, it will send the event to the registrants of this CRU deletion event.

Recovery  Contact your service provider and provide the following information:

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.

Cause  After $ZCNF received a CRU Insertion or TNet CRU Configured event, it tried to add CRU information to the Physical CRU Table (PCT) or the TNet Node Table (TNT) respectively, but found that the tables were full.

Effect  The CRU information does not get stored into the PCT or TNT and, therefore, is unavailable for later queries.

Recovery  Contact your service provider and provide the following information:

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.

Cause  This event occurs whenever $ZCNF receives incorrect or inconsistent information in event packets received from MIOP. The incorrect information could be one of:

Effect  If the event packet for which $ZCNF generated a bad maintenance event contains any events for which there are registered clients, the clients will not be able to receive the registered events.

Recovery  This problem could be caused by a miscommunication between SP, MIOP and ZCNF. Contact your service provider and provide the following information:

Cause  $ZCNF received a CRU configured event from the service processor for a CRU whose entry was not found in the Physical CRU Table.

Effect  No CRU information will be sent to registrants of this event.

Recovery  Check for any previous CRU deletion events from the service processor (SP). If an event is found, it means that either the SP sent a CRU configured event for a CRU that was deleted, or a CRU insertion event was not received after the CRU was deleted and before the CRU was configured. If no CRU deletion event is found but a CRU insertion event is found, $ZCNF’s PCT is not updated. In either case, contact your service provider and provide the following information:

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.

Cause  $ZCNF received a TNet CRU configured event from the service processor (SP) for a CRU whose entry was not found in the Physical CRU Table.

Effect  No entry will be made for this TNet CRU in the TNet node table by $ZCNF and hence no information about it will be returned.

Recovery  Check for any previous CRU deletion events from SP. If an event is found, it means that either the service processor (SP) sent a CRU configured for a CRU that was deleted, or a CRU insertion event was not received after the CRU was deleted and before CRU was configured. If no CRU deletion event is found but there is a CRU insertion event, $ZCNF’s PCT is not updated. In either case, contact your service provider and provide the following information:

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.

Cause  Service processor (SP) events delivered to $ZCNF are not in sync with the sequence number that $ZCNF was expecting according to its internal tables.

Effect  Since the sequence numbers did not match, some events might have been lost. $ZCNF will set its tracking array for sequence numbers according to what was received from SP and will continue processing.

Recovery  This is an informational message only; no recovery is required.

Cause  During coldload, the operator specified that a saved configuration file was to be used in place of the current CONFIG file (configuration database) for coldloading the system.

Effect  The CONFIG file in use before this event got generated is renamed to CONFSAVE and the new CONFIG file is the saved configuration file (CONFnnnn) as specified in the event.

Recovery  This is an informational message only; no recovery is required.

Cause  A system coldload was done using the CONFBASE file, or the CONFIG file is not present in $SYSTEM.ZSYSCONF.

Effect  The system will start up with the configuration recorded in CONFBASE file. It will be a “bare minimum” system and will not have the configuration that it had prior to the current coldload.

Recovery  This is an informational message only; no recovery is required. If you do not want a “bare minimum” system, you must coldload a system by specifying the CONFIG file instead of CONFBASE.

Cause  The CONFIG file was successfully opened and is serving as the system’s configuration database.

Effect  None.

Recovery  None required. This is an informational message that is issued whenever a system is coldloaded. The message indicates a successful open of the CONFIG file by the configuration database manager ($ZCDB).

Cause  An SCF SAVE CONFIGURATION command was used or the CONFIG file was saved to CONFSAVE by $ZCDB during its processing. $ZCDB always saves the current configuration file into CONFSAVE when the system is coldloaded.

Effect  The current configuration has been saved into either CONFnnnn or CONFSAVE.

Recovery  This is an informational message only; no recovery is required.

Cause  The configuration database manager ($ZCDB) was trying to read records from the configuration database as specified by the client, but encountered an error other than FEEOF and FEOK.

Effect  The records read before this event occurred are returned to the client but no further records are read. The event contains information about the last record read.

Recovery  The error returned in the event is a file system error; it determines what recovery procedures to follow. If the error persists, contact your service provider and provide the following information:

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.

Cause  The request to insert a record into the configuration database failed because the configuration database manager ($ZCDB) encountered an error other than FEOK and FEDUP while trying to write to the file.

Effect  The record indicated in the event is not inserted into the configuration database.

Recovery  The error returned in the event is a file system error; it determines what recovery action is necessary. If the error persists, contact your service provider and provide the following information:

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.

Cause  While $ZCDB was trying to insert or delete a record in the configuration database, it found that the configuration database file was locked by a locker, but the locker had died. This event can also occur when $ZCDB receives a request for locking the file and finds that the current lock owner does not exist.

Effect  An attempt to insert, delete, or obtain a lock for the configuration database will succeed because the previous locker is no longer there. The previous owner’s process descriptor is displayed in the event.

Recovery  This is an informational message only; no recovery is required.

Cause  This is a general purpose event that is used to display any file system error received during normal functioning of configuration services.

Effect  The event description provides a file system procedure number (as defined in $SYSTEM.ZSPIDEF.ZFILC), the error that was returned from this procedure, and the file number. Use this information to determine what went wrong and what effect can be expected.

Recovery  If the error persists, contact your service provider and provide the following information:

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.

Cause  The file name that was specified in the event is not a key-sequenced file, or a KEYPOSITIONX call on the file failed with the error indicated in the event.

Effect  Since these events are usually concerned with processing of the configuration database, they could lead to the indicated configuration file either not being opened or not being copied to a temporary file. Either of these scenarios will eventually lead to a halt of the processor in which the Configuration Database Manager ($ZCDB) process is running.

This event is also generated when $ZCDB attempts to locate the record for a configured adapter in the configuration database. In this case, the error is returned from the $ZCDB process to the requester that requested information about the configured adapter in a specific group, module, and slot. You may also see errors from other subsystems noting the error returned by $ZCDB.

Recovery  Use a FUP INFORMATION command to make sure that the configuration database file currently in use is a key-sequenced file.

If the configuration database file is not key-sequenced, copy CONFSAVE to a file such as CONFnnnn where nnnn is a four-digit number indicating the configuration version to be saved. Use this CONFnnnn file to coldload the system by specifying nn.nn as the saved config version during coldload.

If the configuration file is a key-sequenced file and this error persists, contact your service provider and provide the following information:

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.

Cause  The file name specified in the event is a configuration database file, but it does not have 837 as its filecode.

Effect  Since these events are usually concerned with processing of the configuration database, they could lead to the specified configuration either not being opened or not being copied to a temporary file. Both of these scenarios will eventually lead to a halt of the processor in which the Configuration Database Manager ($ZCDB) process is running.

Recovery  Change the file code of the configuration database file to 837.

Cause  The configuration database process ($ZCDB) failed to create a temporary file name.

Effect  Since the creation of a temporary file is required for processing the configuration database, this event means that eventually $ZCDB will halt the processor in which it is running.

Recovery  If the file name indicated in the event already exists, determine the openers of the file and provide this information to your service provider along with the following information:

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.

Cause  An attempt was made to purge the file name given in the event, but when the purge failed the file was renamed.

Effect  Either the CONFSAVE file is purged or the CONFSAVE file is renamed to the file name indicated in the event

This occurs as part of normal processing and is not considered an error event. The current CONFIG file is renamed to CONFSAVE.

Recovery  This is an informational message only; no recovery is required.

Cause  An internal file error occurred.

Effect  The Configuration Database Manager ($ZCDB) is unable to read information from configuration database file. You might also receive errors from other subsystems noting the error returned by $ZCDB.

Recovery   If this error persists, contact your service provider and provide the following information:

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.

Cause  The Configuration Database Manager ($ZCDB) encountered a file system error while converting the old style shared adapter records to the new style shared adapter records.

Effect  The conversion from the old style shared adapter name to the new style shared adapter name will not take place. You might also receive errors from other subsystems noting the error returned by $ZCDB.

Recovery  The error returned in the event is a file system error; it determines what recovery action is required. If the error persists, contact your service provider and provide the following information:

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.

Cause  While the Configuration Database Manager ($ZCDB) was trying to update shared adapter records as part of the conversion of old style records to new style, it found an adapter record that was not shared but was preceded by or followed by an adapter with the same Group Module Slot (GMS) entry.

Effect  This is a warning message. Removal of this adapter record would unset a bit that indicated the adapter being configured. You might also receive errors or warnings from other subsystems noting that the adapter was not configured.

Recovery  This is an informational message only; no recovery is required.

Cause  The Configuration Utility process ($ZCNF) received one or more SP hardware events from the service processor that were timestamped before the coldload time. Either the system time was rolled back or stale events were received.

Effect  If $ZCNF has received at least one good event (one timestamped after coldload), this event is just a warning message. If $ZCNF has not received any good events, these events are stale and will be dropped.

Recovery  This is an informational/warning message and occurs at least once during coldload. If more occurrences of this event are noted, it could indicate some other problem in the SP, MIOP, or DSC subsystem. Contact your service provider and provide the following information:

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.

Cause  The Configuration Utility process ($ZCNF) failed to launch the Configuration Database Manager ($ZCDB).

Effect  Since $ZCDB is critical for system functioning, $ZCNF will halt the processor on which it is running.

Recovery  The information contained in the event will indicate the error received from PROCESS_LAUNCH_. Contact your service provider and provide the following information:

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.

Cause  The Configuration Utility process ($ZCNF), received a process death message for the Configuration Database Manager ($ZCDB).

Effect  If this happens during coldload, $ZCNF will halt the processor in which it is running. If this happens at times other than during coldload, $ZCNF will attempt to restart $ZCDB.

Recovery  Contact your service provider and provide the following information:

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.

Cause  The Configuration Utility process ($ZCNF) attempted to restart $ZCDB three times in the last 10 minutes.

Effect  ZCDB is critical for system functioning; therefore, if it has already passed its restart threshold, $ZCNF will not attempt to restart it again and $ZCNF will halt.

Recovery  Contact your service provider and provide the following information:

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.

Cause  The persistence manager ($ZPM) successfully launched the coldload TACL or started a generic process for the first time.

Effect  This is an informational message indicating that a process was started in a CPU.

Recovery  This is an informational message only; no recovery is required.

Cause  The persistence manager ($ZPM) restarted a generic process that was killed, possibly by a user or because of an abend or CPU diver. If the process died due to CPU diver, this event occurs in the CPU being reloaded, as $ZPM restarts the process in that CPU.

Effect  This is an informational message. The indicated process is started in the indicated CPU.

Recovery  This is an informational message only; no recovery is required.

Cause  During it's initialization phase, the persistence manager ($ZPM) received an error while trying to reserve a process name in the Destination Control Table (DCT).

Effect  The process name is not reserved in the DCT and is therefore available for use.

Recovery  Contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) received a process death message for a generic process that was marked as a persistent process. The process death message was delivered because either the process was stopped by a user or the CPU (on which the process was running) was divered.

Effect  Any applications that depend on this persistent process might either fail or produce delayed responses. Note that all subsystem managers are also marked as persistent; if this event is received for a subsystem, the process will be restarted by $ZPM if it has not already exceeded its restart limit (as specified by the AUTORESTART attribute). If the process has exceeded its restart limit, $ZPM will wait for 10 minutes before attempting additional restarts.

Recovery  No recovery is needed. $ZPM will restart the process. However, you should determine why the process stopped and take action to avoid future stoppages.

Cause  The persistence manager ($ZPM) received a process death message for a generic process that was marked as a persistent process. The process death message was delivered because the process abended for some reason.

Effect  Any applications that depend on this persistent process might either fail or produce delayed responses. Note that all subsystem managers are also marked as persistent; if this event is received for a subsystem, the process will be restarted by $ZPM if it has not already exceeded its restart limit (as specified by the AUTORESTART attribute). If the process has exceeded its restart limit, $ZPM will wait for 10 minutes before attempting additional restarts.

Recovery  Although the process is restarted, it might not keep running. Contact your service provider and provide the following information:

This will ensure that any problem in the product that owns the process is recognized.

Cause  The persistence manager ($ZPM) received a process death message for a generic process that was not marked as a persistent process. The process death message was delivered because the process abended for some reason.

Effect  Since this is not a persistent process, $ZPM will not attempt to restart it. If any applications depend on this process, they will fail since the process is no longer available.

Recovery  Contact your service provider and provide the following information:

This will ensure that any problem in the product that owns the process is recognized.

Cause  The persistence manager ($ZPM) was unable to launch the process named in the event.

Effect  The indicated process is not launched. If the process is coldload TACL, $ZPM abends. If it is any other process, $ZPM attempts to launch the process on another CPU if the CPU is available and the process was configured to run on that CPU.

If the process is a subsystem manager process, applications or other processes that were configured to run through that subsystem will fail.

If the process was the $IMON process, a process will not be able to go into INSPECT.

Recovery  Check the error returned in the event for a PROCESS_LAUNCH_. If recovery action still cannot be determined, contact your service provider and provide the following information:

Cause  While trying to restart a persistent process, the persistence manager ($ZPM) found that it had already attempted the maximum number of restarts allowed for the process (determined by the AUTORESTART attribute) in the last 10 minutes.

Effect  $ZPM will delay any future attempts to restart the process for 10 minutes. The process will therefore not be available for at least another 10 minutes.

Recovery  None required since $ZPM restarts the process after 10 minutes. However, if this problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) encountered a critical internal error and is abending.

Effect  The Configuration Utility process ($ZCNF) will restart $ZPM; however, any applications that depend directly or indirectly on $ZPM might fail or experience a response delay.

Recovery  Although $ZCNF restarts $ZPM, the cause of the abend should be determined. Contact your service provider and provide the following information:

Cause  During reload of a CPU, the persistence manager ($ZPM) encountered an error while trying to execute the checkin protocol with the subsystem manager process indicated in the event text.

Effect  The subsystem manager process does not know that a CPU has been reloaded. All processes that were supposed to run on the reloaded CPU and are managed by the subsystem manager for which checkin failed will not be launched. This could lead to application failures.

Recovery  The error number in the event indicates why the checkin failed. Once the cause is determined, divering the CPU and reloading it should result in a successful checkin. If the problem persists, please contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) encountered a critical internal error during its operation. This might be followed by an abend.

Effect  The event text names the procedure where the internal error occurred. If it happened during a reload, the reload process might not complete, resulting in $ZPM not being able to start all processes that are dependent on $ZPM. Also, checkin protocols with subsystem managers might not get executed. If the internal error occurs when $ZPM is trying to process a PROCDEATH message from a process, $ZPM will not attempt to restart the process.

In other cases, $ZPM either abends or does not complete its processing, in which case $ZPM will be unable to manage some of the persistent processes.

Recovery  Recovery action depends on information returned by the event. If appropriate recovery action cannot be determined, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) encountered an error when retrieving a reserved name record while it was trying to sort its internal list of reserved names as per processes that contain a multi-name.

Effect  The record that $ZPM was trying to reserve is discarded and its entry is not reserved in the DCT (destination control table). This could result in failures when an application tries to access the DCT for this record or obtain information about this record.

Recovery  Contact your service provider and provide the following information:

Cause  While processing a generic process record, the persistence manager ($ZPM) found that either the startup CPU or the stop mode was incorrectly specified in the record. The event indicates which procedure encountered the error and which process record had the incorrect value. The last part of the event indicates whether it was an incorrect CPU or stop mode.

Effect  The indicated procedure is not properly started or is aborted by $ZPM.

Recovery  Determine how the procedure was configured through the KERNEL subsystem ($ZZKRN) and ensure that valid startup CPU and stop mode are specified. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) successfully configured an alternate swap file for the coldload TACL. The event provides information about the file that is being used as the swap file for the coldload TACL.

Effect  This is an informational message. The first file name in the message text is the original swap file name and the second file name indicates the swap file currently in use.

Recovery  This is an informational message only; no recovery is required.

Cause  The persistence manager ($ZPM) launched the coldload TACL but failed while attempting to open the coldload TACL to write a startup message.

Effect  Since this is the coldload TACL for which an open failed, $ZPM will abend.

Recovery  Recovery action depends on the error and error detail values given in the event message. Contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) attempted the maximum restarts possible for the process named in the event, but was not able execute a 10 minute delay before process restart was attempted again.

Effect  $ZPM will not restart the process.

Recovery  Check to determine why the process is not able to restart. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) failed to open the process named in the event message, and was unable to send the startup message.

Effect  Although the process was created by $ZPM, it might not function properly due to failure of the open attempt.

Recovery  Use the error value indicated in the event message to determine the recovery action. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) was unable to write the startup message to the process named in the event message.

Effect  Although the process was created by $ZPM, it might not function properly since $ZPM had problems communicating with it.

Recovery  Use the error value given in the event message to determine recovery action. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) failed to open the process named in the event message and was therefore unable to write the SPI STOP command to the process.

Effect  The process will not be stopped and might not function properly.

Recovery  Use the error value given in the event message to determine the recovery action. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) was unable to send assign messages to the process named in the event message.

Effect  The process might not function properly.

Recovery  Use the error value indicated in the event message to determine the recovery action. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) was unable to send param messages to the process named in the event message.

Effect  The process might not function properly.

Recovery  Use the error value given in the event message to determine the recovery action. If the problem persists, contact your service provider and provide the following information:

Cause  The persistence manager ($ZPM) was unable to copy all defines intended for the indicated process into a buffer that was to be passed to the process.

Effect  The process will not receive all defines and might not function properly.

Recovery  Contact your service provider and provide the following:

Cause  The backup for the Reliable Home Terminal process ($ZHOME) was created in the indicated CPU.

Effect  None; this is an informational message.

Recovery  This is an informational message only; no recovery is required.

Cause  The primary process for $ZHOME died and the backup process has taken over.

Effect  None; this is an informational message.

Recovery  This is an informational message only; no recovery is required.

Cause  The Reliable Home Terminal process ($ZHOME) failed to either open or write to a file. The file is either $0 or the output file for $ZHOME as specified in the $ZHOME startup message.

Effect  $ZHOME might be unable to display or receive messages from clients (processes with their term specified as $ZHOME).

Recovery  Use the error number and file name given in the event to determine appropriate recovery action.

Cause  The Reliable Home Terminal process ($ZHOME) wrote to or opened a file.

Effect  None; this is an informational message indicating that $ZHOME successfully communicated with a file and that the file is now being used.

Recovery  This is an informational message only; no recovery is required.

Cause  The Reliable Home Terminal process ($ZHOME) encountered an internal error. The cause might be a failure of one of the following $ZHOME functions:

Effect  Depends on which $ZHOME activity failed.

Recovery  Since this is a $ZHOME internal error, contact your service provider and provide the following information: