IBM Automation Control for z/OS 1.1.1
IBM Automation Control for z/OS
Overview
© Copyright IBM Corporation 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Objectives
This presentation covers:
 the IBM Automation Control for z/OS and its capabilities
 the components of the product
 the product’s automation capabilities
 policy-based and goal-driven automation
Note:
• This presentation applies mainly to IBM Automation Control for z/OS but
also shows the differences toIBM Tivoli® System Automation for z/OS.
Functions not provided by IBM Automation Control for z/OS are in
underlined italic. The terms automation and the automation product are
used when there are no differences.
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-2
Agenda Tivoli System Automation
• Business Issue
• Automation Portfolio, History, and Evolution
• Automation Components
 Processor Operations
 System Operations
• System Operations Key Automation Technologies and Features
• Integration
• System Automation Details
 Policy based Automation
 Operator Interfaces
 Goal-driven Automation
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
3
Business issue
Application downtime affected by:
Cost per hour for being Down in M$
 Application complexity
 Application dependencies
Brokerage
Retail Sales
 CICS, DB2, IMS, network etc.
Pay per view
0
Standish Group
1
2
3
4
5
6
7
I/T Pressures
Outage Causes
Application
Failures
40%
40% 40%
40%
20%
20%
Technology Failures
 Heterogeneous environments
Operator
Errors





Application availability
Operations complexity and costs
Skills and education requirements
Automation implementation and maintenance costs
Rapid change of I/T
infrastructure
– Loss of business
– Loss of customers – the competition is just a mouse click away
– Loss of credibility, brand image, and stock value
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
System Automation family provides high
availability and disaster recovery
IBM only vendor to provide end-to-end, cross-platform automation
System Automation
Application Manager
Agentless Adapter
IBM PowerHA
Automation
Control for
z/OS
System Automation for z/OS
NetView
System
Automation for
Multiplatforms
C
F
z/OS
Veritas
MSCS
Unclustered
nodes
Linux, AIX
Linux, AIX, Windows
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
5
Automation evolution
1. Message filtering
2. Re-active message automation
3. Command-driven resource management
– Start, stop, recycle
– Parent–child dependency
4. Policy-based automation (vs. scripts)
5. Goal-driven application management
– Cluster-wide
– Complex dependencies
6. Disaster recovery
7. Pro-active, health-based automation
8. Composite application management
9. Adaptive automation
 Adapt to changed
configuration and goals
 Auto discovery
 Solve performance problems
before they cause outages
Policy-based automation
using best practices can:
 Reduce costs and
time-to-value
 Increase automation
degree
 End-to-end
automation
 Automation of
IEF123I
application
 Automated entities and their
dependencies
repetitive
 Message
within system
automation or complex and sysplex
tasks
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-6
IBM Automation Control for z/OS for the mid market
Based on the advanced automation technologies of Tivoli System Automation
and NetView® for z/OS, has no other pre-requisites, and provides:
• Automation, easier operations, and high availability for z/OS and local
hardware resources
• Policy-based automation reduces costs and implementation time
 Auto discovery and comprehensive plug’n play automation modules
• Lowered complexity through resource relationships and grouping
 Define and operate a complex business application as a single group
• Goal-driven automation
 Manages all automation resources such that goals are fulfilled
• Integration with z/OS ecosystem and many Tivoli products
• Easy installation and configuration with Configuration Assistance
• Secure, role-based operations
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-7
Comparison with System Automation for z/OS
Provides:
 NetView capabilities limited
to automation functions
 Single-system scope
 Processor Operations of
local CPC
 Best practice configuration
for improved time-to-value
System Automation for z/OS + NetView
Automation Control
Does not provide:
Sysplex support
End-to-end adapter
GDPS support
I/O-Operations
Unlimited interaction with
other Automation Control
systems in sysplex
Enterprise-wide Processor
Operations
Full access to NetView
Automation Table
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-8
Automation Control for z/OS - Components
System Operations
 Automate repetitive and complex tasks in single z/OS systems
Helps operators to perform their tasks in a more robust way
Reduces z/OS specific skill requirements
 Automated operations through monitoring of applications, messages, and
