Migrating old configurations to new XML configuration

In order to ease migration from the existing MFA configuration files, including the existing z/Server XML configuration file, Micro Focus have provided a command line migration utility that performs the conversion for you.

The tool is called MFA Config Migration Utility (mfacmu), and can be executed from a Micro Focus Enterprise Developer command prompt by invoking mfacmu.exe. By executing the command with no parameters you should see the help as below:

Copyright(c) 2018 Micro Focus. All rights reserved.
MFA Config Migration Utility Version 1.0.0.1
Syntax Help:

mfacmu -Output <OutputPath> -Main <MFAMainTaskConfig> -Server <MFAServersConfig
> [-ZServ <zServerConfig> -ENDV <EndevorConfig> -AMSQ  <AMSConfig> -CHGX <Chang
eManConfig> -CGMQ <CGMQOTMAConfig>,<CGMQOTMAConfig>,... -Default <DefaultConfig
>] -Schema <ConfigSchema>

Where:

    <outputPath>        - The filename/location of the new config.

    <MFAMainTaskConfig> - The path to the MFA main task config.
    <MFAServersConfig>  - The path to the MFA servers config.

And optionally:

    <zServerConfig>     - The path to the zServer xml config.
    <EndevorConfig>     - The path to the Endevor config.
    <AMSConfig>         - The path to the AMS config.
    <ChangeManConfig>   - The path to the ChangeMan config.
    <CGMQOTMAConfig>    - A path to a CGMQOTMA config or comma delimited list o
                          f paths.
    <DefaultConfig>     - The path to a config to be used by all application se
                          rvers unless a specific one has been specified.
    <ConfigSchema>      - Path to the Config schema to validate against. when n
                          not set this defaults to finding the file in the prod
                          uct.

Examples:
mfacmu -Output newconf.txt -Main C:\Config\PARMS.TXT -Server C:\Config\SERVERS.
TXT

mfacmu -Output C:\Config\newconf.txt -Main C:\Config\PARMS.TXT -Server C:\Confi
g\SERVERS.TXT -ZServ "C:\zserver config\IVPXML.XML" -AMSQ C:\Config\PARMSAMS.TX
T

The job of mfacmu is to take your existing MFA configurations files from MFA Started Task, any other MFAAS Started Tasks and even the existing z/Server XML configuration file if used and convert that to a new valid XML configuration file that can be used straight away.

Before you use the utility you need to gather the following information:

  1. The PARMS file used by MFA Started Task. This is typically located in hlq.MFA.CNTL(PARMS), but can be found by looking at the XDBIN DD statement in your JCL procedure.
  2. The SERVERS file used by MFA Started Task. This is typically located in hlq.MFA.CNTL(SERVERS), but can be found by looking at the SERVERS DD statement in your JCL procedure.
  3. For each MFAAS Started Task (for Endevor, ChangeMan and AMS and so on) you will need the PARMSAS file. This is typically located in hlq.MFA.CNTL(PARMSAS), but can be found by looking at the XDBIN DD statement in your JCL procedure. You need to keep a note of the purpose of the MFAAS Started Task (ChangeMan or Endevor and so on) so that the correct file can correctly specified to the mfacmu tool.
  4. If you are using the z/Server feature you will need the existing IVPXML configuration file. This is typically located in hlq.ZSERVER.CONFIG(IVPXML), but can be found by looking at the CONFXML DD statement in your JCL procedure.

These files need to be download to your client ready for use by the mfacmu tool. For a typical installation you may have the following:

  1. MFA Started Task - MFA Server
  2. MFAS Started Task - Data Connect Server
  3. MFAAS Started Task - Endevor Application Server
  4. MFAAS Started Task - AMS Application Server
  5. z/Server - z/Server feature

In which case you have downloaded four files. PARMS and SERVERS from MFA Server, nothing from Data Connect, the PARMSAS file from Endevor and the PARMSAS file from AMS. It is entirely possible to use the same PARMSAS file for each MFAAS Started Task, in which case you will only need to download it once. You will also need to download the z/Server XML configuration file.

Download the files into the following structure:

MFA Server

Endevor

AMS

z/Server

Save the resultant XML configuration file as:

Invoke the mfacmu utility as follows:

mfacmu -Output C:\FILES\XMLConfiguration\MFAXML.xml -Main C:\FILES\MFAServer\PARMS.txt -Server C:\FILES\MFAServer\SERVERS.txt -ENDV C:\FILES\Endevor\PARMSAS.TXT –AMSQ C:\FILES\AMS\PARMSAS.txt –Zserv C:\FILES\ZServer\IVPXML.xml

The following or similar output is displayed:

Copyright(c) 2018 Micro Focus. All rights reserved.
MFA Config Migration Utility Version 1.0.0.1
ASTYPE parameter is now implicitly determined.
MTP004W: The following parameter has an empty value: DSNQUALIFIER_ENDEVOR=
    --- ENDEVOR DSN QUALIFIER
MTP003W: The following parameter statement is ignored, has no value: MFA_ACCEPT_
EMPTY_FILES         --- DOWNLOAD EMPTY DATA SETS (YES,NO)
MTP003W: The following parameter statement is ignored, has no value: MFA_GUI_BLA
NKPASSWORD          --- CLEAR PASSWORD FIELD (YES,NO)
MTP003W: The following parameter statement is ignored, has no value: MFA_GUI_IGN
OREUSERCTO          --- DISABLE INACTIVITY TIMEOUT (YES,NO)
MTP003W: The following parameter statement is ignored, has no value: MFA_JOBNAME
_CHECK              --- BATCH JOB STARTS WITH SUBMITTER'S ID (YES,NO)
MTP004W: The following parameter has an empty value: CHANGEMAN_SSID=
    --- CHANGEMAN SUBSYSTEM ID X ("SERX")
MTP004W: The following parameter has an empty value: CHANGEMAN_DSNQUALIFIER=
    --- CHANGEMAN DSN QUALIFIER
MTP003W: The following parameter statement is ignored, has no value:
TCP LINK FEATURE parameter is now implicitly determined.
MFA FEATURE parameter is now implicitly determined.
MCO FEATURE parameter is now implicitly determined.
REMOTE IMS FEATURE parameter is now implicitly determined.
ES/MTO OUTBOUND FEATURE parameter is now implicitly determined.
ASSERVER parameter is now implicitly determined.
ASGROUPID parameter is now implicitly determined.
ASSERVER parameter is now implicitly determined.
ASGROUPID parameter is now implicitly determined.
ASSERVER parameter is now implicitly determined.
ASGROUPID parameter is now implicitly determined.
ASSERVER parameter is now implicitly determined.
ASGROUPID parameter is now implicitly determined.
ASTYPE parameter is now implicitly determined.
ORGANIZATION parameter is now implicitly determined.
MAP002W: Attribute not in white list: MAX_PUBLIC_FILES
MAP002W: Attribute not in white list: CHANGEMAN_SSID
MAP002W: Attribute not in white list: CHANGEMAN_INTERFACE
ASTYPE parameter is now implicitly determined.
ORGANIZATION parameter is now implicitly determined.
MAP002W: Attribute not in white list: MAX_PUBLIC_FILES
MAP002W: Attribute not in white list: CHANGEMAN_SSID
MAP002W: Attribute not in white list: CHANGEMAN_INTERFACE
ASTYPE parameter is now implicitly determined.
ORGANIZATION parameter is now implicitly determined.
MAP002W: Attribute not in white list: MAX_PUBLIC_FILES
MAP002W: Attribute not in white list: CHANGEMAN_SSID
MAP002W: Attribute not in white list: CHANGEMAN_INTERFACE

Warnings have an error code ending in W and are yellow, these can be safely ignored. Errors have an error code ending in E and are red and need to be resolved. Contact Micro Focus support for assistance. An example of an error might be:

Copyright(c) 2018 Micro Focus. All rights reserved.
MFA Config Migration Utility Version 1.0.0.1
MCW001E: Unable to find schema. Config will be written but not validated.

The mfacmu tool returns 0 on success and 1 on failure. If the tool returns 1 then you need to contact Micro Focus support for assistance. On success the generated XML file can be used in your MFA Started Task JCL procedure by uploading it. You need to change the CONFXML DD statement to point to it.

You can now use the Mainframe Access Configuration Utility to view and modify this XML configuration file in a Web User Interface. See Mainframe Access Configuration Utility for more information.