Rocket® Enterprise Developer (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.
To stop or kill a SEP
You can stop or kill a service execution process (SEP).
If you stop a SEP it will stop when the SEP has completed the current task. Stopping a SEP is most useful if an associated JCL is looping, or if it is a SEP with a debugger attached.
Killing stops the SEP when it is currently running a task. If the task terminates prior to the kill process being initiated, ESMAC returns a message explaining that the target task was no longer active.
Note: After stopping a process, Enterprise Server will automatically replace the SEP to
keep the configured number of SEPs - unless it is a debug SEP or a SEP that was started
from the command prompt. In these cases it will stop the SEP but not replace it.
To start ESMAC:
- Access the Enterprise Server Administration screen for your installation.
- In the table of enterprise server instances, check that the server you want has started, and if not, start it.
- In the Status column of the enterprise server instance to monitor, click Details.
The Details screen for the server is displayed.
- On the Details screen, select the tab, then click ES Monitor & Control.
The Enterprise Server Monitoring and Control (ESMAC) screen is displayed.
To stop or kill a SEP
- Click SEPs in the menu.
- Click Stop next to the SEP.
To kill a SEP
- Click SEPs in the menu.
- Click Kill next to the SEP.