alerts: Increase availability and performance through pro-active automation
Processor Operations
z/VM
Blade Virtualization
Future Offering
AIX on
POWER7
Linux on
System x 1
Future Offering
Linux
on
System z
Optimizers
Smart Analytics Optimizer
z/OS
z/TPF
z/VSETM
Linux on
System z
Select IBM Blades
DataPower 1
HMC with zManager
System z Host
Automate and control hardware
operations on local CPC
Power on/off and reset
Blade Virtualization
System z PR/SM™
z HW Resources
Blade HW Resources
Support Element
zBX
Private data network (IEDN)
Perform system IPL for z/OS,
Linux, z/VM, blades
Automate local LPAR settings
like weights
and capping
IBM Software
Group | Tivoli Software
© 2013 IBM Corp.
1-9
Component Processor Operations
• Processor Operations provides external automation
• Automatic CPC & LPAR capacity changes
• zEnterprise Single Point of Control
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-10
Component Processor Operations
provides external automation
z/VM
PR/SM
HMC/SE
SNMP API
z/VSE
z/OS
z/OS
Linux
Central processor complex (CPC)
• LPAR startup, recovery, and
shutdown
• z/VM guest system support
• LPAR capacity & weight
management
• Power management
• IBM zEnterprise
management (zBX)
• Secured through SNMP V3
encryption and SAF
protected access
SA z/OS
ProcOps
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
11
Component Processor Operations
provides external automation
• External Automation
Central processor complex (CPC)
z/VM
PR/SM
HMC/SE
SNMP API
ProcOps
 IML & IPL (NIP time)
 Respond to System or Operator Console messages
including priority messages (synchronous WTORs)
 Set time of day clocks
 Detect and resolve wait states
 CPC capacity changes, powermode control
 Server Time Protocol and LPAR management
• Hardware status changes and alerts
• Single point of control for System z
• Ease of Use
 Common commands for:
• CPCs, LPARs, zBX blades, systems, and
z/VM guests
• z/OS, Linux, z/VM, z/VSE, z/TPF, zAWARE
 Easy to configure
 NetView and SNMP based, no PC required
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-12
12
ProcOps Hardware Management Console Tasks
13
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
Capacity in MSU
Do your own smart capping and load distribution
Group Capacity Limit
LPAR
LPAR
1
1
LPAR
2
LPAR
2 slow
LPAR
LPAR 3
3
Free, displaceable capacity
Software cost challenges:
• Charges based on peak rolling 4 hour
average or the LPAR Defined Capacity
whichever is lower
• Capping might cap priority workload
Solutions using SA z/OS:
• Move workload to under-utilized system
using server/move groups based on
 Predicted free capacity and WLM data
 Using OMEGAMON metrics
• Use ProcOps API to adjust capacity across
LPARs and WLM capacity groups
automatically
• Policy-based looping jobs resolution
System 1
System 2
System 3
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-14
Automatic CPC & LPAR capacity changes
• ProcOps Management API to:
 Query current CPC configuration details
 Query and set LPAR-specific controls
 Query and set the default CPC RESET activation profile
 Manage RESET, IMAGE, and LOAD activation profiles
 Automate IPLs from SCSI devices (Linux, z/VM)
• Allows you to automate based on schedule, workload,
application
– LPAR weight (defined, initial, minimal, maximal, current (R/O))
– Defined capacity to lower your software costs
– Provisioning of new CPs to adapt to increased workload
– Reserve of CPC (or reserve query)
– Switch between WLM and PR/SM management
– IPL profiles for easier operations
• ISQCCMD target_system_ProcOps_name ICNTL
target_hardware_name.lparname CMD(UPDATE) VAR(vnm)
IBM Software Group | Tivoli Software
VAL(vvl)
© 2013 IBM Corp.
1-15
zEnterprise Single Point of Control
• ProcOps zEnterprise support:
• Controls blades (incl. automated start/stop of virtual servers)
• Provides a command interface to operate the zBX entities
zEnterprise
• Dynamically discovers the virtual servers running on a blade
BladeCenter
 When blades are turned on, virtual servers can be started as well
Extension (zBX)
 Virtual servers can be stopped before turning off a a blade
• Collects configuration and status information of
the zBX and the associated resources
 Blade Centers and individual blades
ProcOps
ISQECMD via
HTTP
 Virtualization hosts (Hypervisors)
 Virtual servers
 Workload resource groups
incl. list of virtual servers assigned to the workload
 Ensemble Managing Primary HMC
