Problem:

How is it possible to move Mainframe Access to a different LPAR?

Resolution:

In order to move MFA to another LPAR you must:

Ensure all MFA datasets are available to new LPAR. In most cases, this is not an issue because DASD is shared.

Update $MVSTCP in MFA INSTLIB:

LOCAL= <name of tcp/ip started task on new LPAR>

BIND=<IP address of new LPAR>

PORT=<port number assigned to MFA>

Run $MVSTCP. Ensure MFA loadlib is APF authorized. MFA should now start successfully on new LPAR.