Chapter 64 NSK (NonStop Kernel) Messages

The messages in this chapter are generated by the NonStop Kernel. These messages include NSK as the subsystem name.

Some messages that include NSK as the subsystem name are sent by the Reload subsystem. For these messages, see the Reload chapter.

The following example shows the format of these messages as they are sent to printers, log files, and terminals:

95-07-28 18:02:28 \DALLAS.3,0 TANDEM.NSK.D40 000211 KMSF: 
CONFIGURATION FILE: $SYSTEM.SYS40.ZSYSCFG




	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.

100

server: cpu changed from old to new because of cause

`server`	is the process name of the OSS message-queue server reporting the error.
`old`	is the processor number of the previous primary processor.
`new`	is the processor number of the primary processor on which the OSS message-queue server is currently running.
`cause`	is the reason for the processor change.

Cause The OSS message-queue server has switched processors in response to a hardware or software failure.

Effect The OSS message-queue server now runs on what was previously its backup processor.

Recovery Informational message only; no corrective action is needed.

101

server: COMMAND LINE PARAMETERS INVALID: list

`server`	is the process name of the OSS message-queue server reporting the error.
`list`	is the list of invalid parameters.

Cause The OSS message-queue server was started with the indicated invalid command-line parameters.

Effect The OSS message-queue server terminates.

Recovery Start the OSS message-queue server with correct parameters. See the Open System Services Management and Operations Guide for a list of valid parameters.

102

server: INTERNAL ERROR: error

`server`	is the process name of the OSS message-queue server reporting the error.
`error`	is the description of the specific error detected.

Cause The OSS message-queue server has detected an internal inconsistency.

Effect The OSS message-queue server terminates.

Recovery Contact your a service provider and provide all relevant information as follows:

Saveabend file
A copy of the OSS fileset catalog files
Description 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.

103

server: Backup Process created in cpu nn

`server`	is the process name of the OSS message-queue server reporting the event.
`nn`	is the processor number of the processor on which the backup server process is running.

Cause The OSS message-queue server has successfully created its backup server process.

Effect The OSS message-queue server is now running as a process pair.

Recovery Informational message only; no corrective action is needed.

104

server: Unable to create backup in cpu nn, PROCESS_CREATE_Err: pc-error, Err detail: error-detail

`server`	is the process name of the OSS message-queue server reporting the error.
`nn`	is the processor number of the processor on which the creation of the backup server process was attempted.
`pc-error`	is the error returned by the Guardian PROCESS_LAUNCH_ procedure. For further information, see the Guardian Procedure Errors and Messages Manual.
`error-detail`	is the error detail returned by the Guardian PROCESS_LAUNCH_ procedure. For further information, see the Guardian Procedure Errors and Messages Manual.

Cause The OSS message-queue server was unable to create a backup server process because of a resource shortage in the backup processor. There might be insufficient swap space on or too many processes running in the backup processor.

Effect The OSS message-queue server has no backup server process.

Recovery Correct the cause of the resource shortage. If there is a shortage of swap space, allocate additional swap space. If too many processes are running, stop unneeded processes on the backup processor.

105

server: Malloc unable to allocate Memory

server

is the process name of the OSS message-queue server reporting the error.

Cause The OSS message-queue server is unable to allocate memory. There might be insufficient swap space or too many processes running.

Effect The OSS message-queue server terminates.

Recovery Correct the cause of the resource shortage. If there is a shortage of swap space, allocate additional swap space. If too many processes are running, stop unneeded processes.

106

server-name: Server name is not correct

server-name

identifies the server.

Cause The server was started with a wrong name.

Effect The server terminates.

Recovery Start the server with the correct name.

107

server-name: Mom process failed

server-name

identifies the message-queue server.

Cause The mom process of the message-queue sever failed.

Effect If the primary message-queue server has failed, the backup process becomes the primary and creates a new backup. If the backup process has failed, the primary process creates a new backup.

Recovery This is an informative message only; no corrective action is needed.

108

server-name: Backup failing too often

server-name

identifies the message-queue server.

Cause The backup process of the message-queue server is failing too often.

Effect When the backup process fails too often in a short period of time, the server message-queue runs without a backup process for significant amount of time. The message‑queue server primary process creates a new backup process.

Recovery This is an informative message only, but it is recommended to check that you try to determine why the backup process is failing so often.

109

server-name: Backup is in invalid state

server-name

identifies the message-queue server.

