ZETALY Automated Capacity© overview

This chapter presents ZETALY® product ZETALY Automated Capacity©, version 4.5.00.

ZETALY Automated Capacity© environment

Collection environment

ZAC Collector

ZETALY Automated Capacity© collects metrics using its own collector (ASC). One ZAC collector STC must be started on every z/OS image.

ZAC Monitor

At each interval (the running frequency of the algorithm – the Policy Adjustment of ZAC), the ZAC Monitor retrieves data from ZAC Collectors such as R4H, DC, IMSU, Weight, number of logical processors, WLM Capping percentage for each LPAR and serial number, family, type, number of CPs for each CPC. In addition, the ZAC collector provides WLM service class and tenant resource groups information.

Setting environment

At each interval (the running frequency of the algorithm), ZAC decides to change (or not) the z/OS image defined capacity (DC). There are 2 ways to execute those changes:

BCPii

• The BCPii feature is available on z/OS 1.11 and higher

HMC API

• Configure the API and allow the HMC to be accessed via the network

Network environment

If you plan to use BCPii setting method, there are no network prerequisites.

If you plan to use HMC setting method, ask your Network Specialist for routing availability between the various z/OS images, and between ZETALY Automated Capacity© z/OS images and the HMC.

If a Firewall is used, make sure the SNMP protocol is opened between ZETALY Automated Capacity© z/OS images and the HMC.

More information is available in chapter 7: “Enabling communication with the HMC”.

ZETALY Automated Capacity© architecture

General architecture

The ZETALY Automated Capacity© product consists of three parts:

• The “Monitor” (main STC) controls the entire process. It runs permanently on one LPAR and executes cyclically (the frequency depends on the “INTERVAL” parameter);
• The “Collectors” which are ZAC agents (collector STC);
• The “Reporter” (HTTP server STC), which allows access to graphs and tables via a web browser
  • Internet explorer 11. Recommended version is IE 11
  • Mozilla Firefox 42+
  • Google Chrome 30+

Each cycle collects data, analyses LPAR behavior, sets LPAR capacity (or not), updates report files, sends alarms (or not) and writes SMF records.

Operator

Figure 1 ZAC Architecture

MONITOR

ZCASC : main ASC started task

Data gathering (collect)

• LPARs: DC, IMSU, R4H, WLM

Capping, WLM Service Class MSUs, importances MSUs, …

• CPCs: capacity, CPs, …

LPAR behavior analysis

Elaborates DC changes strategy

LPAR settings

Via BCPii or HMC API

Web reporting

Update HTML data files

Alert sending

WTO, emails, CMD

Web browser

From IE11, Firefox 42 or Chrome 30 upwards.

SMF records writing

225 by default

Metrology

ZETALY Streaming Agent, TDS - SAS/MXG, TBA, other

ASC REPORTER

ZCASCW IBM Web Server DOMINO or APACHE

ASC Commands

Period definitions

ASC parameters

ASC COLLECTOR AGENT

DC, IMSU, R4H, WLM Capping,

WLM Service Class MSUs, Importances MSUs, Tenant resource groups consumtions,….

ZETALY Automated Capacity© typical configuration sample

• One ZAC monitor (ZCASC) for two CPCs. This example shows one monitor, which manages two CPCs (a maximum of eight CPCs can be managed by one monitor).

Another way is to start one monitor per CPC. Thus, when you stop the monitor, only one CPC and the LPARs belonging to it are impacted.

In CMP mode you must start only one monitor to manage the entire CMP.

• One ZAC Web Reporter (ZCASCW) per ZAC monitor
• One ZAC Collector (ZCASCCOL) per LPAR managed by the ZAC monitor

Figure 2 Typical ZAC Configuration