Professional Documents
Culture Documents
Out of service!
Thank you very OnDemand challenges
much and have a – Downtime unaffordable
nice day!
– Heterogeneous by nature
– Environment is complex to manage
Customer pressures
– Application availability
– Operations complexity and costs
– Skills and education requirements
– Rapid change of IT-infrastructure
Automation Tasks
Operator
Event
*WEBSPHERE
*HYPERSWAP
*PROCOPS
*IBMCOMP
Resources
*GDPS
*TBSM
*CICS
*NMC
*TWS
*USS
*SAP
*DB2
*E2E
*IMS
Relationships
*ITM
Resource groups
Restart and failover rules
*BASE *Empty
Policy content Best practice policies Administrator
Automate applications
Automate repetitive and complex System (Applications)
tasks
Monitor applications, messages, and
alerts
SA MP on Linux
on System z
VCS
MSCS
SA MP on Linux
on System x or p HACMP
SA MP on Windows
Management of cross-
platform dependencies TBSM Alerting in case of critical events
SA App TEC /
Manager OMNIbus
Enterprise-wide access
Enterprise-wide access
Infrastructure totoother
otherNetView
NetView
Systems
Systems
(default goals)
VSAM Coordinated failover
Takeover
Tivoli Enterprise Portal MQ file
Status Display Facility ISPF-based
NetView 3270 Customization Dialog
NetView Management Console
Automation configuration file (Agent)
NetView / Automation Manager control file
Apps SA NetView
Agent / MFPLSTSA
INGMSG01 (automation table)
Apps SA Agent
Automation
Apps Agent
NetView AS
SA will…
Application PAYROLL uses a DB2-database
1 Start JES and RRS to access employee data
JES RRS
DB2 itself consists of multiple address
spaces. Required are:
– MSTR, master address space
depends on
– DBM1, services
– IRLM, lock manager
DB2_IRLM
2 Start DB2
For transaction processing the Resource
DB2_DBM1
Recovery Services (RRS) address space is
DB2_MSTR
needed
Most address spaces depend on the JES
depends on
subsystem
3 Start PAYROLL PAYROLL To ensure proper function of PAYROLL,
these dependencies must be considered
when PAYROLL is started
●
A System Automation (SA) Resource
represents any instance in a z/OS system that
JES/APL/SYSA RRS/APL/SYSA can be monitored and automated
JES RRS
Typical instances are
●
●
Applications to automate started tasks,
depends on
USS processes, CICS regions, and many
more
DB2_IRLM DB2_IRLM/APL/SYSA ●
Groups of applications to manage their
DB2_DBM1 DB2_DBM1/APL/SYSA
members as one entity or to realize cross-
system failover capabilities
DB2_MSTR DB2_MSTR/APL/SYSA
DB2/APG/SYSA
Additionally, special resources exist such as
●
depends on ●
z/OS Systems to manage system
add/leave
PAYROLL/APL/SYSA
PAYROLL
●
Groups of systems to manage resources
SYSA/SYS/SYSA in a sysplex
SYSB/SYS/SYSB ●
Monitor resources to monitor the health of
applications, the system, or any other
object in a z/OS system
SYSPLEX/GRP
Resource States
●
Status changes cause SA to react such that
Active message Term message (<type>) a satisfactory compound status is reached
indicates startup … and completion of shutdown
Compound status
Application Startup
●
Optional pre-start command sequence
Up message ●
Actual startup command sequence
indicates end of startup
●
Optional post-start command sequence
SA issues pre-start ●
Application start request is issued by SA
commands ●
Optionally, when a supporting resource is
available
SA issues startup
commands ●
Example: Activate VTAM major node for
application as soon as VTAM is up
SA issues post-
start commands Post-start sequence starts when
●
●
Up message was received …
Active message ●
… and start request originated from SA
indicates startup
●
Different start types can be defined to tell
SA, for example, the difference between a
JES cold and a warm start
Relationships
Supporting Resource
●
Relationships describe how a particular
dependent resource depends on one or more
supporting resources
DB2_IRLM
DB2/APG/SYSA DB2_DBM1
●
The relationship type tells SA what to do with
the dependent resource, for example:
DB2_MSTR ●
MakeAvailable
●
MakeUnavailable
●
HasParent
WhenAvailable MakeUnavailable
●
A condition tells SA what must be fulfilled before
an action is executed, for example:
●
WhenAvailable
●
WhenDown
HasParent MakeAvailable WhenDown
●
Conditions are treated by SA like goals, i.e. SA
PAYROLL/APL/SYSA PAYROLL
attempts to bring the supporting resource into a
state such that the condition is fulfilled
Dependent Resource
Define an Application
COMMANDS HELP
------------------------------------------------------------------------------
Define New Entry
Command ===>
Entry name resulting from
Define new entry of type Application NEW command
●
Errors, e.g. JES2 main-task abend
*071 $HASP098
●
Normal operator tasks, e.g. SMF data set switch
ENTER TERMINATION
OPTION
SA allows you to react on messages with
●
●
Replies, e.g. “R xx,END”
“REPLY 71,DUMP” ●
Commands, e.g.
S SMFCLR,MAN=SYS1.MAN1
●
Combination of both
*072 $HASP098
ENTER TERMINATION ●
If a message is issued multiple times in a
OPTION
row, you can react differently within each
“REPLY 72,END” PASS (escalation/sequencing)
COMMANDS HELP
------------------------------------------------------------------------------
Reply Processing Row 1 to 22 of 22
Command ===> SCROLL===> PAGE
Enter the replies to be issued when this resource issues the selected message
or define this message as status message.
maintenance reasons
JES RRS
●
Both, JES and RRS are supporting resources
and therefore are not affected
HasParent ●
PAYROLL is a dependent resources that must
SA will… be shut down before the DB2 group can be
DB2_IRLM
stopped
2 Stop DB2 DB2_DBM1
DB2_IRLM
DB2_DBM1 DB2_MSTR
●
The IRLM and DBM1 address spaces must be
DB2_MSTR shut down before the MSTR address space is
stopped
HasParent
●
In fact, they are started and stopped by the
1 Stop PAYROLL PAYROLL
master address space itself – no operator
Policy intervention is required
“I want
to stop
DB2”
Application Groups
●
Combine multiple components of one
application on one system or cross-system
DB2/APG/SYSA ●
Operate those components on a group-
level rather than individually
DB2_DBM1 DB2_IRLM ●
Application groups have either a system or a
sysplex scope
HasParent HasParent
●
System Automation supports three ‘natures’ of
DB2_MSTR
groups
●
BASIC – the group is available when all of
its resource members are available
Compound status of the DB2 is ●
MOVE – the group is available when one
SATISFACTORY, when all resource resource member is available
members are AVAILABLE ●
SERVER – the group is available when one
or more resource members are available
Application Shutdown
●
Optional shutdown initialization command sequence
●
Actual shutdown command sequence
Term message (<type>) ●
Optional post-shutdown command sequence
indicates shutdown…
Shutdown initialization sequence starts when
●
●
Application stop request is issued by SA
●
Optionally, when a supporting resource is unavailable
SA issues post-shutdown ●
Example: Send warning message to users or quiescing
commands activities
●
NORM – for normal shutdown commands and replies
●
IMMED – for immediate shutdown commands and replies
●
FORCE – for forced shutdown commands and replies
Subsystem : C_DB2_MSTR
Shutdown Phase: SHUTIMMED External Shutdown:
* For the detail-oriented: See Shutdown Delay field in application information policy item for how long SA will wait between shutdown passes
IEASYSxx:
…
●
Goal: manage maximum possible number of
CMD=SA products/components through SA
… ●
including JES, VTAM, etc.
●
Default desired status for the resources is
COMMNDSA: AVAILABLE, unless
…
●
A resource is prevented from being started at IPL
COM=‘S NETV,SUB=MSTR’ ●
The goal in the policy is UNAVAILABLE
COM=‘S INGEAMSA,JOBNAME=AM,TYPE=HOT,SUB=MSTR’
… ●
The system starts merely those components
necessary to ‘bootstrap’ SA
●
NetView running Automation Agent
z/OS console:
●
An automation manager
AOF767I AUTOMATION OPTIONS: 010
●
[NetView Subsystem Interface]
. STOP - CANCEL AUTOMATION
. PAUSE - SUSPEND AUTOMATION ●
At SA-initialization time, you can decide to
. NOSTART - DO NOT AUTOMATE SUBSYSTEM STARTUP perform a
. NOSAVE - DO NOT SAVE AUTOMATION CONTROL FILE
. WARM - WARM START FROM CACHE
●
Warm or cold start
. COLD - COLD START FROM DISK ●
Nostart or pause
. TABLE= - OVERRIDE DEFAULT AUTOMATION TABLE(S)
. ENTER - CONTINUE WITH 'WARM'
NOTE: CACHE IS CURRENT, NO UPDATE REQUIRED
NOTE: DEFAULT IS: WARM
*002 AOF603D ENTER AUTOMATION OPTIONS OR 'R' (RE-DISPLAY) - DOMAIN IPXFG
Policy Information
Bibliography
Related Documentation
– SA z/OS V3.3 Defining Automation Policy (SC34-2572)
– SA z/OS V3.3 User’s Guide (SC34-2573)
– SA z/OS V3.3 Programmer’s Reference (SC34-2576)
– SA z/OS V3.3 Customizing and Programming (SC34-2570)
–
White Papers
– IBM Tivoli System Automation for z/OS V2.3:
A Primer to Monitor Resources
– Performance Driven Automation with OMEGAMON and System
Automation for z/OS
End of Presentation
User forums
http://groups.yahoo.com/group/SAUSERS/
The purpose of this group is to discuss technical issues related to IBM Tivoli System Automation for z/OS with your peers.
http://groups.yahoo.com/group/SA4DIST/
The purpose of this group is to discuss technical issues related to IBM Tivoli System Automation with your peers.
This group is for distributed platforms like Linux and others, but not z/OS.