Cause The message-queue server primary process failed before it checkpointed all the information to the backup process, because the backup process is in an invalid state.

Effect After generating this event, the message-queue server terminates.

Recovery Restart the message-queue server.

110

server-name: Backup is stopped

server-name

identifies the message-queue server.

Cause The primary message-queue server process stopped the backup process server when it detected a problem with the backup process.

Effect The primary message-queue server process creates a new backup process.

Recovery This is an informative message only; no corrective action is needed.

111

server-name: Invalid Dialect type

server-name

identifies the message-queue server.

Cause The message-queue server received a request with an invalid dialect.

Effect The message-queue server discards the invalid request.

Recovery This is an informative message only; no corrective action is needed.

112

server-name: Invalid Request type

server-name

identifies the message-queue server.

Cause The message-queue server received an invalid request.

Effect The message-queue server discards the invalid request.

Recovery This is an informative message only; no corrective action is needed.

113

server-name: Backup is not running

server-name

identifies the message-queue server.

Cause The message-queue server is running without a backup process.

Effect The message-queue server is no longer fault-tolerant.

Recovery This is an informative message only, but HP recommends that you try to determine why the backup server process fails so often.

114

OSS PME table usage is at currentPMEusagepercentage PMEs InUse : currentPMEusage Max PMEs : maxPME

`currentPMEusagepercentage`	is the current PME table usage percentage.
`currentPMEusage`	is the current PME usage.
`maxPME`	is the maximum PME table size.

Cause One of the following:

The PME table usage has crossed the threshold (70% of the maximum PME table size).
The PME table usage is above the threshold and 15 minutes have elapsed since the last event.
The PME table usage is above the threshold and has changed by more than 3% of the maximum PME table size since the last event.
The PME table usage has dropped below the threshold and 15 minutes have elapsed since the last event.
The PME table usage has dropped below the threshold and has changed by more than 3% of the maximum PME table size since the last event.

Effect OSS Process Creations fail if the PME table usage is 100%.

Recovery This is an informational message only.

115

An invalid exception occurred for the specified process

Cause The IB IP received an unknown exception.

Effect The IB IP stopped itself.

Recovery This is an informational message only.

116

Debug Services was unable to start the default debugger

Cause The program file is either missing or not secured correctly.

Effect The process requiring debug services resumes.

Recovery This is an informational message only.

117

Unable to send startup message to the default debugger

Cause The default debugger might have terminated.

Effect The process requiring debug services resumes.

Recovery This is an informational message only.

118

Default debugger is not registered with the debug services

Cause The default debugger might have terminated.

Effect The process requiring debug services resumes.

Recovery This is an informational message only.

119

A persistent debugger stopped and was not restarted in the expected timeframe

Cause Unknown

Effect The process or processes being controlled by the debugger resume.

Recovery This is an informational message only.

120

A process encountered a MAB which had been not registered for

Cause Unknown

Effect The MAB IP received an exception for a process that was not registered as an MAB.

Recovery This is an informational message only.

121

A process encountered a TFDS trigger, but the TFDS subsystem is not registered with Debug Services

Cause Unknown

Effect The process that encountered the TFDS trigger continues.

Recovery This is an informational message only.

122

Debug Services was unable to allocate memory

Cause Unknown

Effect The request being processed fails.

Recovery This is an informational message only.

123

Debug Services monitor encountered an error deregistering

Cause Unknown

Effect Debug-related requests in the given processor will probably fail.

Recovery This is an informational message only.

124

Debug Services monitor encountered an error registering itself with NSK

Cause Unknown

Effect Debug-related requests in the given processor will probably fail.

Recovery This is an informational message only.

125

Debug Services monitor encountered an error registering itself with NSK

Cause The Debug Services monitor successfully registered with the NonStop operating system.

Effect None.

Recovery This is an informational message only.

126

A debugger has enabled privileged debugging with a particular process

Cause A debugger enabled privileged debugging with a particular process.

Effect None.

Recovery This is an informational message only.

128

Offending process PIN is: PIN Guardian filename: FILE-NAME TLEs allocated to this process: TLEs Maximum TLEs for the processor: TLEMAXIMUM TLE usage (%) is TLEPERCENT

`PIN`	is the process identification number (PIN) of the process that crossed the threshold of 50% or 75%.
`FILE-NAME`	is the Guardian file name of the process that crossed the threshold of 50% or 75%.
`TLEs`	is the number of time-list elements (TLEs) allocated to the process that crossed the TLE threshold.
`TLEMAXIMUM`	is the maximum number of TLEs available in the processor.
`TLEPERCENT`	is the number of TLEs currently allocated to a process as a percentage of the maximum number of TLEs. The value will be either 50% or 75%.

