Managing Cross-System Command Traffic › Understanding Linkages › Identifying Command Sources on Linkages

Identifying Command Sources on Linkages

You can grant authority to a specific user or to a group of users on your system to issue commands that will be executed on another system by using the LINK command. Various features of the LINK command allow you to be as selective as you want to be. For example:

• To enable a specific local CMS user or service machine to issue cross-system commands, specify USER=userid on your LINK command. The userid variable represents the CMS user ID or service machine. You can allow all local users the ability to issue cross-system commands by specifying USER=ALL.

  The CA MIC z/OS LINK command uses the PRODUCT parameter to enable a product to issue cross-system commands. In z/VM, the PRODUCT parameter is not required. To enable a z/VM product to issue cross-system commands, simply use the USER parameter on the LINK command to enable the product service machine.

• To enable your own user ID to issue cross-system commands, you can omit the USER parameter on your LINK command. When the USER parameter is not specified, the linkage is created for the issuing user ID by default.
• You can define more than one linkage for a single command source. For example, you can enable CMS user USER1 to issue cross-system commands if you specify USER=ALL or USER=USER1 on your link command.
• CA MIC looks for a specific linkage for a command source (for example, USER=USER1) first and uses this linkage if it exists. If it does not find a linkage for that command source, the general linkage is used (for example, USER=ALL).

For information about identifying command sources for linkages on z/OS systems, see the CA MIC Message Sharing for z/OS Programming Guide.

Note: The LINK command parameters are flexible and powerful. They are capable of controlling access to CA MIC cross-system commands.