IBM OS/390 User Manual

Page of 673
Automated Operations - handles the complex operations job scheduling
procedures to ensure that work is completed in a timely manner.
Verifying that the resources needed for a scheduled workload are
available; for example, that the required disk or tape volumes are
available for a backup operation.
Planning to ensure the availability of day-to-day operations items, such
as printer paper, tapes, and control center equipment.
Specifying operations policies and procedures, preventive maintenance
schedules and procedures, and operations recovery procedures.
Supporting output delivery as defined by service-level agreements.
Workload control - distributes work-handling and work-processing
responsibilities across systems. It includes monitoring, analyzing, and
adjusting of work in those systems. Examples of these functions include:
Translating workload policies into system specifics.
Distributing workload policies to systems.
Receiving work requests and distributing them to systems, based on
needs and policies.
Managing resources needed for a workload for example, ensuring a tape
volume needed by a batch job is mounted and ready for use on a tape
drive.
Monitoring systems and resources to determine work progress.
Responding to queries about the status and progress of work.
Accepting, and responding to, notification requests for work-related
events, such as job termination.
Taking action on workload-related events, such as restarting or rerouting
work.
Managing the printing and delivery of hard copy output.
Operations control - applying operations policies for exception conditions,
resource shortages, and other situations.
30.5.3 Methodology
Operators must have documentation and tools to understand how the system
and workloads are supposed to be set up and run, the instructions to carry out
setup/execution tasks, information on what to monitor and look for, instructions
on what to do when something goes wrong, and a callout list of who should be
contacted for various situations. This information can be kept in a set of files or
in a PDS for starters; while it is popular to have hard copy 
run
″ 
books, these
are much more vulnerable to becoming out of date. In either case, a strong
maintenance process that is tied into the problem, change, and configuration
process is required to ensure accurate and up-to-date information.
Automating operational tasks is one of the most productive activities to carry out
in the OS/390 environment. Automation will reduce problem detection and
bypass time, eliminate human error, and support higher availability by carrying
out quicker recovery actions. Automation can also make operators more
productive by carrying out more mundane and repetitive tasks, monitoring for
situations, and doing initial recovery. One of the simplest tasks to automate is
message suppression, so that only critical messages are displayed at consoles;
466
VSE to OS/390 Migration Workbook