Cause The process identified by the PIN in this message crossed the threshold of 50% or 75%.

Effect Some other process may not be able to allocate TLEs.

Recovery Stop the process that crossed the 50% to 75% threshold.

129

TLE Limit TLELIMIT reached for Pin PIN Guardian filename: FILE-NAME

`TLELIMIT`	is the configured TLE limit using Subsystem Control Facility (SCF).
`PIN`	is the PIN of the process that crossed the configured TLE limit.
`FILE-NAME`	is the Guardian file name of the process that crossed the configured TLE limit.

Cause The process identified by the PIN in this message crossed the configured TLE limit.

Effect The TLE allocation by the process, which is identified by the PIN in this message, fails till its TLE usage is above the configured TLE limit.

Recovery Increase the configured TLE limit using SCF, if it is low.

130

TLELimit queue overflowed due to PIN PIN

PIN

is the PIN of the process that crossed the configured TLE limit.

Cause The process identified by the PIN in this message crossed the configured TLE limit. Also, the operating system could not generate message 129.

Effect The TLE allocation by the process, which is identified by the PIN in this message, fails until its TLE usage is above the configured TLE limit.

Recovery Increase the configured TLE limit using SCF, if it is low.

131

Process Scheduler change: In CPU CPU-NUM [the process with pin PIN has been [bound to IPU IPU-NUM | unbound] | [soft affinity|DP2] process balancing has been changed from PREV-SETTING to NEW-SETTING | IPU affinity settings have been reset to default values].

`CPU-NUM`	is the processor in which a process scheduler change has been made.
`PIN`	is the PIN identifying the process that has had an ipu setting change.
`IPU-NUM`	is the IPU to which the process identified by PIN has been bound.
`PREV-SETTING`	is the previous process balancing setting in the specified CPU.
`NEW-SETTING`	is the process balancing setting that the specified CPU has been changed to.

Cause An operator has made a change to the IPU affinity of a process or the IPU affinity policies in this CPU.

Effect Changing any of the IPU affinity balancing settings or the IPU affinity of processes may have an undesirable impact on system performance.

Recovery This is an informational message only.

132

OSS PME table usage approaches currentPMEusagepercentage PMEs InUse : currentPMEusage Max PMEs : maxPME

`currentPMEusagepercentage`	is the current PME table usage percentage rounded to the nearest integer value. See the `PMEs InUse` value (`currentPMEusage`) for an accurate number of OSS processes active in the system.
`currentPMEusage`	is the current PME usage.
`maxPME`	is the maximum PME table size.

Cause One of the following:

The PME table usage has crossed the threshold (70% of the maximum PME table size).
The PME table usage is above the threshold and 15 minutes have elapsed since the last event.
The PME table usage is above the threshold and has increased by more than 3% of the maximum PME table size since the last event.
The PME table usage is above the threshold and has decreased by more than 3% of the maximum PME table size since the last event.

Effect OSS Process Creations fail if the PME table usage is 100%.

Recovery This is an informational message only.

133

Global32 memory utilization in CPU cpu: currentAbsSegusagepercent%. availableAbsSegcount of maximumAbsSegcount unitSegs (128KB) available. This range includes FlexPool.

`cpu`	is the affected CPU.
`currentAbsSequsagepercent`	is the current absolute segments utilization percentage rounded to the lower nearest integer value.
`availableAbsSeqcount`	is the number of available absolute segments.
`maximumAbsSeqcount`	is the maximum number of absolute segments.

Cause One of the following:

The absolute segments utilization has crossed the threshold (98% of the maximum absolute segments count).
The absolute segments utilization is above the threshold, and 10 minutes have elapsed since the last event.

Effect Anything that allocates absolute segments (like FlexPool allocation) will fail if the utilization is 100%.

Recovery Identify optional processes that consume significant absolute-segment resources and stop them.

If this error not resolved, contact the Global Mission Critical Solution Center (GMCSC). Provide all relevant information as follows:

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.

200

KMSF TOTAL SWAPSPACE UTILIZATION IN CPU cpu-num: swapspace% KMSF threshold exceeded for file: swapfile (threshold%) Extent size: extent-size disk pages Max extents: num-extents File size reserved: file-size-reserved MB Total file size: total-file-size MB

