Autopath Guidelines

The following is a list of guidelines for implementing the Autopath feature:

If the CA MIA component is running on the host z/VM system, Autopath sends commands from the z/OS GUEST systems, running CA MIA with Autopath enabled, to CA MIA running on the z/VM host, requesting CA MIA managed devices be attached or detached to and from the requesting z/OS guest system.
If you use native z/VM CP commands (meaning drives are not managed by CA MIA for z/VM on the host), it is not necessary to use the CA MIA for z/VM component to take advantage of the Autopath feature. Autopath on the z/OS guest uses CP commands to attach and detach drives.
If you use CP commands for some drives, the CA MIA component for some drives, and leave other drives outside of the control of Autopath, you can use the Autopath feature-Autopath supports this configuration.
If you have a system with drives connected to both native z/OS systems and to z/VM guest z/OS systems, Autopath can be used by the guest systems.
If you have only native z/OS systems, you cannot use the Autopath feature.

Two things affect the way Autopath operates:

Information in the MIMUNITS member
This information defines whether Autopath is to be used for each drive, and whether to use CP commands or a host resident release of CA MIA.

Note: If you are using both Autopath for z/OS and Autopath for z/VM, then devices must be defined as Autopath managed in both the MIMUNITS member for z/OS and the UNITS MIM file for z/VM.
Optional Autopath settings
All of these settings are accessible through the SETOPTION GTAF AUTOPATH= command. In addition, all of these settings can be individually changed for each z/OS system.

More information: