What's new with IBM Db2 Analytics Accelerator for z/OS V8.1

Content

• What is new with maintenance level 8.1.1 (June 26, 2026)

  • Enhancements related to IBM Integrated Synchronization

    • Ability to change the Db2 for z/OS address and port using a stored procedure
      You can now use the stored procedure ACCEL_CONTROL_ACCELERATOR to change both the Db2 for z/OS IP address and port used by Integrated Synchronization to connect to the Db2 for z/OS system. Changing these settings so far has only been possible using the Accelerator Configuration Console. Now, by using the ACCEL_CONTROL_ACCELERATOR stored procedure, they can be changed as part of a batch job, for example when this is needed in failover scenarios to a disaster recovery site.
      Use the following syntax in the ACCEL_CONTROL_ACCELERATOR command parameter to change the Db2 for z/OS IP address and port: 
      
      <aqt:controlCommand xmlns:aqt="http://www.ibm.com/xmlns/prod/dwa/2011" 
      version="1.0">
      <changeReplicationEndpoint ip="<IP Address>" port="<Secure DDF Port>" />
      </aqt:controlCommand>

    • New DSNX881I message warning about a high volume of INSERT or DELETE statements per table. 
      A new DSNX881I (ID=20) message warns about a high volume of INSERT or DELETE operations on a specific table: 
      "/W2068/ High volume of %s operations detected for table: %s. Consider excluding this table from replication to reduce latency". 
      The message explanation says: 
      A high volume of INSERT or DELETE operations to a single table within a transaction can increase latency. If this message occurs, consider excluding this table from replication or keep the size of the transactions small (if possible) to reduce latency.
    • Improved indoubt transaction handling 
      The Integrated Synchronization status information and the Health reporting status messages have been enhanced to display the following information: 
      "Restart position RBA / LRSN : X, URID : X, timestamp : X". 
      Explanation: 
      The RBA or LRSN of the restart position along with the URID and timestamp correspond to the exact position in the log that Integrated Synchronization rewinds to and from where it resumes the processing from after a restart. This can help to identify and eventually cancel long running or indoubt transactions to avoid re-reading the log way back in time after an instance restart. 
      A new DSNX881I (ID=20) message has been introduced to warn about detected indoubt transactions: 
      "/W2069/ Open indoubt transaction detected in the source database system for urid %s. Cleanup of indoubt transactions might be required." 
      To cleanup indoubt transactions from Db2 for z/OS, run command:
      1. -DIS THREAD(*) TYPE(INDOUBT) to display indoubt transactions
      2. -RECOVER INDOUBT with either COMMIT or ABORT ACTION to make sure the transaction ends.

  • Enhancements in Accelerator functionality

    • Enhancements to Federation

      You can now federate history tables (TYPE=H in SYSTABLES) and archive tables (TYPE=R in SYSTABLES). The stored procedure SYSPROC.ACCEL_CREATE_REFERENCE_TABLES supports creation of references to history tables and archive tables. 
      Note: 
      A federated history or archive table would not be accessed by a temporal query on a federated base table. However, you can run a query directly on a referenced history table or archive table.