z/OS MVS Planning: Operations
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Defining console attributes for extended MCS consoles

z/OS MVS Planning: Operations
SA23-1390-00

If your installation uses RACF® to protect extended MCS consoles, RACF maintains information about the console attributes in the OPERPARM segment of each RACF user profile. You can define or alter these attributes using the RACF ADDUSER or ALTUSER commands.

Table 1 shows the console attributes that your installation can control for users of extended MCS consoles. It lists the console attribute, the subkeyword in OPERPARM if you are using RACF, the default value if you do not specify RACF OPERPARM and do not define values through MCSOPER, and the meaning of the default. Notes® follow the table:

Table 1. Console Attributes for MCS and Extended MCS Consoles
Console Attribute RACF OPERPARM Subkeyword Default value Meaning of Default
Command authority for the console AUTH AUTH(INFO) Only informational commands can be issued.
Routing codes for the console ROUTCODE

See Note 3

ROUTCODE(NONE) No routing codes established for the console.
Levels of messages directed to the console LEVEL

See Note 3

LEVEL(ALL) All levels of messages sent to the console.
Message format for console display MFORM MFORM(M) Display only the message text.
System message scope in the sysplex MSCOPE

See Notes 2
and 3.

MSCOPE(*ALL) Display messages from all systems in the sysplex on the console.
Command association in the sysplex CMDSYS CMDSYS(*) Commands are processed on the local system where the console is attached.
Jobname and TSO/E display information MONITOR None No default; monitors jobname and TSO/E information for screen displays. See Displaying jobname, data set status, and TSO/E information.
Logging of command responses LOGCMDRESP LOGCMDRESP(SYSTEM) SYSTEM indicates logging is controlled by the value in HARDCOPY CMDLEVEL in CONSOLxx. (NO indicates that the system does not log command responses if the response message was issued by an authorized program).
Storage limit for message queuing STORAGE STORAGE(1) Storage in megabytes that the system uses for message queuing to the console. The maximum is 2000 megabytes.
Whether the console receives delete-operator- messages (DOMs) DOM

See Note 4

DOM(NORMAL) NORMAL indicates that the system direct all appropriate DOMs to the console. (ALL indicates that all systems in a sysplex direct DOMs to the console. NONE indicates that DOMs are not directed to the console.)
Key name for the console

KEY
See Note 1

KEY(NONE) 1- to 8-byte character name used in DISPLAY CONSOLES,KEY. A key name allows you to group extended MCS consoles by function and refer to the group using the key name in the DISPLAY command.
Whether the console is to receive messages eligible for automation

AUTO

See Notes 2 and 3

AUTO(NO) NO indicates that the console does not receive messages specified for automation through MPF. (YES indicates that the console can receive messages eligible for automation.)
Receive messages directed to console id zero INTIDS N Whether the console receives messages directed to console id zero.
Receive messages directed to unknown console ids UNKNIDS N Whether the console receives messages directed to unknown console ids, such as one-byte id.
Receives the hardcopy message set HC N Whether the extended console receives the hardcopy message set
Note:
  1. Using the KEY name, operators can display information on the DISPLAY CONSOLES,KEY command for all extended MCS consoles defined with the same key.
  2. Using the AUTO keyword, you can define an extended MCS console to receive messages that MPF indicates as eligible for automation. These messages can originate on any system in the sysplex. By specifying AUTO(YES) and MSCOPE(*ALL) or the MCSOPER OPERPARM equivalents, an extended MCS console can receive these messages from all systems in the sysplex.
  3. Altering some console attributes might cause messages to no longer be displayed on a console. Messages that are not displayed on a console will still be logged in SYSLOG and/or OPERLOG, and are viewable using facilities such as SDSF.
    The potential for this situation to occur comes from using these commands:
    • VARY CN
    • VARY CONSOLE
    • CONTROL V,LEVEL
    • LOGOFF (for SMCS consoles)
  4. If the MCSOPER ACTIVATE request specified MSGDLVRY=NONE, the attribute specified or defaulted for DOM will be forced to DOM=NONE.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014