Cautions in using system symbols

The preceding rules mean that some forms of command input will probably not produce the results you want:

1. Symbolic variables before or in a command name remain unsubstituted. The system will process the command with the “&variable;“ in the text, and probably generate a “COMMAND INVALID” error message.
2. If a command exit changes the text and adds a new symbolic variable, the system executes the command before substituting for the variable.
3. The following considerations apply when a command affects systems other than the one issuing it:
   • Except for REPLY, the substitution will reflect the issuing system. For example, if

     SYSVAR1 = (1,2)

     on the system issuing the following VARY command, but

     SYSVAR1 = (3,4)

     on a system with the console “consname” attached, the command

     VARY CN(consname),ROUT=&SYSVAR1

     would result in the console “consname” receiving codes 1 and 2. If this (unlikely) command is what you want, you should ROUTE it to the system with consname attached.
   • The same logic applies to commands that accept the “L=name-a” parameter, that is, where you want the command output messages directed to a console (and display area) other than the one issuing the commands. Substitution of symbolic variables in commands occur on the systems where the commands are issued, not where the “L=” console is attached.
   • Do not use symbolic variables in the “L=” parameter on the ROUTE command. See the ROUTE command description.
   • Understand the implications of using system symbols in commands that flow through several systems in a multisystem environment. See “Sharing Commands That Flow Through Multiple Systems” in z/OS MVS Planning: Operations for more information.