# EntireX RPC Server: Terminate Problems

**URL:** <https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [September 16, 2008, 2:55am UTC](https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012 "2008-09-16T02:55:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dieter\_W\_Storr](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/dieter_w_storr/32/91_2.png) [@Dieter\_W\_Storr](https://techcommunity.softwareag.com/u/Dieter_W_Storr)\
**Post date:** [September 16, 2008, 2:55am UTC](https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012/1 "2008-09-16T02:55:59Z")

</div>

As I reported earlier, we start now only one EntireX RPC Server job, which contains 5 tasks (NTASKS=5) and use TCP/IP for communication. Before, we started 5 Server jobs using SVC.

It was no problem to terminate the Server job by issuing the TERMINATE command through user exit (API) USR2071N. Now, with 1 job and 5 tasks, we have to terminate five times the server. Even one cancel command (CO) for the job won’t work. We have to do it five times.

Before the change, when the Broker ended, the Server also ended automatically. Now, the Server job is up and running but nobody can use the server.

Any ideas?

Dieter Storr

> **[Storr Consulting, Inc. - Index](http://www.storrconsulting.com)**
>
> Mainframe and PC Solutions, Software and Hardware, 
> Concepts, Design, Performance Analysis, Data Modelling,
> Teaching English and Art

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [September 16, 2008, 4:16am UTC](https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012/2 "2008-09-16T04:16:35Z")

</div>

This sounds like you are not using ADALNKR, which is a prerequisite for RPC servers with NTASKS \> 1, see

[url][http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat424mf/rpc/start.htm#start\_Considerations\_for\_Natural\_RPC\_Servers\_with\_Replicates[/url]](http://techcommunity.softwareag.com/ecosystem/documentation/natural/nat424mf/rpc/start.htm#start_Considerations_for_Natural_RPC_Servers_with_Replicates%5B/url%5D)

---

<div class="post-metadata">

**Author:** ![Dieter\_W\_Storr](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/dieter_w_storr/32/91_2.png) [@Dieter\_W\_Storr](https://techcommunity.softwareag.com/u/Dieter_W_Storr)\
**Post date:** [September 16, 2008, 6:06am UTC](https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012/3 "2008-09-16T06:06:19Z")

</div>

Thanks, Wolfgang.

I will discuss it with the system folks.

Dieter

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:50pm UTC](https://techcommunity.softwareag.com/t/entirex-rpc-server-terminate-problems/79012/4 "2021-04-02T14:50:53Z")

</div>