Paul Edwards <[log in to unmask]> wrote in article
<[log in to unmask]>...
 <<Snip>>
> The only way(after several hours of cold starts/cool
> starts/attempted purges) I found to disable PSMON was to remove all
> capabilities from the PRED group except IA and BA. Then on a restart it
> does not turn on. Why is this occuring? Has anyone had this problem?
> Just passed this to the response center during another call.

The following series of commands...

:sysdiag

*****************************************************************
******                                                     ******
******               ONLINE DIAGNOSTIC SYSTEM              ******
        <SNIP>
*****************************************************************

    Type "HELP" for assistance.

DUI >diagsystem showactive
   CURRENTLY ACTIVE DIAGNOSTIC SYSTEM PROCESSES
        Program Name             PID

          MEMLOGP                49
          PSMON                53
DUI >diagsystem abort 53

This will get rid of the process and release the files so the patch process
will replace them.

Mark Ranft