`cpu-num`	is the number of the processor detecting the condition.
`swapspace`	is the amount of swapspace that the processor currently uses (that is, the combined swap space used by each swap file configured for the processor).
`swapfile`	identifies the kernel‑managed swap file.
`threshold`	identifies the configured threshold for the processor at which messages should be generated.
`extent-size`	is the size of each extent of the swap file.
`num-extents`	is the number of extents that the swap file has.
`file-size-reserved`	is the part of the swap file that the processor currently uses.
`total-file-size`	is the number of memory pages currently allocated for the swap file.

Cause The specified kernel-managed swap file (represented by the token ZNSK-TKN-FILE) exceeded its configured threshold.

Effect The value of swap space use (represented by the token ZNSK-TKN-SWAPSPACE) determines the effect. A high value (approximately 80%) might prevent the processor from creating processes.

Recovery Expand the swap file or add an additional swap file for the processor.

201

KMSF SWAPFILE CREATED: swapfile CPU cpu-num

`swapfile`	identifies the kernel‑managed swap file.
`cpu-num`	identifies the processor detecting the condition.

Cause A swap file has been created using the NSKCOM ADD command.

Effect The swap file is fully allocated, and disk free space is reduced by its configured size. The file is not used until it is enabled for use by the NSKCOM START command.

Recovery Informational message only; no corrective action is needed.

202

KMSF SWAPFILE PURGED: swapfile [ CPU cpu ]

`swapfile`	identifies the purged kernel‑managed swap file.
`cpu`	is the processor associated with the swap file if the processor is known; otherwise, no value is shown.

Cause A kernel‑managed swap file has been purged by the NSKCOM DELETE command.

Effect The swap file is no longer available for use.

Recovery Informational message only; no corrective action is needed.

203

KMSF SWAPFILE STARTED: swapfile CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`cpu`	is the processor associated with the swap file.

Cause The kernel‑managed swap file was enabled for use by the NSKCOM START command, or the swap file was enabled for use by the Kernel‑Managed Swap Facility (KMSF) after the disk that the swap file is on came up.

Effect The swap file is available for swapping by the indicated processor.

Recovery Informational message only; no corrective action is needed.

204

KMSF SWAPFILE STOPPED: swapfile CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`cpu`	is the processor associated with the swap file.

Cause A user stopped usage of the specified swap file by entering the NSKCOM STOP command, or the disk that the swap file was on went down.

Effect Swapping to the specified swap file is prevented. If the swap file’s disk went down, processes swapping to the file are abended. If this is the only swap file available for the processor, stopping use of the file prevents any processes from starting in that processor until a swap file is enabled for use by the Kernel‑Managed Swap Facility (KMSF).

Recovery If other swap files are available for the processor, this is an informational message only; no corrective action is needed.

If the disk that the swap file is on went down, bring the disk up. KMSF automatically opens and starts using the swap file.

If no other swap files are available for the processor, you must add and enable use of a swap file for the processor. Because you cannot start a process on the processor, run NSKCOM on another processor. Use the NSKCOM ADD and START commands to add and enable a swap file for the processor. You can also use the START command to enable the stopped file to put it back into use.

205

KMS swapfile aborted: swapfile CPU cpu

`swapfile`	identifies the KMS swapfile.
`cpu`	is the CPU associated with the swapfile.

Cause A user entered the NSKCOM ABORT command.

has the command completed?

Effect All processes that are swapping to the swapfile are stopped.

is it deleted?

If no other swapfile is configured for the CPU, the CPU goes down?

Recovery Informational message only; no corrective action is needed.

206

KMSF SWAPFILE MAXEXTENTS ALTERED: swapfile NEW VALUE num‑extents CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`num‑extents`	identifies the new number of extents of the swap file.
`cpu`	is the processor associated with the swap file.

Cause A user entered the NSKCOM ALTER command and specified new MAXEXTENTS.

Effect The swap file’s size has been changed to the new MAXEXTENTS.

Recovery Informational message only; no corrective action is needed.

207

KMSF SWAPFILE THRESHOLD ALTERED: swapfile NEW VALUE threshold% CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`threshold`	identifies the new configured threshold for the file at which message 200 should be generated.
`cpu`	is the processor associated with the swap file.

Cause A user entered the NSKCOM ALTER command and changed the configured threshold for the swap file.

Effect Messages will be generated when the swap file exceeds its new threshold.

Recovery Informational message only; no corrective action is needed.

208

KMSF SWAPFILE STOP PENDING: swapfile CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`cpu`	is the processor associated with the swap file.

