IEE241I

Explanation
A reconfiguration request asked that the system
reconfigure a CPU or core online
or offline. The system was unable to perform the requested reconfiguration;
the message text gives the reason.
In the message text:
DUE TO RPSGNL SWITCH FAILURE ON TARGET CPU
RPSGNL SWITCH failed to initiate the CPU ending routine.
DUE TO SYSTEM RECOVERY
Alternate CPU recovery (ACR) processing removed a CPU during CONFIG
command processing.  
WOULD REMOVE LAST CPU AVAILABLE FOR JOB SCHEDULING
A CPU cannot be removed because it is the only one
in the system that can be used for scheduling jobs.
WOULD RESULT IN A NO CLOCK CONDITION
A CPU could not be taken offline because it is the
only CPU in the complex with a functioning time-of-day (TOD) clock.
ERROR WHILE PERFORMING SIGP RESTART
An error occurred on a CPU during SIGP RESTART
processing.
ERROR WHILE PERFORMING SIGP INITIAL CPU RESET
An error occurred on the target a CPU during
SIGP INITIAL processor RESET processing.
ERROR WHILE PERFORMING SIGP SET PREFIX
An error occurred on the target a CPU during
SIGP SET PREFIX processing.
CPU INITIALIZATION PROCESSING DID NOT BEGIN
Processor initialization did not start on a CPU.
CPU INITIALIZATION PROCESSING DID NOT COMPLETE
Processor initialization did not complete on a
CPU.
CLOCKS CANNOT BE SYNCHRONIZED
CPU reconfiguration process failed because
TOD clocks could not be synchronized.
ERROR CREATING SYSTEM TRACE AREAS
A CPU could not be brought online because
the system trace areas could not be created for it.
ERROR CREATING MACHINE CHECK HANDLER AREAS
A CPU could not be brought online because
the machine check handler areas could not be created for it.
ERROR CREATING CPU-RELATED LINKAGE STACKS
A CPU could not be brought online because
the central processor-related linkage stacks could not be created
ERROR OBTAINING STORAGE
A CPU could not be brought online because
storage could not be obtained for processor-related system data areas.
ERROR LOCATING FRR INITIALIZATION ROUTINE
A CPU could not be brought online because
a routine could not be located in the system nucleus.
ESTAE COULD NOT BE ESTABLISHED
The recovery environment for CPU or core reconfiguration could not be established.
ID NOT RECOGNIZED
The reconfiguration operation was canceled because the specified
CPU or core identifier
is incorrect.
{CPU|CORE} NOT AVAILABLE
The reconfiguration operation was canceled because the requested
CPU or core does not belong
to this configuration.
WOULD REMOVE LAST {CPU|CORE}
The target CPU or core cannot
be removed because it is the only one in the system.
UNABLE TO OBTAIN {CPU|CORE} STATUS, SERVICE PROCESSOR COMMUNICATION
FAILURE
The reconfiguration operation was cancelled because of a CPU or core interface error.
UNABLE TO CONFIGURE CRYPTO OFFLINE
The operator tried to configure offline a CPU with
an associated Integrated Cryptographic Feature (ICRF) but the system
could not configure the ICRF offline. If no logrec data set error
record accompanies this message, one of the following has occurred: The system detected an incorrect parameter.
The processor or ICRF is not in a suitable state to be configured
offline.  For example, the ICRF is not installed on the processors.

UNABLE TO OBTAIN STORAGE FOR ENF SIGNAL
The operator tried to configure offline a CPU with
an associated Integrated Cryptographic Feature (ICRF) but the system
could not obtain storage to issue an ENF signal.
REQUIRES HIPERDISPATCH ENABLED
A CPU ID greater than x'3F' has been dynamically added to the
system while HiperDispatch mode is disabled. To configure a CPU or core with a CPU address
greater than x'3F', HiperDispatch mode must be enabled.
PROCESSOR TYPE MISMATCH
A CONFIG {CPU(x)|CORE(x)},ONLINE|OFFLINE
or CONFIG MEMBER command was issued with a CPU or core type specification,
and the subject CPU or core is
not of the specified type.

System action
The system cancels the reconfiguration and tries
to return the CPU or core to
the  state it was in before reconfiguration processing began.

Operator response
Do the following: Enter DISPLAY MATRIX=CPU to display the status
of CPUs (when LOADxx specifies PROCVIEW CPU) or DISPLAY MATRIX=CORE
to display the status of cores (when LOADxx specifies PROCVIEW CORE).
For more information on the DISPLAY command, see z/OS MVS System Commands. 
Depending on the value of text, do the following: DUE TO SYSTEM RECOVERY
Check the CPU or core status.
WOULD RESULT IN A NO CLOCK CONDITION
Enter the CONFIG command again when there are other CPUs or cores in the complex with
functioning TOD clocks.
CPU INITIALIZATION PROCESSING DID NOT COMPLETE
Enter the CONFIG command again; if the problem persists, notify
the system programmer.
ID NOT RECOGNIZED
Enter the CONFIG command again specifying a valid CPU or core identifier.
{CPU|CORE} NOT AVAILABLE
Make sure that the CPU or
core is in this configuration. Enter the CONFIG command again.
REQUIRES HIPERDISPATCH ENABLED
Notify the system programmer.
PROCESSOR TYPE MISMATCH
If you entered the intended processor type, notify the system
programmer. Otherwise, specify the correct processor type.

For any other message text, enter the CONFIG command
again.

System programmer response
If the message text is REQUIRES HIPERDISPATCH
ENABLED, enable HiperDispatch mode on the system to configure online
CPUs or cores with a CPU
address greater than x'3F'.
If the message text
is PROCESSOR TYPE MISMATCH, examine the logical partition definition
to verify that the processor type is what you intended.
For
other message text values, you can search problem reporting databases
for a fix for the problem.

Source
Reconfiguration

Module
IEEVCVSR

Routing code
-

Descriptor code
5