Saving Events

Events that you create for a program are automatically maintained when you reload the same program during a Prism session. This saves you the effort of redefining these events each time you reload a program.

Note these points:

• Prism prints a warning message if it can't maintain an event--for example, because the event is supposed to occur at a source line that no longer exists. Obviously, changing the program can also change the meaning of events; a breakpoint set at line 32, for example, may still be a valid event, but it may not be the event you want if you have deleted lines earlier in the program.

• Disabled events become enabled when a program is reloaded.

• Events are deleted when you leave Prism.

To use Prism commands to save your events to a file, and then execute them from the file rather than individually:

1. Issue the show events command, which displays the event list.

   Redirect the output to a file. For example,

show events @ primes.events

(See " Redirecting Output" for information on redirecting output.)

1. Edit this file to remove the ID number at the beginning of each event.

   This leaves you with a list of Prism commands.

2. Issue the source command when you want to read in and execute the commands from the file.

   For example,

source primes.events