Chapter 15 COM‑KRNL (Common) Messages

Cause  The specified object switched processors in response to a command, a software failure, or a hardware failure.

Effect  The object runs in the new processor.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified object switched to an alternate path. The switch was in response to a programmatic command, software failure, or hardware failure.

Effect  The object uses the new path.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified object reported a new summary state. The change may have been in response to a programmatic command, software failure, or hardware failure.

Effect  The object reports the new summary state.

Recovery  Informational message only; no corrective action is needed.

Cause  The I/O process encountered a fatal I/O error. The cause may be incorrect or inconsistent configuration information that cannot be corrected through the Subsystem Control Facility (SCF) or the Communications Management Interface (CMI), or insufficient resources to support the specified configuration.

Effect  The I/O process stops. See the appropriate subsystem management programming manual for details.

Recovery  Correct the specific cause of the error.

Cause  Take ownership execute I/Os are normally issued during controller initialization but may also be issued to switch the IOC path, and thus the I/O process and processor, in order to lock out an overloaded or malfunctioning path.

Effect  The specified processor now owns the port.

Recovery  Scan the log for earlier messages referring to the same device. If an earlier operator message indicates that the operator message -10001 was generated because the device was recently started or because of an operator request, no action is required. If previous operator messages indicate a hardware or software fault on the device, those operator messages should indicate the response. If the same operator messages persist after operator message -10001 is issued, the fault is probably in the controller and not in the associated processor.

Cause  Some condition required that the controller be reinitialized. The controller may have lost the context within which it was communicating with an associated I/O process, or it may have had a nonrecoverable software error.

Effect  The controller is reinitialized.

Recovery  Examine the log for other messages concerning the device. Look both before and after operator message -10002. If operator messages related to the device are markedly different before and after operator message -10002, the problem was probably caused by software and has been cleared up by the reset. If operator messages indicate that the errors continue after the reset, hardware is probably the source of the problem.

Cause  The I/O process or driver associated with the controller has detected a power-on interrupt.

Effect  The controller was powered on at the time indicated.

Recovery  Informational message only; no corrective action is needed.

Cause  An execute I/O (LAC) command was issued to the controller, but the corresponding interrogate I/O (IIO) did not occur within the channel time-out period. The channel or the controller is faulty.

Effect  Communication through this channel or controller may be impaired.

Recovery  Scan the log for other error messages about the corresponding processor and I/O channel. If no processor-related messages appear, the problem is most likely with the controller (unless there are no other controllers primaried to this processor channel).

Cause  The I/O process has detected an unexpected interrupt from the controller. The channel or controller detected a fault.

Effect  Communication through this channel or controller may be impaired.

Recovery  Examine the interrupt word in the error message to determine the cause of the interrupt.

Cause  The controller has been replaced and powered up, or the controller has been reset following a failure.

Effect  If the message contains no error information, the controller now contains a fresh copy of its microcode.

Recovery  If the message contains an error number, it indicates the cause of the failure. Verify that the microcode file is present and properly secured. Check the versions of the microcode and the downloading process. If the version numbers do not match, upgrade the older software.

Cause  No startup message was received upon process initiation. The Kernel assumes that the Kernel-based process initiator adheres to the command interpretor startup logic. Thus, this event reveals that a file-close was detected with no startup message.

Effect  The process terminates.

Recovery  Resend the file open with a startup message following it.

Cause  The process is monitoring whether the input message queue might overflow under worst-case conditions.

Effect  If the process appears to be in a stressed condition, certain kinds of failures could result in the process incorrectly tracking the openers. The server might believe that there are opens when there are none.

Recovery  To eliminate the stressed condition, reduce the declared nowait depth of the openers, or reduce the number of openers, or both. If the error occurs the first time the subsystem is brought up or occurs repeatedly, contact your application developer or HP representative and provide all relevant information as follows:

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 trace file stops collecting data.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  A trace file has been opened on a subsystem that supports fast tracing.

Effect  None.

Recovery  Informational message only; no corrective action is needed.

