Here we have two utilities. The first is an updated POOL program
which will print out a list of active tasks which may be aborted (if and
when a POOL crunch occurs). The second is a task which may be scheduled
to run periodically to clear 'deadwood' out of GEN. If a task is stopped
and has no outstanding I/O and it is checkpointable, it will be checkpointed
out by CKP. This has the advantage of periodically compacting core, removing
tasks lying around in stopped state waiting for an offspring's status to
be returned, and saving POOL space( a task in core has it's header in POOL).
Since, I have not tried this version of CKP on any other system but mine,
and since it is a privileged task, be careful. Try it out standalone.
We use a version of it scheduled to run every 2 minutes, and it seems to
work just fine. Our version is not applicable to a standard V3.2 system,
so the enclosed source file has been modified so it will supposedly run
on a standard V3.2 BL26 system. Sadly, we no longer have a 'standard'
V3.2 system lying around on a disk.

There are times when one realy wants to stop the execution of
a task. As is well known, the STP command will not always do this and
it is slated for removal as an MCR command. The HALT command is provided
as an example of how to absolutely stop the execution of a task. Of course
the task gets frozen in memory and will not checkpoint (unless you go
and add some lines of code in REQSB.MAC). Again this is a very privileged
task, which has not been tried elsewhere. Use at your own risk, and test
it carefully. It does, however, work on our system.

GOOD LUCK,

Jim Downward
KMS FUSION, INC
PO Box 1567
Ann Arbor, Mich. 48104
(313)-769-8500
29-Oct-80