Skip to main content

Communication problem between MFA server and CICS in Enterprise Server

  • March 24, 2015
  • 0 replies
  • 0 views

Problem:

The customer tries to setup a connection from Enterprise Server to Mainframe CICS Region using MFA Server and SysC.
In the ES CICS Region the SysC never gets Active, and when they try to use CRTE transaction, it returns the following error: DFH4410 System MFA1 was not located.

Solution:

Firstly we made the following verification of the customer's configuration:
1) On Mainframe site, MFA Server:
- In the MFA.CNTL PARMS member enable the MCO feature:
MCO FEATURE=YES

This is for the CICS support.

- LUNAME in  MFA.CNTL SERVERS
This should correspond to the CICS region VTAM APPLID on the Mainframe.


2) On Enterprise Server site:
- Regading the SysC definition:
Is the SysC group in the CICS startup list?
The SysC should be in the Active resources in order for the connection to be made.
And the group should be in the startup list of the CICS.

Here is what should be placed in the SysC options:
MF Node: should be the IP address or domain name of the mainframe running the MFA Server
MF Port: the port on which the MFA Server is listening
Net Name: the APPLID of the mainframe CICS region
Session Max: The number of sessions that can use this connection (5 in this sample)

- Was a MSS Inter-System Communication Listener created for the Region?
What port was specified in the Endpoint Address?
The port should be set to the default one (*.*) or to (*.<MFA_Server_port>)

<MFA_Server_port> is the port on which MFA Server is listening.
By changing the port of the Listener the problem was solved and the SysC was in the ES CICS Active resources.


#SysCInter-SystemCommunication
#EnterpriseDeveloper
#MFDS

0 replies

Be the first to reply!