A checkpoint is not allowed when storage access across address
space boundaries has been established. When using cross-memory support,
the restrictions shown in Table 1 may
apply.
Table 1. Cross-Memory Support
Restrictions| Macros |
Restriction Code |
Instructions |
Restriction Code |
|---|
| LXRES |
2 |
EPAR |
2 |
| ETCRE |
2 |
ESAR |
2 |
| ETCON |
2 |
IAC |
2 |
| AXRES |
2 |
IVSK |
2 |
| AXERT |
2 |
MVCP |
3 |
| AXSET |
2 |
MVCS |
3 |
| ATSET |
2 |
MVCK |
3 |
| PCLINK |
1 |
PC* |
4 |
| |
|
PT* |
3 and 4 |
| |
|
SAC |
1 |
| Code
Definitions:
- You must release this resource before checkpoint and reestablish
it after checkpoint or restart.
- You must reestablish this resource after a restart.
- You must be sure that the keys and ASIDs are correct after a restart.
- Any attempt to restart from a checkpoint taken in a program call
(PC) routine is unpredictable. If a PC routine issues a PCLINK, and
then a CHKPT, the error is detected and a checkpoint request is refused. It is impossible to detect a PC routine
when the PC routine does not issue a PCLINK and the PC routine is
entered without a space switch. If a PC routine issues a checkpoint,
that PC routine must ensure that all the requisite values needed for
a PT instruction are current before issuing the PT instruction. These
values may change after a restart (for example, the ASID might be
different).
|
z/OS DFSMSdfp Checkpoint/Restart
Copyright IBM Corporation 1990, 2014