Cause  The Common Kernel detects errors in the SPI response from a server.

Effect  The Common Kernel process attempting to communicate with another server using the SPI protocol encountered a problem in analyzing the response.

Recovery  The recovery depends on the application. For detailed recovery actions, see that application’s manual.

Cause  Messages filled the specified object’s system buffer faster than the object could read them from $RECEIVE. This can happen when a high priority process dominates the processor or when the object is waiting on a long-outstanding waited request.

Effect  The object may no longer have accurate knowledge of its environment. (It may be unaware, for example, that an opener’s processor has failed.)

Recovery  See the subsystem management programming manual. The object may need to be restarted.

Cause  Message collection for alternate collector 3 has been switched to a new collector process in response to an interactive or programmatic request.

Effect  This message is sent to the old collector. The related operator message -32715 and subsequent operator messages are sent to the new collector.

Recovery  Informational message only; no corrective action is needed.

Cause  Message collection for alternate collector 3 has been switched from the previous collector process in response to an interactive or programmatic request.

Effect  This message and subsequent operator messages are sent to the new collector. The related operator message -32714 is sent to the previous collector.

Recovery  Informational message only; no corrective action is needed.

Cause  Message recording on collector 3 has been stopped in response to an interactive or programmatic request.

Effect  No further messages are recorded by alternate collector 3.

Recovery  Informational message only; no corrective action is needed.

Cause  Event collection for alternate collector 2 has been switched to a new collector process in response to an interactive or programmatic request.

Effect  This message is sent to the old collector. The related operator message -32718 and subsequent operator messages are sent to the new collector.

Recovery  Informational message only; no corrective action is needed.

Cause  The message collection for alternate collector 2 has been switched from the previous collector process in response to an interactive or programmatic request.

Effect  This message and subsequent operator messages are sent to the new collector. The related operator message -32717 is sent to the previous collector.

Recovery  Informational message only; no corrective action is needed.

Cause  Event recording on collector 2 has been stopped in response to an interactive or programmatic request.

Effect  No further messages are recorded by alternate collector 2.

Recovery  Informational message only; no corrective action is needed.

Cause  Message collection for alternate collector 1 has been switched to a new collector process in response to an interactive or programmatic request.

Effect  This message is sent to the old collector. The related operator message -32721 and subsequent operator messages are sent to the new collector.

Recovery  Informational message only; no corrective action is needed.

Cause  The message collection for collector 1 has been switched from the previous collector process in response to an interactive or programmatic request.

Effect  This message and subsequent operator messages are sent to the new collector. The related operator message -32720 is sent to the previous collector.

Recovery  Informational message only; no corrective action is needed.

Cause  Event recording on collector 1 has been stopped in response to an interactive or programmatic request.

Effect  No further messages are recorded by alternate collector 1.

Recovery  Informational message only; no corrective action is needed.

Cause  The swap volume specified in the named object’s startup parameters is not a local disk volume. This error can occur when you start a process across a network.

Effect  The object uses the default swap volume default-volname instead of the specified volume, volname.

Recovery  Abort the process and restart it with a more suitable swap volume, or allow the process to run using the default swap volume.

Cause  The state of dynamic memory changed: memory either became congested or is no longer congested.

Effect  The subsystem might reduce some of its optional uses of memory (for cache buffers, for example). Some degradation of performance is possible.

Recovery  Informational message only; no corrective action is needed.

Cause  An attempt to start a backup process was abandoned because the HP internal DATA_INITIALIZE_CHKPT_ procedure failed. The cause of the failure is indicated by proc-errnum and is described in error-text.

Effect  The attempt to start the backup is abandoned.

Recovery  Take appropriate action based on the error code and text.

Cause  The PROCESS_CREATE_ or NEWPROCESSNOWAIT procedure encountered an error trying to start a child process. The cause of the error is indicated by the primary and secondary error numbers and the error text.

Effect  The attempt to start the child process is abandoned.

