z/OS MVS Planning: Operations
Previous topic |
Next topic
|
Contents
|
Contact z/OS
|
Library
|
PDF
Contents (exploded view)
z/OS MVS Planning: Operations
SA23-1390-00
Abstract for MVS Planning: Operations
z/OS Version 2 Release 1 summary of changes
Planning MVS operations
Operations goals
Operating environment
Multiple console support and the MVS environment
Operation modes of console support
Shared mode
Distributed mode
Planning for distributed mode
Migration and fallback considerations
Sysplex operating environment
Using MCS, HMCS and SMCS consoles in a system or sysplex
Extended MCS consoles
Extended MCS consoles and console attributes
Defining and protecting extended MCS consoles
Defining console attributes for extended MCS consoles
MCSOPER and OPERPARM
SDSF and MVS operations planning
RMF and MVS operations planning
IBM OMEGAMON z/OS Management Console and MVS operations planning
Tivoli OMEGAMON and MVS operations planning
Automated operations and z/OS operations planning
Tivoli NetView for z/OS
Tivoli System automation for z/OS
Tivoli workload scheduler for z/OS
Remote operations and MVS operations planning
ESCON, FICON, and operations planning
Defining console configuration
Console considerations for z/OS V1R8 and higher
Choosing how to define your console configuration
Using CONSOLxx
CONSOLE statement
INIT, DEFAULT, and HARDCOPY statements
CONSOLxx and the sysplex
Sharing a single CONSOLxx member for all systems
Using unique CONSOLxx members for each system
Defining all consoles in the CONSOLxx member of the first system to Join the sysplex
SMCS console considerations
Installing SMCS
Defining SMCS to VTAM
Updating CONSOLxx
Starting the SMCS application
Changing APPLIDs
Using VTAM generic resource names
Changing GENERICs
Defining SMCS consoles
Predefined LU and LOGON
Changing LOGON
Changing the predefined LU
Providing security for SMCS consoles
Userids
Commands
Application ID
Console
Network
Activating an SMCS console
Deactivating an SMCS console
Removing console definitions from a configuration
Sample invocation of IEARELCN
Environment
Return and reason codes
Removing extended MCS console definitions from a configuration
Sample invocation of IEARELEC
Environment
Return and reason codes
Defining devices as MCS, HMCS or SMCS consoles
Devices MVS can use as MCS consoles
Using console names
Using console names in a sysplex
Restrictions for console names
Attaching consoles to particular systems in a sysplex
Planning console recovery
Recovery considerations
Console recovery and the RESET CN command
Planning console groups
Activating CNGRPxx
Display of synchronous messages
Considerations using consoles to display synchronous messages
System console automatic activation
Recovery for consoles
System problems
Console hardware errors
System programming problems
Recovery actions for an error message in the message area
Recovery actions for a lack of console activity
Console message backups
WTO buffer backup
WTOR buffer backup
Notes about console message backups
Recovery actions for a WTO buffer shortage
Recovery actions for a WTOR buffer shortage
Recovery actions for command flooding indications
Console hardware errors
Recovery actions for error messages centered on the screen
Recovery actions for a locked keyboard
Actions to see system messages at the system console
Planning console security
Controlling command authority with the AUTH attribute
Assigning a console master authority
Using RACF to control command authority and operator logon
Using RACF to authorize console operators and command use
Defining RACF profiles
RACF access authorities
Defining users with RACF
Defining TSO/E users of extended MCS consoles with RACF
Defining commands with RACF
Defining consoles with RACF
Setting DEFAULT LOGON requirements for MCS, HMCS and SMCS consoles
Setting LOGON requirements for individual MCS, HMCS or SMCS consoles
Automatic LOGON
Required LOGON
Optional LOGON
MVS commands, RACF access authorities, and resource names
Other ways to control command authority for consoles
Planning console functions for operators
How to control the use of an MCS console
Examples of MCS console screens
Defining the USE attribute
Message display and the full-capability console screen
Specifying automatic message deletion for MCS, HMCS or SMCS consoles
Temporarily suspending the screen roll
Comparison of roll, roll-deletable, wrap modes, and HOLDMODE
Manual deletion of messages
How operators specify message numbering
Using SEG to delete groups of messages from the screen
Status displays and MCS, HMCS and SMCS consoles
Setting up out-of-line display areas on a console
Where to route status displays
Controlling the format of messages and status information on console screens
Displaying jobname, data set status, and TSO/E information
Adding information to mount messages
Defining PFKs and other command controls for consoles
Setting up PFKs for consoles
An example of defining a PFK table
Defining the command delimiter for full-capability consoles
Hardcopy processing
The hardcopy message set
Characteristics of the hardcopy message set
Defining the hardcopy message set
Printing the hardcopy message set
The hardcopy medium
Hardcopy processing
Format of hardcopy records
Using OPERLOG
Using SYSLOG
SYSLOG MPF flags
Hardcopy failure
Temporarily disabling the hardcopy medium
Managing messages and commands
General characteristics of messages and commands
Message and command routing
Message flow in a system
Command flow in a system
Command flooding
Message and command flow in a sysplex
Messages in a sysplex
Message recovery following system failures
Commands in a sysplex
Command flow, CMDSYS and CPF in a sysplex
Command flow and the ROUTE command in a sysplex
Command flow and the L= Operand in a sysplex
Routing messages
Defining routing codes
Handling messages without routing codes
Defining message levels for a console
Specifying message levels and routing codes for a console
Directing messages from other systems to a console in a sysplex
Replying to messages from other systems in a sysplex
Directing messages that are eligible for automation to extended MCS consoles
Receiving messages that are directed to console ID zero
Receiving messages that are directed to unknown console IDs
Routing commands
Using CMDSYS on the CONSOLE statement
Using the ROUTE command
Using the command prefix facility
Defining a system name as a command prefix
Using the L=Operand on certain commands
Sharing system commands by using system symbols
What are system symbols?
What are wildcards?
Planning to share system commands
Sharing commands that flow through multiple systems
MPF and MVS operations planning
Specifying MPFLSTxx members
Using MPF to handle foreign messages
MPF options
Specifying message presentation
Suppressing messages
Retaining messages
Action message retention facility
Using MPF to retain messages
Displaying information about messages awaiting action
Grouping messages by function
Selecting messages for automation
Automation in a sysplex
Installation exits for messages and commands
IEAVMXIT and message processing
Message processing exits other than IEAVMXIT
Command installation exits
Considerations for a sysplex
Considerations for system symbols
CNZ_MSGTOSYSLOG exit
CNZ_WTOMDBEXIT exit
Monitoring messages
Enabling message monitoring
Disabling message monitoring
Controlling WTO and WTOR message buffers
Controlling reply IDs for WTOR messages
RLIM and RMAX values
Reply IDs and RMAX
Controlling automatic ending of Multi-line WTO messages
Aggregating messages returned to the ROUTE command
Appearance of aggregated messages
Controlling write-to-log (WTL) message buffers
Handling translated messages
Steps for providing translated messages
Allocating storage for a run-time message file
Compiling message files
Invoking the message compiler
Using JCL to invoke the message compiler
Using CLIST to invoke the message compiler
Using REXX to invoke the message compiler
Example of running the message compiler
Message compiler return codes
Controlling MMS through installation exits
Using parmlib to control message translation
Using MMSLSTxx statements
Using CNLcccxx
Using the INIT statement on CONSOLxx
Activating MMS
Summary of MVS message and command processing services
Message flooding
z/OS Message Flood Automation
Operation
Message flood detection behavior
Message Flood Automation and CONSOLxx parameters
Message Flood Automation and MPFLSTxx parameters
Message Flood Automation and the Subsystem Interface (SSI)
Message Flood Automation and EMCS consoles
Limitations
Operator commands
PARMLIB specifications
SYSLOG records
SYSLOG message ordering
Recovery
Other information
Migration
Migrating from one level to another
Initializing Message Flood Automation
Interpreting message rate information
Setting thresholds based on message rates
Shutting down Message Flood Automation
Defining auto-reply policy for WTORs
Migration
Operator commands
PARMLIB specifications
Displaying WTORs being monitored by auto-reply processing
Auto-reply notification messages
SDSF support for auto-reply policy
Planning for operation tasks
Initializing the system
The system console and message processing
Using the system console
Using the AUTOACT console group
Specifying LOAD information
The NIP console
The system console and CONSOLxx
Using AUTOACT with the system console
Naming the system console
The system console during normal operations
Problem determination and the system console
The system console in problem determination mode
Establishing console attributes for problem determination mode in CONSOLxx
Changing console attributes through commands
Messages that the system console receives in problem determination mode
Example of controlling problem determination mode for the system console
Specifying the time-of-day clock and the JES subsystem
CLOCKxx and the sysplex
Setting the TOD clock accuracy monitor service
Handling wait states
Interacting with system functions
Device allocation
Considerations for operators
Hot I/O detection
Considerations for operators
Device boxing
Considerations for operators
Controlling shared DASD
Specifying shared DASD mount characteristics
Considerations for operators
IPLing a system that shares DASD
Using the automatic IPL function
Wait state action table (WSAT)
Exploiting dynamic CPU addition
Exploiting the z/OS IBM System z Advanced Workload Analysis Reporter (IBM zAware) for OPERLOG
Examples and MVS planning aids for operations
Summary of CONSOLxx and commands to change values
Controlling extended MCS consoles using RACF
Defining the user profile of an extended MCS console
Granting the user access to the RACF OPERCMDS class
Allowing a TSO/E user to issue the CONSOLE command
Changing console attributes using RACF
Using RACF to control APF lists
Command authorization
Defining command profiles
Controlling how to add or delete APF list entries for a library
Controlling how to change the APF list format
Using RACF to control dynamic exits
Command authorization
Defining command profiles
Controlling defining a dynamic exit
Controlling adding, modifying or deleting exit routines
Controlling how to undefine a dynamic exit
Controlling how to obtain a list of the dynamic exits
Controlling calling of routines of a dynamic exit
Controlling recovering of dynamic exit processing
Using RACF to control LNKLST concatenations
Command authorization
Defining command profiles
Controlling defining a LNKLST set
Controlling adding a data set to a LNKLST set
Controlling deleting a data set from a LNKLST set
Controlling removing the definition of a LNKLST set
Controlling testing of a LNKLST set
Controlling updating of a Job's LNKLST set
Controlling activation of a LNKLST set
Using RACF to control dynamic LPA
Command authorization
Defining command profiles
Controlling adding a module to LPA after IPL
Controlling deleting a module from LPA after IPL
Managing messages with a console cluster
Setting up and using a console cluster
Defining routing codes for the consoles
Defining the operating modes and the message levels for the consoles
Setting up display areas
Setting message roll rates and message deletion specifications for the consoles
Setting up a periodic display of outstanding requests
Defining PFKs for CON1
Summary of the PFK definitions for the cluster
Activating the PFK table
Summary of contents of CONSOLxx for the cluster
Defining a console configuration for a sysplex environment
Planning your console configuration for each system
Console groups for the sysplex
Defining CONSOLxx for each system
AUTOR00 parmlib member
Copyright IBM Corporation 1990, 2014
z/OS MVS Planning: Operations
z/OS MVS Planning: Operations
Copyright IBM Corporation 1990, 2014
