Skip to main content

Hi folks!

I made a simple client program in C to execute a transaction to MFES usingĀ CICS_ExternalCall function (casbnccl64) library in linux.

In the same instance of MFES (localy), I can run this sample program and execute the transaction with no problems, but when I execute same program from a remote instance get the following messages from the driver:

Wed 21 May 2025 04:43:33 PM CEST MccDoOpen: timeout connecting to server at MFNODE:22.123.1.2,MFPORT:23001
Wed 21 May 2025 04:43:33 PM CEST MccOpen: Error opening conversation: (15) timeout expired
Wed 21 May 2025 04:43:33 PM CEST MccDoClose: CCI error 3: An invalid CCI handle was supplied
Wed 21 May 2025 04:43:33 PM CEST MccClose: Error closing conversation: (8) communications component error

I read in any place that I need to establish the ES_ECI_SOCKET environment variableĀ  with IP and PORT of the MFES listener server but it doesn't work either.

Any help for that?

Thanks



------------------------------
Jose Antonio Romero
Mainframe Infrastructure System Architect
NTT Data
Barcelona ES
------------------------------

Hi folks!

I made a simple client program in C to execute a transaction to MFES usingĀ CICS_ExternalCall function (casbnccl64) library in linux.

In the same instance of MFES (localy), I can run this sample program and execute the transaction with no problems, but when I execute same program from a remote instance get the following messages from the driver:

Wed 21 May 2025 04:43:33 PM CEST MccDoOpen: timeout connecting to server at MFNODE:22.123.1.2,MFPORT:23001
Wed 21 May 2025 04:43:33 PM CEST MccOpen: Error opening conversation: (15) timeout expired
Wed 21 May 2025 04:43:33 PM CEST MccDoClose: CCI error 3: An invalid CCI handle was supplied
Wed 21 May 2025 04:43:33 PM CEST MccClose: Error closing conversation: (8) communications component error

I read in any place that I need to establish the ES_ECI_SOCKET environment variableĀ  with IP and PORT of the MFES listener server but it doesn't work either.

Any help for that?

Thanks



------------------------------
Jose Antonio Romero
Mainframe Infrastructure System Architect
NTT Data
Barcelona ES
------------------------------

Hi Jose,

I can see CCI errors being mentioned which typically means a network connection problem. Can you ping the remote machine?
I recommend you to consider raising a support case to seek assistance on this issue, it is likely that tracing is needed/requested for this.
When raising the case please generate and include a MFESDIAGS diagnostics collection for our review.

Regards,

Kim



------------------------------
Kim Hoskin
Mr
Rocket Internal - All Brands
------------------------------

Terms & ConditionsAccessibility statement