Cause The NSKCOM STOP command was issued against the specified swap file.

Effect The swap file does not accept any new processes, and its existing processes are not affected. The swap file remains in use until all processes using the file have terminated. The ZSYSCFG file is modified to mark the swap file with a STOP mark.

If this is the only swap file available for the processor, stopping use of the file prevents any new processes from starting in that processor until usage of a swap file is enabled. Any attempts to start new processes generate process creation errors, such as PROCESS_CREATE_ error 55, “the space guarantee cannot be allocated.”

Recovery If other swap files are available for the processor, this is an informational message only; no corrective action is needed.

If no other swap files are available for the processor, you must add and enable use of a swap file for the processor to allow process creation. Because you cannot start a new process on the processor, run NSKCOM on another processor. Use the NSKCOM ADD and START commands to add and enable use of a swap file for the processor. You can also use the START command to put the stop-pending file back into use.

209

KMSF SWAPFILE PURGE PENDING: swapfile CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`cpu`	is the processor associated with the swap file.

Cause The NSKCOM DELETE command was issued against the specified swap file.

Effect The swap file is marked for deletion in the configuration file ZSYSCFG. Once all processes using the swap file have terminated, the swap file is deleted.

Recovery Informational message only; no corrective action is needed.

210

KMSF CONFIGURATION FILE NOT FOUND: config-file

config-file

identifies the Kernel‑Managed Swap Facility (KMSF) configuration file.

Cause A processor being disk booted or bus booted did not find or could not open the KMSF configuration file, $SYSTEM.SYSTEM.ZSYSCFG.

Effect If space is available on $SYSTEM, KMSF creates and opens a default swap file, $SYSTEM.ZSYSSWAP.SWAPnn, where nn represents the processor number. Otherwise, the processor halts with halt code %3055, “swap create failure.”

Recovery If the file ZSYSCFG exists but is corrupt, you might be able to recover its contents by opening it with EDIT or TEDIT. If not, make space available on $SYSTEM for default swap files or use the NSKCOM ADD command to rebuild ZSYSCFG and create swap files for all your processors.

211

KMSF CONFIGURATION FILE: config-file

config-file

identifies the current Kernel‑Managed Swap Facility (KMSF) configuration file.

Cause The Kernel‑Managed Swap Facility (KMSF) has found a configuration file.

Effect KMSF reads the configuration file to set up swap files.

Recovery Informational message only; no corrective action is needed.

212

KMSF CONFIGURATION FILE SYNTAX ERROR ON LINE NUMBER : line-num

line-num

is the EDIT line number in the ZSYSCFG file on which the syntax error was detected.

Cause During startup, a syntax error was detected in the ZSYSCFG configuration file. Normally, you will not receive this message if you use NSKCOM to configure swap files and view and alter the configuration file. The ZSYSCFG file is intended to be altered only by the NSKCOM program. If you receive this message, someone has probably attempted to edit the file.

If there are multiple lines with errors in the ZSYSCFG file, this message is generated for each line.

Effect The specified line of the configuration file is ignored. Any swap file specified on the line is not added or enabled for use. If there is no swap file configured for a processor, KMSF attempts to create a default swap file for the processor. If KMSF cannot create a default swap file, the processor does not come up. The next time a super‑group user (255, n) runs NSKCOM, the Kernel‑Managed Swap Facility (KMSF) deletes the line from the configuration file.

Recovery Print the ZSYSCFG configuration file and note the contents of the line that is in error. Run NSKCOM as a super‑group user (255, n) to correct your KMSF configuration. If a swap file was specified on the erroneous line, use NSKCOM to add and enable use of the file.

If this error recurs or is not resolved through NSKCOM, contact the Global Mission Critical Solution Center (GMCSC). Provide all relevant information as follows:

A copy of your ZSYSCFG file
The contents of the line that is in error
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.

213

KMSF SWAPFILE NOT FOUND: swapfile

swapfile

identifies the kernel‑managed swap file as it is specified in the ZSYSCFG file.

Cause A swap file listed in the ZSYSCFG configuration file was not found during system startup. One possible reason a swap file might not have been found is that the disk was down when the processor was loading.

Effect If another swap file is specified for the missing swap file’s processor, the processor uses the other swap file. If no other swap file is specified and there is sufficient space on $SYSTEM, KMSF creates a default swap file for the processor. If KMSF cannot find or create a swap file, the processor does not come up.