• Allows to subscribe for asynchronous events
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-16
Component System Operations
• Architecture
• Summary of key automation technologies and features
• Example: Relationships – Starting an application
• Grouping concepts
• Automation in action
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-17
Component System Operations
Policy-based automation
OMNIbus
SA IOM
SDF
TEP
Configuration
Goals
Requests
Overrides
Status
Events
Policy
Automation Engine
Commands
Resources
Job/STC
UNIX
Logs
I/O
• Timers, events, triggers, service periods...
• Dependencies and groups
• Thresholds, active and external monitors
 JES, CICS, IMS, DB2, TWS, WebSphere,
OMEGAMON, UNIX, SAP, GDPS…
 Message monitoring & response
• WTO, WTOR, joblog, UNIX, NetView, hardware
 Escalation to SA IOM, OMNIbus...
Monitor
Applications
 Start, recover, and shutdown applications,
system and sysplex using:
 Prevent outages of critical resources:
Sysplex
System
• WTO and AMRF buffers, spool, sysplex
• SYSLOG, LOGREC, SMF, dump data sets
Easier operations at the application level
 3270 or Tivoli Enterprise Portal
 Single point of control, single system image
 Goal-driven automation
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-18
What can you automate?
• Automate messages from z/OS, applications, logs, hardware…
• Prevent outages of critical resources
• Start, recover, and stop z/OS resources
•
•
•
•
•
•
•
•
•
STCs, jobs…
UNIX System Services (USS) resources
Easier z/OS operations and monitoring
Change system run mode like day or night shift
Escalation of problems
Pro-active automation using integration with monitors
Integration with scheduling
Problem determination
DB2, CICS, and IMS automation
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
19
Summary of key automation technologies
Play
• Policy-based automation can replace scripts
• Plug and play automation using best practices
• Powerful sysplex-wide automation and operation
Web
• Goal-driven automation to keep applications in line with HasParent
ForceDown
MyWeb
business goals
VIPA
DB
• Grouping of resources for reduced complexity and
management at business application level
• Relationships between resources for accelerated startup and
shutdown, and correct recovery
• Manage by state, not by message
• Integration with monitors and OMEGAMON
• Health status can trigger pro-active automation
• Manager / agent design
• Same automation concepts enterprise-wide
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-20
Key automation features
• Comprehensive automation for z/OS and UNIX applications, for example:





User defineable start types and three stop types
Desired available status, startup and restart options
Warning and alert thresholds to stop recovery
Exception and captured messages
Monitoring of UNIX processes, files, and ports
•
•
•
•
•
•
•
Statuses: observed, desired, automation, startability, compound, and health
Automatic or manual move of entire application inside system or sysplex
Server group with availability and satisfactory targets and member preferences
Application pacing to avoid CPU peaks when starting bulk applications
Built-in ASCB scan monitor reduces CPU overhead for monitoring
Comprehensive automation infrastructure makes extension easy
Operator notification and alerting to SDF, SA IOM, OMNIbus, problem
management,…
• Special support for CICS, DB2, IMS, OPC, and LIFELINE
• Automation reports and availability and recovery time reporting
• No backup configuration required as policy implies all possible configurations
 Runmodes like e.g. normal and disaster recovery
 Non-disruptive cluster-wide policy activation synchronized with NetView automation table load
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
21
UNIX System Services (USS) automation
• Automation policy for USS resources
 Processes
 Files and file systems
 TCP Ports
/ (root)
tmp
mount usr
• Best practices policy for ftp, ssh,
inetd, syslogd, nfs, webserver...
• UNIX automation infrastructure to
…
File
System
Port 22
Files
Make
Available
HasParent
sshd
fork
ssh session
ssh session
ssh session
ssh
group
 Start and stop
 Monitor using start command, user ID,
and a filter (for uniqueness)
• Solution to fork problem uses process
ID, fast active monitor and z/OS events
to identify the right process
• Trap UNIX syslogd messages
• Security setup
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
22
Example: Relationships – Starting an application

Automation Control will…
Application PAYROLL uses a DB2 database
to access employee data
1 Start JES and RRS

JES
RRS
depends on
DB2 itself consists of multiple address
spaces. Required are:

MSTR, master address space

DBM1, services

IRLM, lock manager
DB2_IRLM
2 Start DB2
DB2_DBM1

DB2_MSTR
depends on
3 Start PAYROLL
PAYROLL


