VARY CN command

The VARY CN command is used to set attributes for MCS, Start of change HMCS, SMCS and extended MCS consoles. The command can also be used to change the state of a console. End of change

The command only changes the attributes of the console when the console is active. If the console is not active, message IEE871I is issued, and the attributes are not changed. LU and LOGON are two attribute exceptions and they can be changed for inactive SMCS consoles. The syntax of the VARY CN command is:

 
V CN{(*|conspec1[,conspec1]... )}
       [,AMSCOPE=([*][,name[,name]...])]
       [,AUTH={ALL|INFO|MASTER|([SYS][,IO][,CONS])}]
       [,AROUT=(rtcode[,rtcode]...)]
       [,DMSCOPE=([*][,name[,name]...])]
       [,DROUT=(rtcode[,rtcode]...)]
       [,INTIDS={Y|N}]
       [,LOGON={OPTIONAL|REQUIRED|AUTO|DEFAULT}]
       [,LU={luname|*NONE*}]
       [,MSCOPE={(*ALL)|{([*][,name[,name]...])}]
       [,OFFLINE[,FORCE]|,ONLINE[,SYSTEM=sysname][,FORCE]|[,STANDBY]
       [,SUPSBY={Y|N}]
       [,ROUT={ALL|NONE|(rtcode[,rtcode]...)}]
       [,UNKNIDS={Y|N}]

Note:

You do not have to put a single AUTH=operand, or a single MSCOPE= operand, or a single routing code in parentheses. You must put a single console in parentheses.
Active MCS/HMCS/SMCS/EMCS consoles can have their attributes changed. If the console is inactive, message IEE871I CN=consname NOT ACTIVE. CAN NOT CHANGE CONSOLE ATTRIBUTES is issued. Only the LU and LOGON attributes can be changed for a SMCS console that is inactive.
When LU=*NONE* is specified, the VARY command no longer requires the LOGON keyword to be specified with the LU keyword.
If the OFFLINE keyword was specified, then the following keywords cannot be specified:
- LU
- LOGON
Syntax error message ASA103I is issued for this incorrect combination of keywords.
If the OFFLINE keyword was specified, with other attribute keywords besides LU or LOGON, the OFFLINE will deactivate the console, but the attribute keywords will not execute. Message IEE871I will be issued.
In console services shared mode, the effect of the VARY attribute command lasts for the duration of the IPL. In distributed mode, the effect of the command lasts only for the duration of the console being active.

CN

Change the indicated authority for the specified console name(s). When you are uncertain of the current console names, enter a DISPLAY CONSOLES command; see Displaying console status information for further information on this command.

conspec1

Represents one of the following:

nnnnnnnn: The name of the console device.
*: The console that you are currently issuing commands from.

AMSCOPE

Adds one or more system names to the list of systems from which the console can receive messages. If you specify more than one system name, separate the names with commas.

You can also specify an asterisk (*), which means that the console is to receive messages from the system to which it is attached. If the console is later attached to a different system, the console will start receiving message from that different system. For example, specifying AMSCOPE(SYS1,SYS2,*) causes a console to receive messages from systems SYS1, SYS2, and the system to which the console is attached.

AUTH=

Specifies the system command groups that the console is authorized to enter. This command requires MASTER authority and might be protected with a security product OPERCMDS resource class with the MVS™.VARYAUTH.CN profile, which requires CONTROL authority. In addition, the MVS.VARY.CN profile, which requires UPDATE authority, must also be specified. Table 1 lists the commands and their associated groups.

MASTER: One or more specified consoles are authorized to enter all system operator commands.
ALL: One or more specified consoles are authorized to enter INFO, SYS, IO, and CONS commands.
INFO: One or more specified consoles are authorized to enter only INFO commands.
(SYS, IO, CONS): One or more specified consoles are authorized to enter INFO commands as well as SYS, IO, or CONS commands (depending on which commands you include). Enter them in any order.

AROUT=rtcode

The system is to add one or more specified routing codes or the routing codes in the specified range(s) to the routing codes already defined for the console. You can specify single routing codes (rtcode), ranges of routing codes (rtcode-rtcode), or a combination of single routing codes and ranges of routing codes on the same AROUT operand. For example, specifying AROUT(2,11-14,28) adds routing codes 2, 11, 12, 13, 14, and 28.

DMSCOPE

Deletes one or more system names from the list of systems from which the console can receive messages. If you specify more than one system name, separate the names with commas.

If the console currently is defined to receive messages from the system to which it is attached, you can also remove that definition. To do this, specify an asterisk on the DMSCOPE parameter.

For example, if you have issued VARY CN AMSCOPE(SYS1,SYS2,*), the console receives messages from SYS1, SYS2, and whatever system the console is currently attached to.

If the console is attached to SYS1, it receives messages from SYS1 and SYS2. Issuing VARY CN DMSCOPE(*) has no effect on the console until the console is moved to a system other than SYS1 or SYS2. When it is moved to the other system, the console does not receive messages from that system.
If the console is attached to SYS3, it receives messages from SYS3 as well as SYS1 and SYS2. When you issue VARY CN DMSCOPE(*), the console immediately stops receiving messages from SYS3.

DROUT=rtcode

The system is to remove the specified routing code(s) or the routing codes in the specified range(s) from the routing codes already defined for the console. You can specify single routing codes (rtcode), ranges of routing codes (rtcode-rtcode), or a combination of single routing codes and ranges of routing codes on the same DROUT operand. For example, specifying DROUT(2,11-14,28) deletes routing codes 2, 11, 12, 13, 14, and 28.

INTIDS=

Whether the specified console can receive messages which are directed to console ID zero. These messages are usually the command responses for internally issued commands.

Y: The specified console is to receive these messages.
N: The specified console is not to receive these messages. This is the default value.

LOGON=value

This allows the operator to change the unique LOGON value of the specified console. The LOGON attribute can also be changed for inactive SMCS consoles. The LOGON keyword cannot be specified when the OFFLINE keyword is specified. The LOGON value is one of the following:

OPTIONAL: Indicates that this console does not require LOGON
REQUIRED: Indicates that this console requires an operator to logon before issuing commands
AUTO: Indicates that this console is automatically logged on
DEFAULT: Indicates that this console is to use the LOGON specification on the DEFAULT statement

OPTIONAL, REQUIRED, AUTO and DEFAULT all mean the same as they do on the LOGON keyword of the CONSOLE statement in CONSOLxx. See z/OS MVS Initialization and Tuning Reference for more information.

This command requires MASTER authority and might be protected with a security product OPERCMDS resource class with the MVS.VARYLOGON.CN profile, which requires CONTROL authority. In addition, the MVS.VARY.CN profile, which requires UPDATE authority, must also be specified.

LU=

luname OR *NONE*: Allows the operator to change or turn off the predefined LU name of a SMCS console. See z/OS MVS Planning: Operations for more information on predefined LUs. This command is only valid for SMCS consoles. If the command is issued for a non-SMCS console, then message IEE044I is issued. If the console is active, the only LU value that would be accepted is the LU that the console is active on or *NONE*. If a different LU is specified for an active console, then message IEE045I is issued. The LU keyword cannot be specified if the OFFLINE keyword is specified. If the console is not active, any LU can be specified. This command requires MASTER authority. It might be protected with the RACF® OPERCMDS resource class with the MVS.VARYLU.CN profile, which requires CONTROL authority. In addition, the MVS.VARY.CN profile, which requires UPDATE authority, must also be specified.
Value Range: Is from 2 to 8 characters. The first character must begin with the letters A through Z or with a #, $, or @; the remaining characters can be A through Z, 0 through 9, or #, $, or @.

MSCOPE

In a sysplex, specifies which systems the console is to receive messages from.

*ALL: The console will receive system messages from all active systems in the sysplex.
*: The console will receive system messages from the system it is attached to.
name: The console will receive system messages from the specified system name or system names in the sysplex.

OFFLINE

Deactivates an MCS, Start of change

HMCS

or SMCS console and places the device in offline status (has the same effect as VARY device,OFFLINE for the device, when VARY device,OFFLINE is issued on the system where the console is attached). VARY CN(...),OFFLINE is sysplex-wide in scope, and does not have to be issued from the system where the console is active. Attributes specified with the OFFLINE keyword will not be changed. The OFFLINE will deactivate the console, but the attribute changes will be ignored. If LU or LOGON were specified, then message ASA103I will be issued (and the OFFLINE will not execute). Any other keywords, message IEE871I will be issued, but the OFFLINE keyword will deactivate the console.

Note:

For an HMCS console, VARY CN(consolename),OFFLINE is supported, but OFFLINE,FORCE is not supported. End of change

ONLINE

Activates a device defined in the CONSOLxx parmlib member as an MCS console. MVS determines the system on which to activate the console in the following order:

The system specified on the SYSTEM keyword (if you specify SYSTEM on the VARY CN command)
The system on which this console was last active (if the console was previously active)
The system specified on the SYSTEM keyword in CONSOLxx (if you specified SYSTEM on the CONSOLE statement in CONSOLxx for this device)
The system on which the command is processed.

VARY CN(...),ONLINE does not accept extended MCS or SMCS console names as input.

Note:

Using the VARY CN(consolename),ONLINE command to activate an HMCS console is not supported. End of change

If you specify a list of consoles, MVS attempts to process each console specified in the list:

If a console is already active, MVS issues the same message (the DISPLAY C output - message CNZ4100I) as when activating a console.
If a console is already active on another system (for example, if you specify SYSTEM=SYS1 and the console is already active on SYS2), then MVS issues message CNZ0005I.
If the console cannot be activated, MVS issues a message appropriate to the situation. There are a number of such messages, including:
- IEE025I (the console device has no logical paths)
- IEE274I (the console name is not defined as a console in the sysplex)
- IEE420I (the console is an extended MCS console)
- IEE606I (the console name is not defined on this system)

FORCE

Activates an MCS console even when the console is being kept offline by a configuration manager. If you issue the VARY CN,ONLINE command and receive a message indicating that the device is being kept offline by a configuration manager, you can issue the VARY CN,ONLINE,FORCE command if necessary.

The FORCE keyword can only be specified if ONLINE is also specified.

When specified with the OFFLINE keyword, it acts just like a VARY dev,OFFLINE,FORCE command.

STANDBY

Deactivates an MCS or HMCS console and places the device in standby mode. VARY CN(...),STANDBY is sysplex-wide in scope, and does not have to be issued from the system where the console is active. If the MCS console is offline, STANDBY will attempt to bring the device online and place it in standby.

If you specify STANDBY, no other operands are accepted. STANDBY is not accepted for SMCS consoles, the system console, EMCS consoles, printer consoles, subsystem consoles or consoles in status display (SD) or message stream (MS) mode.

SUPSBY=

Specifies if the specified console can be placed in standby mode:

Y: The specified console can enter standby mode.
N: The specified console should not enter standby mode. If the console is currently in standby mode, the command is rejected.

SUPSBY is not accepted for SMCS consoles, the system console, EMCS consoles, printer consoles, subsystem consoles or consoles in status display (SD) or message stream (MS) mode.

SYSTEM

Specifies the system on which the console is to be activated. SYSTEM overrides any default system specification (for example, the SYSTEM keyword on the CONSOLE statement). SYSTEM is valid only if you specify the ONLINE keyword.

The SYSTEM value applies to all values in the list of console names. If the system specified as the SYSTEM keyword value is not active in the sysplex, you will receive an error message.

ROUT=

The routing codes of messages the console(s) can receive. These codes replace those previously assigned. See Table 1 for a list of routing codes.

You can specify single routing codes (rtcode), ranges of routing codes (rtcode-rtcode), or a combination of single routing codes and ranges of routing codes on the same ROUT operand. For example, specifying ROUT(2,11-14,28) assigns routing codes 2, 11, 12, 13, 14, and 28.

Note: The system processes the ROUT, AROUT, and DROUT operands in the order that you specify them in the command.

ALL: The console receives all system-to-operator messages.
NONE: The console does not receive any system-to-operator messages.
rtcode: The console receives all messages with the specified routing codes. You can specify single routing codes (rtcode) or ranges of routing codes (rtcode-rtcode) on the same ROUT operand.

UNKNIDS=

Whether the specified console can receive messages which are directed to "unknown" console IDs. These IDs are one-byte IDs which the system cannot resolve.

Y: The specified console is to receive these messages.
N: The specified console is not to receive these messages. This is the default value.

Example 1:

To assign master level authority to an active console named REMOTE, enter:

VARY CN(REMOTE),AUTH=MASTER

Example 2:

To limit active console CON3 to receiving unsolicited messages from only systems SY3 and SY4, enter:

VARY CN(CON3),MSCOPE=(SY3,SY4)

Example 3:

To add SY2 to the list of systems which will send unsolicited messages to active console CON3, enter:

VARY CN(CON3),AMSCOPE=SY2

Example 4:

To activate consoles FRED and STAN, enter:

V CN(FRED,STAN),ONLINE

Example 5:

To activate consoles ABLE and BAKER for use on system SYS1, enter:

V CN(ABLE,BAKER),ONLINE,SYSTEM=SYS1

Example 6:

To activate console FRED, and at the same time to authorize FRED to enter informational, console control and system control commands, and receive messages for the primary operator, the tape pool, and the tape library, enter:

V CN(FRED),ONLINE,AUTH=(CONS,SYS),ROUT=(1,3,5)