Db2 Analytics Accelerator on Z - IFL, Memory, and Storage Configuration Changes

How To

Summary

IBM® Db2® Analytics Accelerator for z/OS® is a bundled solution package for the acceleration of database queries. Currently, it is a mainframe-based solution, where the accelerator is installed in a dedicated logical partition (LPAR). This is called IBM Db2 Analytics Accelerator for z/OS deployed on IBM Z. The short name is: Acccelerator on Z.

You have the following options when it comes to setting up Accelerator on Z:
- Setup on a single dedicated LPAR (single-node setup)
- Single-node setup in a Geographically Dispersed Parallel Sysplex (GDPS®) for failover support
- Setup on multiple dedicated LPARs (multi-node setup)
- Multi-node setup in a GDPS environment

Depending on the option chosen (single-node or multi-node), the Accelerator on Z requires one or more Secure Service Container (SSC) LPARs. IFLs, memory, and storage are key elements of SSC LPARs to execute accelerator workloads. This tech note describes steps to change the configuration of those three key elements.

Steps

How to change the IFL configuration

Adding IFLs

Login to HMC -> Operation Customization
Select Logical Processor Add
Select "Change a Running System" or "Save and Change“

Using the “Operational Customization -> Logical Processor Add” function of the HMC, the additional IFLs are directly

switched online and are made available to the operating system. However, this does not trigger a re-configuration of

Db2. A RESET or at least a backend Db2 engine restart is recommended. After IFLs have been added dynamically,

they are used, but the accelerator configuration is optimized only after a restart.

Removing IFLs

Login to HMC -> Operation Customization
Select Customize/Delete Activation Profiles

Removing IFLs requires a re-activation of the LPAR. This implies some downtime.

How to change the memory configuration

In the LPAR activation profile it is possible to change the memory size of the LPAR.

2. After the activation (using a restart), the new memory size is used.

How to change the storage configuration

It is possible to add storage without a downtime of the accelerator.

1. Log on to the Admin UI.

2. It is recommended to use the existing configuration file as the basis for your modifications. Download the currently active configuration file for the accelerator by selecting 'Download the currently active configuration file for the Accelerator':

3. Once the updated configuration file is ready for deployment, click the Upload icon/button to upload the updated configuration file for the accelerator.

4. The accelerator continues to work. If you have added storage in your configuration file, the corresponding disk drive is formatted.

It is not possible to remove storage from the accelerator. The new disks become part of an encrypted volume group and cannot be taken out. The easiest option might be to start over with a fresh installation (fewer disks) and to reload the data when it is really needed.

If you change the configuration of the Db2 network ("db2_nw"), you must restart the accelerator. Other changes to the network configuration are applied dynamically, so that a restart is not necessary.

IBM Z configuration changes that might have a resiliency impact

- Do not change the IP address of the accelerator because it is referenced in the Db2 for z/OS communications database (CDB) as well. The CDB information is used for the pairing and for the configuration of IBM InfoSphere Change Data Capture (CDC).

- An IBM Z firmware such as MCL upgrade might have a negative impact on the resilience of the SSC. However, there are cases that an MLC upgrade is required for the next release. It is recommended to verify check the Accelerator prerequisite web page for the latest information.

- Changing a storage box or the Central Processing Complex (CPC) has a complexity of its own and may also have an impact.

- FICON or network switch replacements and maintenance can be planned independently of accelerator maintenance.

- A risk always exists if you use third-party network or SAN equipment.

- Mind conflicts that might be introduced by software dependencies, such as Db2 for z/OS maintenance or an update of the stored procedures.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4LQ8","label":"Db2 Analytics Accelerator for z\/OS"},"ARM Category":[{"code":"a8m0z0000000741AAA","label":"Administration"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"7.5.0"}]

Product Synonym

Db2 Analytics Accelerator on Z, Accelerator on Z

Was this topic helpful?

Document Information

Modified date:
26 January 2022

UID

ibm16479361

Tips