Chapter 3. z/OS 97
3.6 z/OS msys for Operations
msys for Operations is a subset of System Automation for OS/390 V2 that provides
automation of critical events that can have an impact on system or sysplex availability. It also
provides a full-screen interface to simplify sysplex operations. It is a base element of z/OS,
and comes automatically on all z/OS 1.2 or later ServerPacs (that is, it does not have to be
explicitly ordered).
The automation actions that msys for Operations provides are based on IBMs analysis of
customer outages and the root causes of those outages. Any function that it performs is seen
as an area where there were multiple failures due to complexity or lack of automation.
One of the benefits of using msys for Operations is that the automation is designed based on
IBM’s experience across many customers, and is designed with the involvement of IBMs
sysplex architects and developers. However, even if you do not use the automation functions
of msys for Operations, you should study the events that it automates and ensure that you
have equivalent automation for those events.
msys for Operations is also available for OS/390 2.10 and z/OS 1.1 as a free Web download
from:
http://www.ibm.com/servers/eserver/zseries/zos/downloads/
3.6.1 Automated Recovery Actions
A number of recovery actions can be completely automated. These include:
򐂰 Creating or re-creating missing alternate CDSs (CDSs)
򐂰 Expanding the CDSs for the System Logger in case of a directory shortage
򐂰 Management of System Log offload and failure situations
򐂰 Long-running ENQ management to prevent resource lockout
򐂰 Management of WTO(R) buffer shortages
򐂰 Sysplex partitioning
򐂰 Management of Auxiliary Storage shortages
Each automatic recovery action can be enabled or disabled separately and a number of the
recovery actions may be customized. By default all supplied actions are disabled and require
enablement and possibly customization through editing a special data set member should
their function be required.
Alternate Couple Data Set management
When a primary CDS fails, XCF makes the alternate the primary to support continued
operation. After the switch, however, an alternate no longer exists; therefore the current
primary is now a single point of failure for the sysplex as a whole.
msys for Operations provides a recovery mechanism that tries to ensure that an alternate
CDS is always available through creation of a new alternate in the following situations:
򐂰 During initialization of msys for Operations, a check is made to ensure that an alternate
exists for every primary defined. If an alternate is not found then msys for Operations
automatically creates it.
򐂰 At run time, msys for Operations automatically creates a new alternates whenever the
current alternate has been removed or switched to a primary.

Get Achieving the Highest Levels of Parallel Sysplex Availability now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.