Policy
or…
For transaction processing the Resource
Recovery Services (RRS) address space is
needed
Most address spaces depend on the JES
subsystem
To ensure proper function of PAYROLL,
these dependencies must be considered
when PAYROLL is started
I want to start
PAYROLL
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-23
Grouping concepts
An Application Group (APG) is a manageable resource. Requests are propagated to its members.
The APG shows an aggregated state derived from the states of its members.
IMS1CTL
IMS1DLS
IMS1DBRC
Automation
Policy
BBOS001
BBOS002
BBOS00n
BASIC APG
SERVER APG
- all members must be
available to show the APG
available.
- Availability Target =
Number of members which
Automation Control tries to keep UP.
- Satisfactory Target =
Number of members to be UP
so that the APG is in UP.
Dynamically change of
Availability / Satisfactory
targets in runtime
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-24
Automation in action
1.Administrator uses plug and play modules to
10
Operator
create policy
End-to-end
2.Policy activated
Automation
New goal
Manager
3.Active monitor detects resource outage
9
Override
System preferences
4.Automation agent (AA) informs automation manager (AM)
5.AM decides recovery, based on dependencies, status, and
Status
Request
goals
Automation Manager
6.AM delegates execution to AAs
5 Keep in line with goals
7.AAs run, start, or stop commands, watch timeouts and
Check dependencies
success
Decide
Delegate
8.Resources recovered. AAs inform AM
Update status
9.Operator can change cluster or e2e goals
4
6
10.End-to-end automation manager takes care of end-to-end
Automation Agent
dependencies
2
Execute Orders
7
Issue commands
Policy
Timeouts
Resources
1
Relationships, Locations
3 Active monitor
Groups
Preferred systems
Goals
Timeouts ...
Set status
Commands
Monitor
8
Resources
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-25
Goal-driven automation
• What is goal-driven automation
• Goal-driven automation scenario
• Defining and overriding goals
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-26
What is goal-driven automation
• Policy defines goals
 Availability: available, unavailable
UP
DOWN
 Application group goals
• Operator can
 Change or override goals
 Create start or stop goals
• Goals are persistent
 Unlike the fire and forget command driven automation of other products
• Easier operations with a single action at application level
 Goals are propagated to group members and along dependencies
 Conflicting goals resolved by priorities and request sources
• Reduces operator errors
• Resource status adjusted to business goals, dependencies, configuration, and
status
 No need to define backup configurations
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-27
Goal-driven automation scenario
• Defines goals for group WebServer
 Nominal state is unavailable
• Operator creates start request
 Beats nominal state
• Goal is propagated to group
members and along
dependencies
• Automation starts required
CICS and DB2 first
• ApSrvr started after CICS and
DB2 are up
Observed
state by
monitor
Web-Server
Obs
Des
Nom
ApSrvr
HasParent
CICS
Web-Server
Obs
Des
Nom
ApSrvr
HasParent
CICS
Obs
Des
Nom
Obs
Des
DB2 Nom
Obs
Des
Nom
Obs
Des
DB2 Nom
Desired
state from
request
Nominal
state from
policy
•Propagated
along
HasParent
•Beats nominal state
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-28
Defining and overriding goals
• Administrator defines the "goals" for the application according to business
requirements in the policy:
 Desired state: Available (up), unvailable (down)
Batch
 Runmodes
Runtokens: NIGHT
 Availability schedule
Infrastructure
Runtokens:
BASIC
 Relationships (propagation)
 Application groups
Transactional
UP
DOWN
Runtokens: DAY
• Membership (propagation)
• Preferred systems or members
• Availability and satisfactory targets
• Automation Manager tries to keep the system in line with goals
 Problem states stop goal-driven automation and require manual intervention
• Easy, exception oriented operation
 Operator can "overrule" the policy goals by overrides or start/stop requests
• Responsibility moves from operation to automation administrator, but
 Operation is responsible for force requests and request removal
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-29
Policy-based automation
• The power of an automation policy
• Policy available out of the box
• Automation policy features
• Automation policy for applications
• Autodiscovery of the system
• Policy reports
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-30
What is the power of an automation policy?
Easier definition through ‘fill in the blanks’ panels
 Pre-defined automation for common applications
 Faster time-to-value
 Elimination of coding errors
 Easy to build ‘business view’
 More efficient use of scarce
