Managing Cross-System Command Traffic › Creating Linkages › Examples of Creating Linkages

Examples of Creating Linkages

Here are some examples of creating linkages:

• If you want to establish a linkage to enable TSO user USER1 on your z/OS system to issue commands to your VMSYS1 system using SYSTEM authority, issue the following LINK command on your z/OS system:

  LINK TSOUSER=USER1 SYSID=VMSYS1 AUTHORITY=SYSTEM
  

  The syntax of the LINK command is the same whether you are linking to a z/OS system or a z/VM system, but when the target is a z/VM system two additional authority levels (USERPRIV and OPERPRIV) are supported. For more information about the z/OS LINK command, see the CA MIM Resource Sharing for z/OS Statement and Command Reference Guide.

• If you want to enable CMS user MAINT on system VMSYS2 to issue commands to system VMSYS1 using OPERPRIV authority, issue the following command on system VMSYS2:

  LINK USER=MAINT SYSID=VMSYS1 AUTHORITY=OPERPRIV
  

  When cross-system commands are directed to a z/VM system, they always execute on the MIMGR service machine. Therefore, when creating a linkage to a z/VM system, there is no need to define a target console where cross-system commands will execute. The POOL and TGTCONS parameters of the LINK command are ignored when creating a linkage to a z/VM system.

• If you want to issue cross-system commands from a z/VM system to a z/OS system, you will need to use the POOL and TGTCONS parameters on the LINK command to identify the z/OS target console where the commands will execute. For example, to enable CMS user MAINT on the local system to issue commands to system SYS390 using MASTER authority and a shared console pool, issue the following command:

  LINK USER=MAINT SYSID=SYS390 POOL=SHARE AUTHORITY=MASTER