01 |
|
Module IEAVCKRS—Supervisor Control Checkpoint/Restart Router. |
|
08 |
The number of requested SSCRs for the second checkpoint invocation
does not match the number requested in the first checkpoint invocation. |
02 |
|
Module IEAVSPI—SPIE/ESPIE Checkpoint/Restart Routine. |
|
08 |
ESPIE exits were created while the task was running with a
PSW key other than the assigned key. |
|
255 |
IEAVSPI requested a negative number of SCCRs. |
03 |
|
Module IEAVCRVF—Vector Checkpoint/Restart Routine. |
|
04 |
The pointer to the subject task's VSSA is invalid. |
|
08 |
The vector SLIH determined that there are no eligible vector
processors with an attached Vector Facility (VF) online. |
|
12 |
The vector SLIH could not obtain a VSSA for the task. |
|
16 |
The VF section size recorded during the checkpoint is not equal
to the VF section size during the restart. |
|
20 |
In the time interval between checkpoint and the restart, the
mapping of the VSSA changed. |
|
24 |
There are no processors with an attached VF in the complex. |
|
28 |
An unexpected error occurred in IEAVCRVF. |
|
32 |
VF status has been lost because of a machine check. |
|
255 |
IEAVCRVF requested a negative number of SCCRs. |
04 |
|
Module IEAVLSCR—Linkage Stack Checkpoint/Restart Routine. |
|
08 |
There are entries on the task's linkage stack. |
05 |
|
Module IEAVALCR—Access List Checkpoint/Restart Routine. |
|
08 |
The task has entries in use on either the dispatchable unit
access list (DU-AL) or on the primary address space access list (PASN-AL).
That is, the task has established addressability to another address/data
space via an access list. |
|
0C |
An unexpected error occurred during IEAVALCR processing. |
06 |
|
Module IEANTCKR-Name/Token checkpoint/restart extension routine. |
|
08 |
Address space owns name/token pairs that were not created with
the IEANT_CHECKPOINTOK value in the persist parameter. Remove the
definition before taking the checkpoint or add the IEANT_CHECKPOINTOK
option. |