‘people’ resources
Business System
Aggregated Resources
Resources
Consistent, reliable, automation actions
 Testing of abnormal condition actions is difficult and sometimes incomplete with
‘programming’ solutions
 Policy definitions can be re-used, copied and cloned for similar requirements
elsewhere in the enterprise
 Management of entire business applications, rather than individual resources
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-31
Automation policy features
• Resource models for: application, system, group, monitor, automation
operators, user...
• Autodiscovery of applications
• Plug and play automation using best practices




Define once, reuse identically or cloned
Supports z/OS system symbolics and AOCCLONE variables
Automation variables like resource or parent name
• Hierarchical application classes makes policy definition easier
• Easy one stop message automation
Link message to resource status
Tailored NetView automation (AT) and message revision table (MRT)
Creates SYS1.PARMLIB MPF member
Full flexibility to control AT, MRT and MPF artefacts out of the policy
•
•
•
•
•
•
Modifications of what is generated out-of-the-box
User-specific AT conditions with full syntax checking, but no overrides
Definition of sysplex, system, MVS, and application defaults
Documentation in web and flat file reports
Multiple users can browse or edit policy
Activity log for PDB changes
Web
SysOps
Control
File
Load




Build
• Enterprise-wide shareable and clone-able automation policy
Policy Database
Report

Applications and application classes covering all aspects from start/stop to messages,
groups, and dependencies
Easy to use and serviced by IBM
IBM best
Auto
practices discovery
Manager
Agent
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
32
Best practice policies provided by IBM
•
•
•
•
Covers z/OS, many applications, and automation
Structured collection of policies
Arbitrary selection of components
Smart import detects duplicates and allows rename
• DB2
• TWS
• WebSphere
• IMS
• CICS
• JES2 JES3
• USS
• ProcOps
• OMEGAMON
• GDPS
• SAPSRV
• More …
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
33
600+ predefined selectable messages
Component
zFS
APPC
BMC
CA
CICS
DB2
DFHSM
DFRMM
GDPS
GMFHS
InfoSphere
IMS
JES2
JES3
Lifeline
LDAP
MIM
MQ
NFS
OMEGAMON
OMVS/USS
OSA/SF
QFETCH
RACF
RMF
RODM
RRS
SDSF
SLS
TBSM
TPX
TSM
TWS
VPS
VTAM
WebServer
WebSphere
Description
Message prefixes
Unix File System for zSeries
(IOE)
Advanced Program to Program Communication
(ASB ATB)
BMC multiple Software Products
(BMC BBM)
CA multiple Software Products
(CAS ESF PXM)
CICS transaction server
(CTG DFH BBM)
DB2 database server for z/OS
(DSN)
Hierarchical Storage Manager
(ARC)
Removable Media Manager
(EDG)
GDPS and z/OS Hyperswap Services
(GEO IOS)
NetView Graphical Monitor Facility Host Subsystem
(DUI)
DB2 and IMS Queue Replication
(ASN CAC)
IMS database and supporting framework
(DFS CQS CSL DSNM)
Job Entry Subsystem 2
(HASP)
Job Entry Subsystem 3
(IAT)
Multi-Site Workload Lifeline
(AQS)
Lightweight Directory Access Protocol
(GLD)
CA MultiSystem Integrity Manager
(MIM)
z/OS WebSphere MQSeries
(CSQ)
z/OS Network File System
(GFS)
z/OS Omegamon Perform. Monitors (CND CSA EC ETE KM KN KO OMV)
z/OS Unix System Services (Open MVS)
(BPX)
zSeries Open Systems Adapter Support Facility
(IOA)
Unicenter CA-QuickFetch
(QFS)
Resource Access Control Facility
(IRR)
Resource Measurement Facility
(ERB)
NetView Resource Object Data Manager
(EKG)
Resource Recovery Services
(ASA)
System Display and Search Facility
(ISF)
SUN Microsystem Tape System Host Software Component
(SLS)
Tivoli Business Service Manager
(GTM)
CA Terminal Productivity Executive (VTAM appl)
(TPX)
Tivoli Storage Manager
(ANR)
Tivoli Workload Scheduler
(EQQ)
LRS VTAM Printer Support
(VPS)
z/OS Communication Server
(IST)
z/OS HTTP Server
(IMW)
z/OS WebSphere components
(BBO)
• On top of best
practices policies
• Selectable
• Serviced
• Service updates report
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-34
244 applications and application classes out of the box
 Zero effort, high quality
 Messages for the following components are shipped, self-configured, serviced
















