Technical data

Interruptions
•• Program processing (RESTART/RUN) → STOP mode:
If an interruption occurs during program processing (e.g.,
multiprocessor stop, I/O not ready/STOP, error OB not
programmed etc.) before the program reaches the specified
breakpoint, the CPU goes into the STOP mode immediately. If
you execute a COLD RESTART or a MANUAL WARM
RESTART, the "program test" function is still in effect and the
breakpoint is still set.
•• Program processing at breakpoint (RESTART/RUN) → STOP
mode:
If stop conditions occur at the breakpoint or following breakpoint
during program processing, the CPU goes directly into the soft
STOP mode and outputs the data.
If you do not specify a new breakpoint while the CPU is in the
STOP mode, the "program test" function is still in effect after the
restart.
•• Wait state → STOP
Causes of interrupts occurring in the WAIT STATE (e.g. MP-STP,
PEU, I/O not ready, stop switch) or resulting from the previous
operation (error causing the CPU to stop) are registered, however,
the CPU remains in the WAIT STATE. The causes of interrupts
only bring about a transition to the STOP mode after you have
specified a new breakpoint in the WAIT STATE and the CPU has
exited the WAIT STATE. The specified breakpoint is not reached.
If you then carry out a RESTART (COLD RESTART or
MANUAL WARM RESTART) the new breakpoint remains set.
Note
If you switch the CPU to stop using the stop switch while it is in
the WAIT STATE, it only goes into the STOP mode after exiting
the WAIT STATE.
If causes of interrupts bring the CPU to the STOP mode during
the PROGRAM TEST, the PROGRAM TEST function (and any
breakpoint you may have specified) remain active after the restart.
11
PG Functions
CPU 928B Programming Guide
C79000-B8576-C898-01
11 - 15