Recovery  See Appendix C, for NEWPROCESS error information and Appendix D, error information, or see the Guardian Procedure Errors and Messages Manual.

Cause  The process terminated voluntarily in response to the indicated condition.

Effect  The process is no longer running. The backup may have taken over.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified file cannot be used as a character-map file, because its format is inappropriate.

Effect  The process terminates.

Recovery  Specify a valid character-map file in the process startup parameters.

Cause  The requested character map is not in the specified character-map file.

Effect  The process terminates.

Recovery  Verify that the specified map is in the character-map file declared in the process startup parameters.

Cause  A request for Transaction Monitoring Facility (TMF) services could not be satisfied, because TMF is not configured on the system.

Effect  The requested TMF operation is abandoned.

Recovery  Check the system configuration.

Cause  Event Management Service (EMS) recording of messages on the primary collector stopped in response to an interactive or programmatic request.

Effect  EMS recording stops.

Recovery  Informational message only; no corrective action is needed.

Cause  The logging functions stopped in response to an interactive or programmatic request.

Effect  Log recording stops.

Recovery  Informational message only; no corrective action is needed.

Cause  Within the last 30 minutes, more than five attempts were made to start a backup process, and all attempts ended in abnormal termination of the backup. This may be caused by hardware failure or by an internal programming error in the subsystem.

Effect  No further attempts are made to start a backup. The backup processor number is reset and the primary process runs without a backup.

Recovery  Try assigning the backup process to a different processor. This often works when hardware is the source of the problem. If this error is reported the first time a subsystem is run or if it is reported repeatedly, contact your HP service provider and provide all relevant information as follows:

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 to allocate an extended segment failed for a reason other than an I/O failure. error-text describes the error.

Effect  The indicated segment was not allocated.

Recovery   Examine the error code included in error-text.

If the error code is -1, needed disk space is not available. Remove unnecessary files from the swap volume or designate another swap volume.

If the error code is -5 or -6, the operating system cannot create new segments in this processor. Reduce the number of segments in use in this processor, or switch the process to a different processor.

Any other error code indicates an internal error; contact your HP service provider and provide all relevant information as follows:

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 memory required to handle a request from the specified process was unavailable. A memory shortage can result from inadequate process memory allocation at startup, lack of disk space on the swap volume, or an overloaded process.

Effect  The request is usually rejected.

Recovery  If insufficient memory was allocated at startup, adjust the value of the DATAPAGES startup argument and rerun the process. If swap space is inadequate, find additional disk space or change the designated swap volume. If the process is overloaded with requests, examine the processing load, restrict the number of command messages, or eliminate unnecessary requests.

Cause  The backup process stopped in response to a request to stop or change the backup.

Effect  The backup process stopped. If a backup processor has been assigned, operator message -32759 probably follows.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified object was started on an inappropriate processor. The hardware or software configuration is not adequate.

Effect  The object terminates.

Recovery  Run the object on a suitable host processor.

Cause  The specified object received a message from a file that the object did not record as open. This message can occur if another subsystem with the same name was running before the subsystem reporting the error.

Effect  The request is rejected with file-system error 60, and the process continues.

Recovery  Informational message only; no corrective action is needed.

Cause  The process has gone through a takeover sequence more than five times within the last 30 minutes (approximately) since the process was initiated or since an operator explicitly caused a primary process to fail. Each of these takeovers was due to abnormal termination of the primary process. This takeover sequence may indicate a hardware failure.

Effect  No new backup process is started. The backup processor is now undefined.

Recovery  Assign a different backup processor. If the problem recurs, there may be a programming error in the subsystem. Contact your HP service provider and provide all relevant information as follows:

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 backup process assumed control from the primary process. Takeover may result from a failing primary process or from an operator or programmatic request.

Effect  If recovery is successful, the backup process assumes the role of primary process and attempts to start a backup in the processor that held the previous primary process. A message should follow indicating that a new backup has been started or that the startup attempt has failed.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified object received a request bearing a SYNC-ID that was older than indicated by the corresponding file open.

