Advanced Topics › Command Processing › How You Create Linkages

How You Create Linkages

You can establish linkages to enable consoles, products, INTERNAL, INSTREAM, and TSO users to issue commands to any system. A linkage is referenced by the command source defined on the linkage. For an explanation of the LINK command and its parameters, see the Statement and Command Reference Guide. Use the following LINK command parameters to create a shared, dedicated, or exclusive linkage:

• Use the ADD parameter of the LINK command to indicate you are creating a linkage. If you specify ADD on a LINK command and the linkage already exists, then it is modified.
• Use the CONSOLE, TSOUSER, PRODUCT, SOURCE, INSTREAM, INTERNAL, or ALL parameter on the LINK command to enable a command source to issue cross-system commands.
• Use the SYSID parameter on the LINK command to restrict the target systems to which a command source can issue cross-system commands. Specify a single system ID, a list of system IDs, or a keyword specifying a group of systems.
• Use the AUTHORITY parameter on the LINK command to dictate the cross-system command authority level assigned to the command source. If the command source is an active MCS console, then the default cross-system command authority level is equal to the authority level that is currently assigned to the console by its SYS1.PARMLIB definition. If a console has MASTER authority, then the default is to allow it to have MASTER authority for cross-system commands as well.
• Use the TGTCONS or POOL parameters on the LINK command to define the type of linkage associated with the command source.

Examples: Creating Linkages

• To enable all local active MCS consoles to issue cross-system commands to any or all external systems, have CA MIC select target consoles from a shared console pool, and use the authority level of the command source (authority of the console issuing the cross-system command), issue the following command:

  LINK ADD ALL SYSID=EXTERNAL POOL=SHARE AUTHORITY=SOURCE
  

  You could omit POOL=SHARE and AUTHORITY=SOURCE because they are default values for the LINK command. ALL does not include extended consoles.

• To enable console MSTR to issue system control commands to system S2, and allow CA MIC to select and remove a target console from the console pool, issue the following command:

  LINK ADD CONSOLE=MSTR SYSID=S2 POOL=DEDICATE AUTHORITY=SYS
  

  You must make consoles available for the console pool on system S2 before console MSTR can issue commands through this linkage.

• To enable a local active MCS console named TAPECON to issue INFO, SYS, CONS, and IO authority level commands cross-system through target console SYSCMSTR on system SYSB, issue the following command:

  LINK ADD CONSOLE=TAPECON SYSID=SYSB AUTHORITY=ALL TGTCONS=SYSCMSTR
  

  Note: Console SYSCMSTR must be defined on SYSB before console TAPECON can issue commands to SYSB.

• To enable TSO CONSOLE user DA1GS21 to issue INFO authority level commands across systems, issue the following command:

  LINK ADD CONSOLE=DA1GS21 SYSID=ALL AUTHORITY=INFO
  

• To enable all consoles (real MCS or extended) with names beginning with ABC to issue MASTER, INFO, SYS, CONS, and IO authority level commands to all external systems, and select target consoles from a shared pool, issue the following command:

  LINK CONSOLE=ABC* SYSID=EXTERNAL AUTHORITY=MASTER POOL=SHARE
  

  Note: You can use the asterisk (*) or pound sign (#) wildcard characters only with the CONSOLE parameter.