IBM Support

Prerequisites and Maintenance for IBM Db2 Analytics Accelerator for z/OS V8.1

Detailed System Requirements


Abstract

This document describes how to get support for installation, upgrading, and operating IBM Db2 Analytics Accelerator for z/OS V8.1.
Furthermore it lists the hardware and software requirements.

Content

  • News

    Accelerator maintenance level 8.1.0.1 is now available. (Dec 9, 2025) 

     

  • Highlights of the new Accelerator version

    • Copying tables across accelerators

      V8.1 supports copying data between V8.1-accelerators natively using the new stored procedure SYSPROC.ACCEL_COPY_TABLES. Replicated and non-replicated shadow tables, AOTs, and archived tables are supported. 
      Consider the following use cases:

      • Migrating to a new accelerator
      • Taking one accelerator offline, e.g. for maintenance reasons, and continue with another accelerator
      • Adding an accelerator to a group of accelerators which is used for workload balancing
      • Re-synching tables on different accelerators after planned or unplanned outage
      • Populating tables that have identical structure and data.
    • LOB support

      V8.1 supports the LOB data type. The support requires the PTF for Db2 for z/OS APAR PH62993. This enhancement allows for seamless storage and management of large objects directly within the accelerator. Thus, users can handle extensive datasets with ease in the accelerator.
    • Unified Monitoring Warehouse

      V8.1 introduces a new built-in Unified Monitoring Warehouse which consolidates all monitoring data into a single, cohesive repository. The warehouse is structured in table format which makes accessing the data easy and convenient. The new tables are offering a detailed view on:

      • Load and Query statistics (to diagnose any performance issues)
      • Active tasks on the system
      • System utilization
      • Events and messages that occurred on the system
      • Table Details.
    • Improved resilience when using Integrated Synchronization

      V8.1 supports the Compression Dictionary Data Set (CDDS) provided by PTF for Db2 13 for z/OS APAR PH64099. This enhancement improves both the resilience and throughput of the data replication when log records for compressed table spaces are processed. We strongly recommend to apply the corresponding PTF and activate the CDDS support by corresponding customization of Db2.
    • New Accelerator Database Engine DB2wh Version 12

      V8.1 exploits Db2 Warehouse version 12 as backend database which provides coming new features and performance improvements. Especially the AI optimizer capabilities of the database have lead to query performance which offloaded queries can benefit from.
  • Download the Accelerator server image from Fix Central

    Please see the following table for the link to download the Accelerator Server image file:

    IBM Db2 Analytics Accelerator
    for z/OS 8.1 maintenance level
    ComponentRelease date
    YYYY/MM/DD
    8.1.0.1 (recommended)

    The release notes for the GA code level still apply. Therefore, read the 

    V8.1 Release Notes before installing this maintenance level.
    Switch to Fix Central for download of the container image "8.1.0.1-Information_Management-IDAA-Z" by clicking

    here.

     
    Please contact IBM support by opening a pro-active case and provide the IDAA maintenance level from where you are upgrading. IDAA support may convey further information concerning the installation/upgrade.
    Build information in Data Studio:
    Accelerator server: 8.1.0.202510170808
    Appliance software: 8.1.0.1.20251118-1143
    Db2 level: 12.1.2.0 [Build special_66570]
    2025/12/09
    Stored procedures:
    Make sure to install FMIDs HAQTX10 and JAQTXID providing the Stored Procedures for Accelerator version 8.1.
    as supplied by PTF UO04189 (APAR PH67172). 
    Build label: 20250708-0149
     
    2025/07/23
    8.1.0 - code level as of General Availability
     
    The container image for the accelerator GA code level 8.1.0 has been withdrawn from Fix Central on Dec 9, 2025. If you still have a need for that code level, contact IBM support. 
     
    Build information visible in the Administration user interface:
    Accelerator server: 8.1.0.202506120857
    Appliance software: 8.1.0.0.20250618-1705
    Db2 level: 12.1.1.0 [Build special_57125]
    2025/06/26
    Stored procedures:
    Make sure to install FMIDs HAQTX10 and JAQTXID providing the Stored Procedures for Accelerator version 8.1.
    as supplied by PTF UO04189 (APAR PH67172). 
    Build label: 20250708-0149
     
    2025/07/23
  • Migrating from Accelerator 7.5 on IBM Z

    • General remarks

      An installation of Accelerator V7.5 on IBM Z can be upgraded to V8.1 using the standard upgrade procedure. 
      The following prerequisites must be met / considered before starting the upgrade installation:

      • We recommend to start the migration of Accelerator V7.5 using maintenance level 7.5.14 or later.
        For migration from earlier V7.5 maintenance levels, a remote maintenance session is mandatorily required:
        for each of your accelerators, IBM Support has to manually shut down the accelerator database before starting the migration to V8.1. Contact IBM support by opening a support case.
      • A multi-node accelerator setup for V7.5 must use the Confined Head Node-architecture.
      • Any existing CDC-based replication subscription must be disabled.
      • Weak certificates for Integrated Synchronization must be replaced.
    • Stored Procedures

      The stored procedures for Accelerator V8.1 are provided via SMP/E-installable FMIDs HAQTX10 and JAQTXID.

      • See the program directory for details and also APAR PH67172.
      • Install them next to the V7.5 stored procedures. See the paragraphs concerning installation libraries and installation and setup in IBM Documentation for details.
      • In the existing WLM environment, concatenate the V8.1 stored procedure library (SAQTMOD) before the V7.5 stored procedures library.
      • The V8.1 stored procedures work with V7.5 and V8.1 accelerators.
      • After the migration and a test phase have been completed, the V7.5 stored procedures can be deinstalled. Note:
        If you are also using Db2 Data Gate on the same Db2 subsystem, you need to retain the V7.5 stored procedures.
    • Multi-node setup considerations

      • The support for a Cross-Drawer head node-architecture setup has been withdrawn in V8.1.
      • V8.1 will only support the Confined Head Node-architecture. Advantages are:
        • Improved load and workload performance because cross-drawer traffic is avoided
        • No PR/SM interaction involved
        • See the paragraph concerning multi-node setup in IBM Documentation for details.
      • Clients using the Cross-Drawer Head Node-architecture need to migrate to the Confined Head Node-architecture prior or during migration from V7.5 to V8.1.
    • Integrated Synchronization & weak certificates

      • Weak certificates are not supported for Integrated Synchronization in V8.1.
      • Weak certificates in general are old certificates which have a key length less than
        • 2048 bits for an RSA certificate
          RSA : Rivest-Shamir-Adleman, a public-key encryption algorithm.
        • 256 bits for an ECC certificate
          ECC : Elliptic curve cryptography, a public-key encryption algorithm.
      • Integrated Synchronization in V8.1 won’t start if a weak certificate is detected.
      • It is recommended to replace weak certificates with new ones before migrating to V8.1.
        Using Accelerator maintenance level 7.5.14, a DSNX881I message with ID 4047 occurs once a day in DB2MSTR if a weak certificate is detected.
    • Coexistence with Db2 Analytics Accelerator V7.5

      To run IBM Db2 Analytics Accelerator for z/OS® Version 8.1 and IBM Db2 Analytics Accelerator for z/OS® Version 7.5 side-by-side in a coexistence setup (that is : pairing a V8.1 accelerator to a Db2 for z/OS subsystem that has already been paired to a V7.5 accelerator), the V8.1 stored procedures must be used to support both Accelerators.
      If IBM DB2 Analytics Accelerator Loader for z/OS V3.1 will be used in a coexistence setup to load data to both a V8.1 accelerator and a V7.5 accelerator (HALOAD), the V8.1 stored procedures must be used.
  • Support - how can we help you?

  • Hardware requirements

    The following sections show the minimum hardware requirements that must be met to successfully install IBM DB2 Analytics Accelerator for z/OS.

    • Computers

      One of the following IBM servers is required:

      IBM Z serverIBM LinuxONE™ serverMachine Type
      Models: ME1
      Models: ML1
      9175
      Models: A01, A02
      Models: LA1, LA2
      3931, 3932
      Models: T01, T02
      Models: LT1, LT2
      8561, 8562
      Models: M01, M02, M03, M04, M05
      Models: LM1, LM2, LM3, LM4, LM5
      3906
      Model: ZR1
      Model: LR1
      3907


       

      A workstation (Intel® or compatible) is required to administer the
      • Installation and setup of the Accelerator on IBM Z. A Web browser (Firefox or Chrome) with network access to the LPAR(s) is required.
      • Accelerator (tables, queries, loads, replication). This workstation must be connected to the LPAR hosting Db2 for z/OS. For the hardware and software requirements of this workstation, see the system requirements for software used for the administration:
       
      For a single-node installation one accelerator is represented by one SSC-LPAR, for a multi-node installation by a cluster of SSC-LPARs. Each LPAR requires IFLs, RAM, and Storage.
      ComponentsMinimum suggested configuration
      IFLs

      For getting-started use cases, the minimum suggested configuration is:

      • 4 IFLs, 256 GB memory, and 10 GB for each InSync subscription
      The recommended ratio between IFLs and memory is: 32 up to 128 GB for each IFL
       
    • Storage

      FCP-attached or FICON-attached storage is required:

      • FCP-attached storage devices
        • A connection to a Fibre Channel SAN using a switched fabric is required.
        • The N Port Identifier Virtualization (NPIV) must be enabled in the Secure Service Container partition through the Support Element. For details see the Secure Service Container User's Guide, pages 6/7.
        • The use of all-flash storage is strongly recommended.
      • FICON-attached storage devices

         

        • A connection to a Fibre Channel SAN using a switched fabric is supported.
      • The amount of storage needed is depending on the workload. During setup the storage provided is distributed on various storage pools. For more information see the table 'Recommended pools and pool sizes' in chapter Installing Db2 Analytics Accelerator on Z of the Installation Guide.
      • Only fully-provisioned storage volumes are supported. This applies to all kind of devices (data, boot, and runtime). For more information see APAR PH39057.
    • Microcode Change Level (MCL)

      Product Engineering always recommends the highest available MCL level for best performance and availability.
      Please find information concerning IBM Z and IBM LinuxONE firmware updates and fixes here.

      • Mandatory MCL for IBM Z17™ & IBM LinuxONE™ 5 (all models) - Oct 3, 2025

        The following MCL or later is mandatory for use of the Accelerator on IBM Z17™ or on IBM LinuxONE™ 5 (all models):

        • Driver D61C Bundle S15
      • Mandatory MCL

        • Mandatory MCL for IBM Z16™ & IBM LinuxONE™ 4 (all models)

          The following MCL or later is mandatory for use of the Accelerator on IBM Z16™ or on IBM LinuxONE™ 4 (all models):

          • Bundle S40 (2025-xx-xx)
        • Mandatory MCL for IBM Z15™ (IBM LinuxONE™ III), IBM Z14™ (IBM LinuxONE™ II)

          The following MCL or later is mandatory for use of the Accelerator on 

          • IBM Z15™ & IBM LinuxONE™ III (all models)
            • Bundle S92 (2025-xx-xx)

     

  • Network requirements

    The following sections show the network requirements that must be met to successfully run IBM DB2 Analytics Accelerator for z/OS.

    • General Requirements

      For query acceleration on IBM Z, a TCP/IP network connection is required between the affected Db2 for z/OS subsystems and IBM Db2 Analytics Accelerator for z/OS V8. This connection can be defined as follows:

      IBM Z ServerRecommended / Supported Network Interfaces

       

      • Recommended: Network Express interfaces (10Gb or 25 Gb)
         
      • Still supported: OSA Express interfaces (10Gb or 25 Gb)
      • HiperSockets (if the Db2 subsystem runs in an LPAR on the same CEC).
      Note:
      Running the Accelerator on IBM z17™ requires MCL Driver D61C Bundle S15 or later. 

       

      IBM LinuxONE™ Emperor 5

       

      • Recommended: Network Express interfaces (10Gb or 25 Gb)
         
      • Still supported: OSA Express interfaces (10Gb or 25 Gb)
      Note:
      Running the Accelerator on IBM LinuxONE™ Emperor 5 requires MCL Driver 61C Bundle S15 or later. 

       

      IBM z16™, IBM LinuxONE™ Emperor 4
      IBM z15™, IBM LinuxONE™ Emperor III
      IBM z14™, IBM LinuxONE™ Emperor II

       

      • Recommended: RoCE interfaces (10 Gb or 25Gb)
      • OSA Express interfaces
      • HiperSockets (if the Db2 subsystem runs in an LPAR on the same CEC).

       


       

      Note:
      For configuration of Network Express, see here
      For an SSC LPAR, it is mandatory to configure the Network Express adapters in Hybrid mode (CPHID type = NETH). Network Express adapters configured as OSH/EQDIO are not supported. 
      Classic OSA cards carried forward to an IBM z17™ or an IBM LinuxONE™ Emperor 5 system have to be configured with CHPID=OSD. 


       

      Note:
      Network Express is a common hardware adapter for OSA/RoCE. It supports running both RoCE and OSA traffic simultaneously on their links so there is no need to use separate RoCE and OSA features any longer.
      For configuration of Network Express, see here


       

      For appliance installation and management, the following is required:

      • A Web browser (Firefox or Chrome) with network access to the LPAR(s).
      • Either the RoCE interface or the OSA Express interface can be used for the management network.

        If the OSA interface is used, one OSA Express card (1 GbE is sufficient) as network adapter for this management network.
        • Port 0 of the OSA Express card must be used and
        • The OSA adapter must be configured in QDIO mode (CHPID OSX or OSD).
      • If a Firewall is in place for this management network, at least HTTP/HTTPS ports (80 and 443) must be accessible for the appliance and the machine running the Web browser in this network.


      We recommend to separate the management network from the dedicated Db2 network.
      If IP addresses defined for the appliance and the machine running the Web browser are in different networks and network routing is implemented, the corresponding gateway must be specified during LPAR network definition.  

       


       

      OSA Express
      Z/OS administrators (system programmers) who are responsible for deploying / configuring OSA or the communication with Linux on IBM Z environments, should read the IBM z/OS Communications Server and OSA-Express Best Practices white paper. Network bandwidth and speed impact overall solution performance. For OSA interfaces we therefore recommend a dedicated OSA Express card and 10GbE (25 GbE) connectivity with Jumbo Frames.


       

      Firewall
       

      If a Firewall is in place for the network between the accelerator and the Db2 for z/OS-LPAR, at least the following ports must be accessible for the IP addresses assigned to the accelerator and z/OS LPAR:
      1400, 1401, 1500, 1600, 2222, 11301-11350, 11351-11399, 11400, 11401, 51113, plus GDPS server ports (if GDPS support is used).

      VLANs (access and trunk interfaces) are supported for networks configured for the accelerator. A trunk interface can carry traffic for two or more VLANs and requires VLAN specification in the network interface on the HMC (for the "management network") or the data network, connecting to Db2 for z/OS.

    • Requirements for inter-node communication in multi-node installations

      Why RoCE-communication must be used in multi-node installations of IBM Db2 Analytics Accelerator

      The RoCE communication will be possible when using the

      • the Network Express interface on IBM z17 or on IBM LinuxONE Emperor 5
      • the PCI adapter with a RoCE card on IBM z16, z15, z14 or IBM Linux ONE Emperor 4, III, or II.

      Very high workload in multi-node installations of Db2 Analytics Accelerator on IBM zSystems can lead to inefficient query processing, resource contention, and potential system instability. Using RoCE communication will reduce IFL resource contention, ensure predictable query runtimes, and enhance operational stability. 
      Therefore, the RoCE communication must be used for the inter-node communication between accelerator SSC-LPARs. 
       

      IBM Z servers prior to the z17 generation:
      For inter-node communication, it is recommended to bond two 25 GbE RoCE cards. The primary purpose of bonding is to deliver a performance increase to 50 Gb. A second purpose is to provide high availability.

       

      Click here for information how to configure the cluster network of an accelerator multi-node installation for the use of RoCE communication.

  • Software requirements

    • Operating Systems

       
      Operating system Required z/OS base elements 
      z/OS V3R2

      z/OS V3R1

      z/OS V2R5
       
      z/OS OpenSSH 
      (z/OS V3R1 requires fix for APAR OA65611; see APAR PH57280 for detailed information)
      Data Facility System Managed Storage Base (DFSMSdfp)
      Communications Server IP

      To avoid performance degradation during load operations we strongly recommend to install the PTF for APAR OA61558 when running z/OS V2R5. 

    • Database management software

      Use one of the supported database management systems on your System z server (preferably DB2 13 for z/OS). Make sure that required program temporary fixes (PTFs) and features are installed. Optional features are marked as such.

      Database management system Program number
      DB2 13 for z/OS5698-DB2 (MLC)
      or
      5698-DBV (Value Unit Edition)
      DB2 Utilities Suite for z/OS version 13.15698-DUT
      DB2 12 for z/OS (*)5650-DB2 (MLC)
      or
      5770-AF3 (Value Unit Edition)
      DB2 Utilities Suite for z/OS version 12.15770-AF4

      Note:
      A number of Db2-supplied stored procedures must be configured. See the Installation Guide for details. 
      (*) The support for Db2 12 for z/OS ends on Dec 31, 2025. 

    • Recommended minimum level of JDBC driver

      You can check the version of your JDBC driver by using the following command:
      java com.ibm.db2.jcc.DB2Jcc -version
       
      IBM DB2 Analytics Accelerator Minimum Level for Type 2 Connectivity Minimum Level for Type 4 Connectivity 
      IBM DB2 JDBC Universal Driver (db2jcc.jar)3.63.1413.64.111
      IBM Data Server Driver for JDBC and SQLJ (db2jcc4.jar)4.13.1454.14.119
      IBM Data Server Driver for JDBC and SQLJ V10.1 Fix Pack 2IP23387-IP23396
      Depending on the platform. This is sometimes required if you need to specify Db2 for z/OS special registers as part of the connection URL.
       
    • Recommended ODBC driver level

      Depending on your Linux, UNIX, or Windows operating system, the minimum level for DB2 Connect Version 10.5 is fix pack 4 and the minimum level for DB2 Connect Version 10.1 is fix pack 4. To enable the special registers for query acceleration, see Enabling query acceleration with IBM Db2 Analytics Accelerator for ODBC and JDBC applications without modifying the applications. Older versions of the driver might allow connections to Db2 for z/OS, but might fail to return results if timestamp columns are defined in a certain way.
    • Required Db2 maintenance level

      • Mandatory Db2-PTFs

        • Mandatory PTFs for using Db2 13

          When running IBM Db2 Analytics Accelerator for z/OS V8.1 with Db2 13, the following DB2-PTFs must be installed:

          Db2 PTF numberDb2 APAR numberMandatory since accelerator maintenance levelComments
          UI80810
          UI91652
          PH45854 PH53700 only required when using Integrated synchronization
          UO03540PH62993 required for LOB support
        • Mandatory PTFs for using Db2 12

          When running IBM Db2 Analytics Accelerator for z/OS V8.1 with Db2 12, the following DB2-PTFs must be installed:

          Db2 PTF numberDb2 APAR numberMandatory since accelerator maintenance levelComments
          UI54293PI91620  
          UI57923PI96258  
          UI60263PH00933 only required when using local date format
          UI63996PH00574
          PH10672
          PH13109
           required when using monitoring of HTAP queries
          UI63356
          UI69536
          UI71876
          UI75930
          UI77365
          UI80519
          UI91651
           
          PH06628
          PH23895
          PH28849
          PH37808
          PH40261
          PH45962
          PH53700
           
           only required when using Integrated synchronization which also requires function level V12R1M500
      • Recommended Db2-PTFs

        To determine all (Db2-)PTFs recommended for use with IBM Db2 Analytics Accelerator for z/OS V8.1, use the SMP/E REPORT MISSINGFIX command in conjunction with FIXCAT HOLDDATA as follows:

         

        1. Acquire and RECEIVE the latest HOLDDATA file onto your z/OS system. Use your normal service acquisition portal or download
          the two (2) year HOLDDATA files here: Enhanced HOLDDATA for z/OS .
          Ensure you select 'FULL' from the Download NOW column (last 730 days) to receive the FIXCAT HOLDDATA, as the other files do not contain FIXCAT HOLDDATA.
        2. Run the SMP/E REPORT MISSINGFIX command on your z/OS systems and specify the applicable Fix Categories using the keyword string FIXCAT (IBM.DB2.AnalyticsAccelerator.V8R1, IBM.DB2.AnalyticsAccelerator.V7R5, IBM.DB2.AnalyticsAccelerator.V7R1).

          The report will identify missing PTFs associated with that categories on that system. For more information about the SMP/E REPORT MISSINGFIX command, see here.
        3. Periodically acquire the latest HOLDDATA file and rerun the REPORT MISSINGFIX command to determine if there are new recommended (Db2-)PTFs for IBM Db2 Analytics Accelerator for z/OS V8.1.

         

        For Db2 12 for z/OS, we strongly recommend to apply both the PTFs for the APARs PH21726 and PH28050 having been marked HIPER and having got the FIXCAT keyword IDAAV7R5/K. Together these PTFs resolve the following issue:
        "Queries running on Db2 for z/OS are unexpectedly executed on Db2 Analytics Accelerator if QUERY ACCELERATION has been set to 'ENABLE' or 'ENABLE WITH FAILBACK'. This especially happens if queries have index access on tables with multiple indexes defined. A more costly access path will be chosen resulting in an execution of the query on the accelerator".

    • GDPS support

      The integration with with IBM GDPS ® (Geographically Dispersed Parallel Sysplex) for high availability and disaster recovery requires the following GDPS product versions:

      GDPS Metro Global GM 3-site and 4-site configurations are supported if the PTF for APAR PH27382 has been installed.
      Note:
      Please see the technote 'How to migrate DASD devices of Db2 Analytics Accelerator for z/OS defined for GDPS failover support'.
      The support of GDPS requires the use of the Processor Resource/Systems Manager (PR/SM) mode (rather than using the Dynamic Partition Manager (DPM) mode). 

  • Incremental update

    Integrated Synchronization is a built-in product component for continuous incremental update of accelerator-shadow tables. Changes to the data in original Db2 for z/OS tables are replicated to the corresponding target tables with a high frequency and just a brief delay. This way, query results from an accelerator are always extracted from recent, close-to-real-time data. The replication by Integrated Synchronization requires:

    • Db2 13 for z/OS or Db2 12 for z/OS with PTFs UI80519, UI77365, UI75930, UI71876, UI69536, and UI63356 installed, running at function level V12R1M500
    • Distributed data facility (DDF) with a secure port, configured for network encryption through AT-TLS
    • For data sharing groups: ability to always connect to the same member, for example by using a member-specific secure port that has a local alias.

     

    To benefit from increased resilience and throughput of the replication when processing the logs for compressed table spaces, it is recommended to apply Db2 13 PTF UO02927 and customize Db2 for use of the Compression Dictionary Data Set (CDDS). 

  • Administering the accelerator

    IBM Administration Foundation provides a graphical administration interface for the product.
     

    • IBM Db2 Administration Foundation in conjunction with Db2 Administration Services

      Db2 Administration Foundation provides a user interface for administering IBM Db2 Analytics Accelerator for z/OS after Db2 Analytics Accelerator Administration Services has been installed and configured. For an overview on the installation and configuration, click here.

      For a helpful example how to install and configure IBM Db2 Administration Foundation for z/OS, click here.

      By the way: Db2 Administration Services consists of a set of RESTful APIs that you can use in your applications to streamline or to automate the accelerator administration or management.

       

  • IBM Db2 Analytics Accelerator Loader

    IBM DB2 Analytics Accelerator Loader (further on abbreviated as 'the Loader') is a Db2 Tools product that provides capabilities and options for loading data into Db2 for z/OS and IBM Db2 Analytics Accelerator. These capabilities let you select the load option that best meets your business needs when populating data in the Analytics Accelerator. For use with Accelerator V8.1, the Loader version 3.1 must be used. This Loader version also supports the coexistence of Accelerator V7.5 and Accelerator V8.1 (parallel load of data to both Accelerator versions using HALOAD). 
    For more information on the Loader see here.
  • Collaboration

    • IBM Hybrid Data Management Community

      For collaboration with IBM and other users of IBM Db2 Analytics Accelerator for z/OS click here.
  • History of changes

    11 December 2025:

    • Availability of maintenance level 8.1.0.1 (Dec 9, 2025).

    15 October 2025:

    • Mention mandatory need for MCL Driver 61C Bundle S15 when running the accelerator on IBM z17 or IBM Linux One Emperor 5.
    • Network requirements -> General requirements: synchronize requirements for z17/LinuxONE 5 with prereq web page for IDAA 7.5.
    • Mention support of z/OS 3.2.

    26 August 2025:

    • Network requirements - Acceleration on IBM Z -> General requirements: mention support of OSA cards for LinuxOne 5 hardware.
    • Add table of administration-related APARs to section for Admin Services.
    • Amend the table of refresh packs for Administration Services with a column showing the corresponding Admin Foundation PTF.
    • Add PTF number UO04189 for Stored Procedure APAR PH67172 and specify the corresponding build label.

    25 July 2025:

    • Add Hipersockets to the list of Network interfaces available for IBM z17 HW.

    17 July 2025:

    • Emphasize mandatory need for remote maintenance session if migrating to V8.1 from V7.5 with a maintenance level prior 7.5.14
    • Rework Network-requirements -> General requirements-section with respect to IBM z17 and IBM LinuxOne5
    • Mention z/OS 3.2 preview
    • Repair broken link pointing to helpful document for install/setup of Admin Foundation

    9 July 2025:

    • Mention support of OSA Express interfaces for IBM z17

    4 July 2025:

    • Mention DB2 13 PTFs required for LOB support and CDDS support.
    • Mention UMS PTF UO03795 in the section for Administration
    • Mention IDAA Stored Procedure APAR PH67172
    • Add link to web page with APAR information for accelerator V8.1 (https://www.ibm.com/support/pages/node/7238939)

    3 July 2025:

    • Add sections "Highlights" and "Migration considerations"
    • Add link to the V8.1-Release notes for GA code level"

    27 June 2025:

    • New prereq web page for Accelerator version 8.1

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS4LQ8","label":"Db2 Analytics Accelerator for z\/OS"},"ARM Category":[{"code":"a8m0z0000000775AAA","label":"Db2 related products and functions-\u003EDb2 Analytics Accelerator for z\/OS"},{"code":"a8m0z000000072oAAA","label":"Install and Migrate"},{"code":"a8m0z000000073XAAQ","label":"Troubleshooting"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"and future releases;8.1.0"}]

Document Information

Modified date:
11 December 2025

UID

ibm17176203