The SYNC-LEVEL parameter, supplied when the process was opened, told the subsystem how many completed requests to retain to protect against takeover. This message indicates that an application reissued a request that is no longer retained and might signal that the application is performing checkpoints improperly.

Effect  The request is rejected with file-system error 39.

Recovery  Examine the application for misuse of the file-system sync-depth feature.

Cause  The indicated Subsystem Programmatic Interface (SPI) routine detected an improperly structured request buffer. The requester may have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a Subsystem Programmatic Interface (SPI) message that was too short to be a valid request.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a Subsystem Programmatic Interface (SPI) message that did not have the code word -28 in the first two bytes. The requester may have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a Subsystem Programmatic Interface (SPI) message that was not a valid command message. The requester may have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a Subsystem Programmatic Interface (SPI) message from which the SPI header was missing. The requester may have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a Subsystem Programmatic Interface (SPI) message with a byte count that cannot occur in a well-formed message. The byte count was longer than the transmitted buffer, was odd, or was less than the smallest possible value for a valid request. The requester may have corrupted a valid SPI buffer, lost track of where the buffer was built, or sent the wrong data.

Effect  The request is rejected with file-system error 2.

Recovery  The requester should recreate and send a valid message buffer. If necessary, correct errors in the application.

Cause  The specified object received a RESETSYNC signal from the indicated process. This message usually occurs following an application program takeover when a file was opened in the backup with a CHECKOPEN or FILE_OPEN_CHKPT_ call, but the sync-block was never checkpointed.

Effect  All operations in progress that originated from the file that supplied the RESETSYNC request are discarded. The state of resources that these requests were controlling is undefined.

Recovery  No recovery is required if this error is expected following an application takeover. If the error is unexpected, it might indicate that the application program is not checkpointing file controls properly. Analyze the application program for proper checkpointing of file controls following CHECKOPEN or FILE_OPEN_CHKPT_ procedure calls.

Cause  The specified object rejected a message because too many requests were already in progress. Up to 2000 requests can be accommodated.

Effect  The application request is rejected with file-system error 30.

Recovery  Examine the message log to determine whether error 30 was generated by the file system or the subsystem. If the file system generated the error, reconfigure the operating system to provide more message block space or reconfigure the application environment to assign processes to a different set of processors. If the subsystem generated the error, rebalance the process/processor mix.

The application program can retry command messages after a short time delay but should be careful to avoid indefinite retries.

Cause  The specified object was started.

Effect  The object process is running.

Recovery  Informational message only; no corrective action is needed.

Cause  The process must have a name but was started without one.

Effect  The process terminates.

Recovery  Inspect the sequence used to initiate the process. If it is initiated from a command interpreter, make sure that the NAME option is specified. If it is initiated from within some other application process, examine the way in which it is started and make sure that the resultant process is named. You can prevent this situation by assigning the “must run named” attribute.

Cause  There is insufficient memory available to satisfy internal needs. A memory shortage can result from inadequate process memory allocation at startup, lack of disk space on the swap volume, or an overloaded process.

Effect  Under most conditions, the process terminates.

Recovery  If insufficient memory was allocated at startup, adjust the value of the DATAPAGES startup argument and rerun the process. If swap space is inadequate, find additional disk space or change the designated swap volume. If the process is overloaded with requests, examine the processing load, restrict the number of command messages, or eliminate unnecessary requests.

Cause  The log file was changed.

Effect  This message appears as the last message in the old log if the old log was accessible. Subsequent log messages are sent to the new file.

Recovery  Informational message only; no corrective action is needed.

Cause  The logging functions have been switched from the indicated file to the file on which this message appears.

Effect  Subsequent log messages are sent to the new file.

Recovery  Informational message only; no corrective action is needed.

Cause  A file-system error was returned on a file I/O attempt. This message is typically used for errors associated with the $RECEIVE file, and it may be caused by lack of disk space for allocating an extended segment for some internal table or file. If the error is encountered on the $RECEIVE file, there may be a serious programming problem in the subsystem, particularly if the error is reported repeatedly or the first time the subsystem is started.