z/OS ++
VLF
DLF
LLA
JES2 & JES3
VTAM & VPS
TSO
RACF
DFHSM
DFRMM
RDS
RRS
SDSF
FFST
RMF +
APPC & ASCH
 NetView +
 Automation








Manager +
SysOps
ProcOps
I/O Ops
GDPS +
OMEGAMON +++
TWS +
TSM
TBSM +
More messages &
components are
added permanently
(Development /
APARs)
















OMVS
TCP/IP
OMPROUTE
CRON
HTTP Server
RESOLVER
inetd
Portmapper
LDAP
NFS
ZFS
FTP
SSH
Syslogd
TN3270 +
OSA














MQSeries +
DB2 ++
IMS +
InfoSphere
FDR
CICS +
CMAS
IRLM
SAP +++
BMC products +
CA products +
CA TPX (Terminal
Productivity
Executive)
Sun tape system
WebSphere +
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-35
Automation policy for applications
•
•
•
•
•
Application is a z/OS subsystem, started task, application, batch job, or non-MVS resource
Special support for CICS, DB2, IMS, OPC, and LIFELINE
Transient job type for jobs that terminate themselves
Desired available status, startup and restart options
Monitor command and interval
 Built-in ASID scan monitor reduces CPU overhead for monitoring
• User defineable start types and startup parameters
 Automation can be start type sensitive
•
•
•
•
•
•
•
•
•
Three stop types: normal, immediate, and force
Start or stop can be with multiple commands and stages including init stages
External start or stop
Startup and shutdown triggers
Exceeded error thresholds can stop recovery
Target or source of relationships
Can be linked to application groups, service periods, runtokens
Messages to be automated or captured
Many more definitions for JES, WLM, ARM, automation symbols and flags, timeouts, owner,
infolink, notification
• IBM and user-defined Categories/Subcategories allow specific policy and filtering when
displayed
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
36
Autodiscovery of the system
• Simplifies & accelerates the PDB creation
using accurate models
• Gathers data about a customer system
environment
Best Practices
policy or user
supplied policy
 All address spaces including UNIX processes
• Generates PDB leveraging best practices
policy
 Allows manual adjustments
 Allows to refine and extend the
modelling process
• Distinction between
 Initial Load
 Re-discovery
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-37
Policy reports - Share what automation does
Automation
Policy
hyperlinked
Example of Policy
Database report
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-38
User Interfaces




3270 based operator dialogs
Status display facility (SDF)
Tivoli Enterprise Portal
System Automation Application
Manager
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
39
Key operations features
• Operations at the application level lowers complexity
– Automation takes care of dependencies and components
– Status aggregation that includes health status
• Goal-driven automation can reduce errors
– Goals are not changed by IPL
• Replace consoles with a single NetView console
 Dynamic Status Display Facility and powerful operator commands and dialogs
 Event and status history and logs
 Single point of control for up to three systems in the sysplex
 Parallel sysplex wide single system image
 Automation flags to switch automation on or off
• Scope can be system-wide down to single messages or transactions
• System IPL complete notification
• Web-based user interfaces
– Tivoli Enterprise Portal
– Tivoli System Automation Application Manager (SA z/OS only)
• Same operations concepts across your enterprise
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-40
Operator Interfaces
• 3270 based operator dialogs
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
41
Operator user interface – Status Display Facility
• Status Display Facility (SDF)
• Set of hierarchical panels with pre-defined or user-defined content
• Status changes are dynamically reflected on the panel and propagated up in
the hierarchy
• SDF can be used to
monitor status of
 Application software
 Outstanding operator
replies (WTORs) or
 user items
• Easy to setup
 Support to facilitate
customization and
generation of panels
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-42
Operator Interfaces
3270 based Status display facility (SDF)
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-43
Operator user interface – Tivoli Enterprise Portal
• Tivoli Enterprise Portal is the integration point for monitoring
 OMEGAMON XE
 Tivoli Monitoring
 Tivoli composite application monitors
• Automation Control adds its operational views
to the TEP presented side by side with
availability data
• Capabilities
 Resource overview, health and status item
workspaces
 Situation monitoring and visualization
 Graphical summaries combined with
detailed tabular views
 Context-sensitive linking between
