Managing Cross-System Command Traffic › Setting the Cross-System Command Authority Level › Authority for z/VM Linkages › Considerations for Establishing Authority Levels

Considerations for Establishing Authority Levels

The following lists some important considerations you should be aware of when establishing authority levels for cross-system commands on z/VM systems:

• Because all cross-system CP commands are executed on the MIMGR service machine, a command can execute only if the MIMGR service machine has the CP privilege class required to execute the command. For instance, if a user has the authority level to issue a cross-system CP command, but the MIMGR service machine on the target system does not have the necessary CP privilege class, the command cannot execute on that system.
• When the MI ATTACH and DETACH commands are issued across systems, the issuer is treated as a Class B user. Therefore, the user must use the Class B syntax for these commands.
• For CP commands (such as QUERY) that operate differently depending on the CP privilege class of the virtual machine, the commands will always execute with the privilege class of the MIMGR service machine.
• Certain CP commands should not be issued across systems. For example, commands such as IPL and LOGOFF causes CA MIM to terminate abnormally. Also, the CP SHUTDOWN command will shut down your entire system. Use the LINKAUTH MIM file to prevent this problem from occurring.

Note: If the MI ATTACH or DETACH commands are issued across systems to the target user ID * (asterisk), the device will be attached to or detached from the MIMGR service machine. Also, if the MI ATTACH command is issued across systems without a user ID specified, the device will be attached to the MIMGR service machine.

For more information on the AUTHORITY parameter, see the Statement and Command Reference Guide.