Effect  If the file is critical to the subsystem, the process stops abnormally.

Recovery  If the error is encountered on the $RECEIVE file repeatedly or the first time the subsystem is started, contact your HP service provider. If error 43 is returned by the ALLOCATESEGMENT procedure, free some disk space or specify another disk for extended segments. Refer to Appendix B, for corrective action for the file-system error.

When contacting your HP service provider, provide all relevant information as follows:

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  Message collection for the primary collector has been switched to a new collector process in response to an interactive or programmatic request.

Effect  This message is sent to the old collector. The related operator message -32757 is sent to the new collector.

Recovery  Informational message only; no corrective action is needed.

Cause  Event collection for the primary collector has been switched to this collector process in response to an interactive or programmatic request.

Effect  This message is sent to the new collector. The related operator message -32756 was sent to the previous collector.

Recovery  Informational message only; no corrective action is needed.

Cause  The specified object could not initiate a backup process.

Effect  The attempt to start the backup was abandoned.

Recovery  Examine the error associated with the process creation procedure call and take appropriate action. SeeAppendix C, for NEWPROCESS error information and Appendix D, for PROCESS_CREATE_ error information, or see the Guardian Procedure Errors and Messages Manual.

Cause  A backup process was started in the indicated processor.

Effect  The backup process is running.

Recovery  Informational message only; no corrective action is needed.

Cause  The backup process stopped unexpectedly (for a reason other than a STOP command issued by the primary process). This typically results from interactive termination of a backup process, failure of the processor in which the backup was running, or a programming error in the backup. This message is not issued if the backup process was stopped by the primary process.

Effect  The process no longer has a backup. The primary attempts to start a backup.

Recovery  Determine why the backup stopped. If the backup processor went down, change backup processor assignments to restore the process to full backup status or wait until the processor is restored. If the process was terminated by the operator, it is restarted automatically by the primary. If the process stopped for other reasons, it probably represents a program problem. If the error occurs the first time the subsystem is brought up or occurs repeatedly, contact your HP representative and provide all relevant information as follows:

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 specified object detected an unexpected system message on $RECEIVE. The specified code gives the value of the first word of the message.

Effect  The object ignores the message, but generates a minimal reply.

Recovery  This indicates a serious programming problem in the subsystem. Contact your HP service provider and provide all relevant information as follows:

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 subsystem received a primary process open request for a file that was still opened by the backup process. This condition can arise if the primary fails to issue a CHECKCLOSE call on a backup file or does not wait for the backup process to complete the close.

Effect  The open is rejected with a file-system error 17.

Recovery  Examine the primary application’s handling of CHECKCLOSE or FILE_CLOSE_CHKPT_. If the backup process is active (that is, if it is not using CHECKMONITOR), make sure that there is a way for the backup to signal completion of the backup close so that the primary can avoid the file until that signal is received.

Cause  One of the parameters either specified in the RUN command, passed in the startup message, or specified as a PARAM contained an invalid value.

Effect  The process terminates.

Recovery  Correct the parameter value and retry.

Cause  The process startup sequence contained an unrecognized parameter name. The RUN command or startup message contained an invalid or unsupported parameter.

Effect  The process terminates.

Recovery  Correct the parameter and retry.

Cause  The specified object rejected an open attempt by the indicated process.

Effect  The open is rejected.

Recovery  Correct the name used by the application attempting to open the server. This message may signal an attempt to break security.

Cause  The specified object received an open message from a backup process but could not find a corresponding open from the primary process.

Effect  The open is rejected.

Recovery  This message may indicate a programming problem in the requester. If the requester is using CHECKOPENs, it is possible that the OPEN failed but the requester went ahead trying the CHECKOPEN. This can also indicate that the program and its backup are out of synchronization.

Cause  The object detected an internal program error.

Effect  The process terminates abnormally.

Recovery  This message indicates a serious internal programming error. Contact your HP service provider and provide all relevant information as follows:

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.