workspaces
 Display critical messages and WTORs
 Display topology view
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-44
Tivoli Enterprise Portal workspace
Request Summary:
Graph of vote status for all
resources.
Compound Status Summary:
Graph of resources by Compound
Status.
3
2
2 2
80
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-45
Tivoli Enterprise Portal Resource Topology
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-46
Key integration capabilities
• NetView is an excellent integration platform: many interfaces, great connectivity
• Geographically Dispersed Parallel Sysplex
• Alerting to SDF, System Automation for Integrated Operations Management,
OMNIBus, Event Integration Facility , problem mgmt,…
• Workload automation products can create requests to start or stop applications
 Comprehensive integration with Tivoli Workload Scheduler (TWS)
• Pro-active automation with OMEGAMON XE
• Monitoring of CICSPlex System Manager events
• Reporting: application state changes written to System Management Facility
 System Automation Application Manager availability, startup and shutdown reports
• End-to-end automation of applications running in:
 Multiple sysplexes or cross platform in z/OS, Linux, AIX and Windows
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-47
Lesson 8: Configuration assistance
IBM Automation Control for z/OS includes a new configuration
assistance function that is not (yet) available with System
Automation for z/OS
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-48
Traditional approach
Manual configuration steps
 Often error prone
 Cumbersome
 Time consuming
 ...
Read the Installation manual ...
... decide which of the many
installation steps apply to your
z/OS environment
Perform those steps by....
… adapting all the identified sample
files and …
… filling in your environmental data
at multiple places spread
across the sample files
And do all this
… in a consistent way!
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-49
Configuration assistance
Overview
•
Simple configuration to get base automation components running
Automation
– Automation manger
Manager
– Automation agent
Automation
Agent
– Subsystem interface
SSI
•
Use of configuration assistant that automates majority of
configuration process
•
Keep number of configuration variables down at the necessary
minimum
•
Benefit from lab experience using “standard” option set (stylesheet)
•
Post install/configuration verification to ensure all necessary steps
(in particular steps that have to be done by other persona) have been
completed
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-50
Configuration assistance – concept
One job to run
CONFLIB
Options File
Configuration
Assistant
JCLs
JCLs
JCLs
Start
JCLs
Procedures
JCLs
PARMLIB
DSIPARM
VTAMLIB
VTAMLST
JCLs
JCLs
One place to
define your
configuration data
One PDS to
find your
configuration files
Generating Configuration Files for one system.
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-51
Achieve higher automation level
• More z/OS subsystems, STCs, jobs,...
• Discover new ones using autodiscovery
• Special automation for CICS, IMS, DB2, TWA
• More automated messages
• Messages in joblogs
• z/OS UNIX resources (USS)
• Sysplex resources
• Pro-active automation
Processor Operations
• CPC and LPAR control
• Outboard automation for z/OS, z/TPF, z/VM, z/VSE, Linux
• zEnterprise resources
Same automation concepts across your enterprise
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
52
Summary
• Business applications require high availability
 Downtime can cause lost sales and customer shifts to competitors
• Automation provides high availability for z/OS applications including UNIX
• Policy-based plug and play automation using best practices can replace scripts
 Faster time-to-value
Play
 Much reduced maintenance burden
 Less human error
• Goal-driven automation to keep applications in line with business goals
• Grouping of resources for reduced complexity
and management at business application level
 Status aggregation
 Server and move groups help achieving availability targets
• Relationships between resources for accelerated
startup and shutdown, and correct recovery
• Manage by state, not by message
• Integration with monitors and OMEGAMON to increase
automation degree with pro-active automation
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
1-53
Hindi
Thai
Traditional Chinese
Gracias
Russian
Thank You
Spanish
Obrigado
English
Brazilian Portuguese
Arabic
Danke
Grazie
Italian
Tamil
German
Simplified Chinese
Merci
French
Japanese
Korean
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
54
Informative links....
System Automation for z/OS
website:
wiki:
forum:
http://tinyurl.com/sazos-website
http://tinyurl.com/sazos-wiki
http://tinyurl.com/sazos-forum
http://groups.yahoo.com/group/SAUSERS/
Service Management Suite for z/OS
website:
wiki:
forum:
http://tinyurl.com/smsz-website
http://tinyurl.com/smsz-wiki
http://tinyurl.com/smsz-forum
IBM Software Group | Tivoli Software
© 2013 IBM Corp.
55