Hi,

Where I work we sometimes run into processes that for one reason or another we have to

stop proc/id=

Generally these processes are writing huge log files that are in danger of filling up disks with many users, and without stopping the process the log file cannot be deleted.

The problem is that sometimes these processes go into a suspended state (sh proc/id=/cont shows "SUSPEND"). Some of these suspended processes free themselves of their own accord and terminate, but others stay in memory. I've seen processes that went into suspend for weeks and months until the next reboot got rid of them. My question is (and I've seen this posted further down the board, though not exactly answered) how can a suspended process be forcibly terminated without requiring a reboot?

One method I've thought of using would involve going in to look at the individual threads (ana/proc) and messing around there, though that would probably be quite dangerous.

This annoying suspended state can also occur to processes that write to tape drives where the tape is removed while the drive is still locked by the process and being written to. This can lead to nasty situations while the OS and controller try to sort themselves out.

It's not possible...but
In any case the process go in suspend when it waiting a resource that is not available.
To check it you can use the command analyze/system:
find the process whit command
SDA> show summary
and check the resources in use:
SDA> show process/chann/ind=xxx
if the resource is a mailbox almost surely it's full, in this case you can empty it with a command:
type /out=NL: mailbox-name.