Checkpoint/restart does not include support for SLIP PER monitoring.
The effects of PER on restarting a checkpointed program follow:
No PER monitoring before checkpoint, no PER monitoring
after restart: A program is running in an address space not monitored
for PER interrupts; the program is checkpointed. If the program is
restarted in an address space monitored for PER interrupts, SLIP does
not monitor the restarted program.
PER monitoring before checkpoint, no PER monitoring
after restart: A program is running in an address space monitored
for PER interrupts; the program is checkpointed. If it is restarted
in an address space not monitored for PER interrupts, but other address
spaces are being monitored, unwanted PER interrupts may occur, depending
on the PER control register settings.
If unwanted PER interrupts
occur in the restarted program, SLIP disables the PSW PER bit in the
restarted program. This action can eventually remove all performance
problems because of the unwanted PER interrupts from the restarted
program.
PER monitoring before checkpoint, no PER monitoring
after restart: A program is running in an address space monitored
for PER interrupts; the program is checkpointed. If the program is
restarted and PER monitoring is not active in the system, the system
performance might slow down because the PSW PER bit is enabled in
the restarted program.