IBM OS/390 User Manual
the MPF list can be customized to carry this out. For other automation tasks, IBM
provides several products to support workload and operational planning and
control:
provides several products to support workload and operational planning and
control:
•
TME 10 NetView, while many think of it as a network management product, is
also a robust automated operations product for detecting and reacting to
messages and alerts (for a wide variety of platforms), and carrying out
automated and monitoring actions. NetView can also provide an automated
interface with products such as TME 10 Information Management and
Performance Reporter for MVS, to integrate operations management data
with data from other systems management disciplines.
also a robust automated operations product for detecting and reacting to
messages and alerts (for a wide variety of platforms), and carrying out
automated and monitoring actions. NetView can also provide an automated
interface with products such as TME 10 Information Management and
Performance Reporter for MVS, to integrate operations management data
with data from other systems management disciplines.
TME 10 NetView also provides a central point of monitoring and automation
from/to other operating system platforms; for example, it can monitor and
detect a problem in a LAN Server or UNIX workstation that is required to
allow users to access OS/390 resident applications.
from/to other operating system platforms; for example, it can monitor and
detect a problem in a LAN Server or UNIX workstation that is required to
allow users to access OS/390 resident applications.
•
System Automation for OS/390 (SA for OS/390) is a NetView application for
automating scheduling, monitoring and recovery of various OS/390
workloads, ESCON I/O configurations, and local or remote OS/390 hardware
platforms. For example, it can be used to IML and IPL another OS/390
system, start in proper sequence a set of CICS and DB2 regions, alter an
ESCON director configuration, and provide a central workstation to monitor
what is running across one or more OS/390 systems.
automating scheduling, monitoring and recovery of various OS/390
workloads, ESCON I/O configurations, and local or remote OS/390 hardware
platforms. For example, it can be used to IML and IPL another OS/390
system, start in proper sequence a set of CICS and DB2 regions, alter an
ESCON director configuration, and provide a central workstation to monitor
what is running across one or more OS/390 systems.
30.5.3.1 Automating Operational Procedures
You should look at automating as many operational procedures as you can.
Automation will reduce human error and provide consistency to the procedure.
All of the operational procedures identified in the preceding section can be
automated to some degree by using things such as:
Automation will reduce human error and provide consistency to the procedure.
All of the operational procedures identified in the preceding section can be
automated to some degree by using things such as:
•
MVS facilities, such as exits, the Message Processing Facility (MPF) list and
Automated Restart Management.
Automated Restart Management.
•
An automated operation product, such as TME 10 NetView, System
Automation for OS/390, or a third party automation product.
Automation for OS/390, or a third party automation product.
•
Specialized products with automation interfaces, such as TME 10 OPC/ESA,
DFSMS, and TME 10 Information Management.
DFSMS, and TME 10 Information Management.
Automation should be planned and added in stages as your OS/390 environment
evolves. Both systems programming and operations personnel should be
involved. Procedures should be tested thoroughly before being put into
production. General types of activities you should consider automating include:
evolves. Both systems programming and operations personnel should be
involved. Procedures should be tested thoroughly before being put into
production. General types of activities you should consider automating include:
•
Console operations, such as suppressing messages and replying to WTORs.
•
Workload scheduling, such as starting up and shutting down online
subsystems and batch jobstreams.
subsystems and batch jobstreams.
•
Event detection, to quickly discover problems or potential problems that will
affect system availability (for example, the JES2 spool filling up.)
affect system availability (for example, the JES2 spool filling up.)
•
Monitoring performance and availability.
•
Distributing software - both system software and application output, such as
reports.
reports.
•
Data backup and restore for both system and application datasets.
Chapter 30. Systems Management Philosophy and Methodology
467