NO {REAL} STORAGE CONFIGURED-NO MORE AVAILABLE --or-- NO
MORE {REAL} STORAGE CONFIGURED-NO MORE AVAILABLE
Explanation
One of the following reconfiguration requests was
entered to reconfigure storage:
- CONFIG STOR(xM)
- CONFIG STOR(xM-yM)
- An internal request
The system did not reconfigure any of the storage as requested.
In
the message text:
- {REAL|EXTENDED} STORAGE LOCATIONS ddM TO ddM
NOT RECONFIGURED-text
- {REAL|EXTENDED} STORAGE NOT RECONFIGURED-text
- NO {REAL} STORAGE CONFIGURED-NO MORE AVAILABLE
- The system did not perform the requested reconfiguration. In the
message text:
- ddM
- A 1- to 2-digit decimal number identifying a storage address,
in megabytes.
- OPERATOR CANCELLED
- The operator replied CANCEL to message IEE575A to cancel a CONFIG
STOR command.
- PERMANENTLY RESIDENT DATA
- The system cannot reconfigure the storage because the storage
contains a hardware system area (HSA) or permanently resident data.
The nucleus code is an example of permanently resident data.
- V=R CANDIDATE STORAGE
- The storage contains some or all of the V=R (virtual equals real)
storage area. When the system issued message IEE577D, the operator
replied NONE, indicating that none of the V=R area was to be reconfigured
offline.
- COMMAND PROCESSOR ERROR
- One of the following occurred:
- The ESTAE macro failed, so that a recovery environment could not
be established for configuring the storage.
- A system ABEND occurred while the storage was being configured
offline.
- SOME STORAGE IN OFFLINE STORAGE ELEMENT
- A CONFIG STOR(xM-yM),OFFLINE
command was entered. The range of storage identified in the message
is partially or entirely within an offline storage element.
- OFFLINE PRIOR TO REQUEST
- The range of storage identified in the message was offline when
a CONFIG STOR command was entered.
- STATE UNCERTAIN
- A CONFIG STOR(xM),ONLINE command or CONFIG
STOR(xM-yM),ONLINE command was
entered. The range of storage identified in the message is physically
online, but the command processor failed while bringing the storage
logically online. Some or all of the range identified might be online.
Use the DISPLAY M=STOR command to find out how much, if any, storage
is online.
- UNABLE TO SWAP DATA
- A CONFIG STOR(E=x),OFFLINE command was entered.
The system tried to swap storage containing fixed data with storage
containing non-fixed data, but the command processor either could
not find or could not configure offline enough storage containing
non-fixed data.
- INVALID RANGE
- The CONFIG STOR(xM-yM) command
entered contained this error:
- One of the addresses was not a multiple of the smallest amount
of storage that can be physically reconfigured in the system.
- RANGE END TOO HIGH
- A CONFIG STOR(xM-yM) command
was entered. The ending address, yM, was higher
than the highest central (real) storage address in the system.
- INVALID AMOUNT
- A CONFIG STOR(xM) command was entered. The
amount of storage specified, xM, was either 0 or
was not a multiple of the smallest amount of storage that can be reconfigured
in the system.
- AMOUNT TOO HIGH
- A CONFIG STOR(xM) command was entered. The
amount of storage specified, xM, was greater than
the total amount of storage in the system.
- NO MORE AVAILABLE
- A CONFIG STOR ONLINE command was entered. Either all of the storage
in the system was already online, or there was no more storage physically
available to be reconfigured online.
- OPTION NOT INSTALLED
- A CONFIG command was entered, but the option specified is not
installed in the system.
- NO MORE {REAL} STORAGE CONFIGURED-NO MORE AVAILABLE
- The system reconfigured part of the storage specified in the command
but could not reconfigure all of it.
System action
If a reconfiguration error caused an abnormal
ending, the system writes an SVC dump and a logrec data set error
record.
In all other cases, the system continues processing.
Operator response
System programmer response
Examine the dump to verify that the
RSU parameter is correct for your installation. If the problem persists,
search problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM® Support Center. Provide the
SVC dump and the logrec data set error record.
Source
Module
Routing code
Descriptor code