There have been some changes in the way that Mainframe Access is configured.
The first is combining MFA Server and the z/Server feature into a single installation package called Mainframe Access.
The second is that Mainframe Access Server now uses a XML configuration file, this has many benefits such as:
Micro Focus recommends using the new XML configuration file for new installations and have provided a command line migration utility that takes your old MFA Server configuration files (and z/Server XML configuration file, if required) and produces a new equivalent XML configuration file for you to use. See Migrating old configurations to new XML configuration for more information.
The new XML configuration file also contains the configuration required for the z/Server feature. It has strict requirements that you must be using the unified scheduler (and not the legacy STC Scheduler or CEA Scheduler) and that the holder task must be started as part of MFA Server and not be a standalone address space. Migration actions for these changes can be found in the Micro Focus Enterprise Developer 3.0 product Help.
Legacy configuration files are still supported (for both MFA Server and z/Server) and you are not required to change any of your existing JCL procedures. If you want to continue to use them, full details of their use are contained in the Micro Focus Enterprise Developer product Help.