Hi,
1) In TXseries hp-ux V5.1 we have reciently developed new funcionalities to connect non CICS program to a CICS server region.
The problem that we are having is the sme as the "malsi TXSERIES" had "ECI to CICS call".
We alse use the ECI program provided by IBM to connect a program (a diferent one from the example) server via (ECi_ASYNC)(ECI_GET_REPLY), sometimes this ECI client program fails returning the "ECI_ERR_NO_CICS" error.

2)We are planning to migrate this application to TXSeries hp-ux 7.1 and I have this questions:
- Would we need to install/configure CICS Universal Client to make this ECI and cicsterm calls?
- We would make a lot of concurrently ECI calls in the system.
thanks,

Yes you will need to configure a CICS Universal Client connection to the TXSeries region.

I would advise that you use ECI_SYNC calls to TXSeries and not ECI_ASYNC. It may not seem obvious, but I have noticed in the past that the CUC is less efficient with ECI_ASYC calls compared to ECI_SYNC calls as the transaction rate increases. The CUC seems to run into threading issues as it tries to submit new requests and hold the responses from earlier calls until the client program makes the ECI_GET_REPLY call. When a client program makes many simultaneous ECI_SYNC calls, the CUC is able to start up threads (based on a CUC setting) and service all the requests without waiting for an individual reply before submitting the next request to CICS.

In one test scenario I did a few years ago, I found that I got significantly better throghput by using ECI_SYNC compared to ECI_ASYNC, so we decided to change the client program - it also has the advantage of being easier to program on the client side as you don't need to make another call to get the response.

Do you always get the ECI_ERR_NO_CICS messages or only on some calls? If the problem is intermittent, try switching to ECI_SYNC. If you always get the error then you probably have a setup problem.