Recovery Check that you have specified the swap file’s name and location correctly in the ZSYSCFG file and that the swap file is on the specified subvolume. If the processor loaded, use the NSKCOM START command to enable use of the swap file. If the processor did not load, ensure that the disk the swap file is on is up when the processor is loaded and reload the processor.

214

KMSF SWAPFILE START FAILED: swapfile CPU cpu

`swapfile`	identifies the kernel‑managed swap file.
`cpu`	is the processor that the swap file is configured for.

Cause When the Kernel‑Managed Swap Facility (KMSF) attempted to enable use of a swap file with the START command, the START command failed. This error can occur during startup or following issuance of the START command. Some possible reasons a START command might fail include:

The swap file’s disk is down.
The swap file’s file code is incorrect. This error only occurs if you create the file using a program other than NSKCOM or if you alter the file code.
The swap file is incorrectly specified for multiple processors and is already in use by another processor.
The system is out of physical memory.

Effect The swap file is not used. If there is a heavy demand for swap space, this might slow system performance.

Recovery Correct the error and enable use of the file again:

If the disk is down, bring the disk up and enable the file.
If the file is bad, use NSKCOM to delete the swap file using. Then add and enable use of the swap file.
If the swap file’s code is incorrect, delete the file. Then use NSKCOM to add and enable use of the file.
If the swap file is specified for multiple processors, add and enable use of another swap file for the each of the other processors.

215

KMSF DEFAULT SWAPFILE USED: swapfile

swapfile

identifies the kernel‑managed swap file.

Cause During system startup, the operating system either was unable to enable the configured swap files for use or no swap files were configured. The operating system created and enabled a default swap file for use. This error might occur because a configured file was on a disk that was not yet up.

Effect Processes swap to the default swap file.

Recovery If you had configured swap files, use the NSKCOM ADD and START commands to enable use of the files.

300

Core license enabled for ENABLED-IPUS IPUs and ENABLED-CPUS CPUs (PREV-ENABLED-IPUS IPUs and PREV-ENABLED-CPUS CPUs were previously enabled)

ENABLED-IPUS	number of enabled IPUs.
ENABLED-CPUS	number of enabled CPUs.
PREV-ENABLED-IPUS	number of previously enabled IPUs.
PREV-ENABLED-CPUS	number of previously enabled CPUs.

Cause A Core License has been enabled on the system.

Effect The number of enabled IPUs and CPUs may have changed.

Recovery This is an informational message only.

301

Core license enablement failed, reason: CORE-LIC-REASON

CORE-LIC-REASON

error code indicating the reason for the Core License enablement failure.

Cause An online Core License enablement failed.

Effect The previous enablement remains in effect.

Recovery Contact your service provider and provide the following information:

Event management service log

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

302

Core license defaults enabled (ENABLED-IPUS IPUs, ENABLED-CPUS CPUs), reason: CORE-LIC-REASON

ENABLED-IPUS	number of enabled IPUs.
ENABLED-CPUS	number of enabled CPUs.
CORE-LIC-REASON	error code indicating the reason for the Core License enablement failure.

Cause The Core License enablement failed at coldload.

Effect The system uses the default Core enablement, which is that all IPUs and CPUs are enabled. EMS event 303 will be issued periodically until a valid Core License is installed and enabled on the system.

Recovery Contact your service provider and provide the following information:

Event management service log

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

303

Core license not enabled, reason: CORE-LIC-REASON. A valid Core license file needs to be installed.

CORE-LIC-REASON

error code indicating the reason for the Core License enablement failure.

Cause The Core License enablement failed at coldload, and no valid license file has been installed and enabled since coldload.

Effect Periodic message indicating that a valid Core License needs to be installed and enabled.

Recovery Contact your service provider and provide the following information:

Event management service log

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

305

The coldload processor’s System Class does not match the System Class in the core license file. The processor model’s System Class is cpu-class. The System Class in the license file is lic-class. A Core license file with a matching System Class needs to be installed.

`cpu-class`	System Class of the coldload CPU. Value can be either 0 (high-end) or 1 (entry-class).
`lic-class`	System Class in the license file. Value can be either 0 (high-end) or 1 (entry-class).

Cause The System Class in the Core License file at coldload does not match the System Class of the coldload CPU.

Effect The coldload CPU boots with the minimum number of IPUs enabled and other CPUs will halt with %1703, %1704, or %1705 when reloaded, until this problem is corrected.

Recovery Contact your service provider and provide the following information:

Event management service log

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