Process Scheduler issue in Production

An issue we’re having with a job that is hanging most mornings when we start up our PeopleSoft Process Scheduler in production. The background on the issue we’re having with the .bat job that starts up the Process Scheduler each morning. That job is hanging and not completing most mornings. This has been a frequent issue ever since we implemented the Control-M scheduler.

The rmiregistry.exe 10120 is starting up under the ID that runs the batch job (MMACCT\LBPXROADS) and Control-M (batch scheduler system) won’t complete the job because that process never ends. Initial research seems to point to the idea that it’s not supposed to be creating a second rmiregistry.exe process in the first place.