Search docs.molo17.com

    IBM iSeries logo Db2 for IBM i agent changelog

    Release notes

    2.3.2.1

    Released: November 11, 2026

    • A region of the cache whose flush to the disk fails stays dirty and is flushed again, instead of being forgotten after that one failed attempt;

    2.3.2.0

    Released: November 10, 2026

    • GSSD-1490: a table shared by a CDC entity of the shared journal reader and a snapshot-only or dedicated-reader entity is still read for the CDC entity, instead of being left out of the shared read, which gave the CDC entity none of its changes;

    • A decoded journal row is committed only to the entity it was decoded for, instead of every entity of the table receiving every entity’s version of it, which failed the target on the first missing column when entities of one table had different columns; the legacy DSPJRN reader has the same fix;

    • GSSD-1488: a checkpoint left on a deleted journal receiver is recognised as outdated on journals that reuse the same receiver names, instead of reading the new receiver from the old sequence (CPF7054 every round) or keeping the checkpoint as unreadable for days;

    2.3.1.4

    Released: November 2, 2026

    • GSSD-1473: The Db2 for i insert is batched again and the driver refuses an over-long value, instead of every row becoming its own round trip, which took 9.6 seconds for 436 rows against 0.05 seconds and held the shared pool connections while every other entity queued behind them;

    • GSSD-1477: Query timeouts are cancelled on wall-clock time instead of being handed to the Predictive Query Governor, which rejected a validation of a large table up front with SQL0666 without running it;

    • Where an entity starts reading is logged at INFO once instead of on every poll;

    • GSSD-1473: An over-long value is refused as the bulk staging table is loaded, instead of a staging table one unit wider than its target letting it through so that the drain ran its DELETE and the server refused its INSERT with SQL0404, which on a file that is not journaled lost the row;

    • GSSD-1473: A value refused as too long is reported as Value Too Long for Column, naming the side that refused it and the lengths it measured, and is not retried, instead of being reported as "Request Timeout: Data truncation" and written four times before surfacing;

    • GSSD-1481: A journal read the IBM i refuses with Not authorized is reported as an authority error naming the object and the authorities the reads need, instead of reaching the UI as "AS400 JDBCSQL Syntax Error";

    2.3.1.3

    Released: October 29, 2026

    • GSSD-1467: CDC: the next journal page is read at once after a page holding no rows of the pipeline’s tables, so a busy journal with the file filter off no longer spends most of its time sleeping and falls hours behind;

    2.3.1.1

    Released: October 27, 2026

    • GSSD-1289: new opt-in suspendCaptureForInactiveEntities. An entity stopped for more than 30 minutes is no longer cached: its table leaves the journal read when no other entity needs it and its cache is deleted, instead of growing until the disk fills. When it starts again it reads the journal from its last confirmed transaction, then rejoins the cache. Off by default, since the recovery window becomes the retention of the journal receivers; not available with the legacy DSPJRN reader;

    • CDC: the local cache is drained up to its head in one poll instead of one message per poll, so a backlog reaches the target faster;

    • Metrics: a page’s read time no longer includes the wait for the target to consume the previous page;

    • Target: an object field from a NoSQL source is written as its JSON text instead of {name=Ada, age=36}, and an array that holds a map or a nested array is written as a JSON array instead of [Ljava.lang.Object;@…​;

    2.3.1.0

    Released: October 25, 2026

    • Every staged transaction of a bulk flush reaches the target;

    2.3.0.3

    Released: October 21, 2026

    • GSSD-1427: The members of multi-member files are resolved for all the tables of a pipeline at once, with one SYSTABLES query per schema, instead of one table at a time. On a pipeline of about a thousand entities each lookup took around 200 seconds, so leaving maintenance ran past the REST timeout; 274 tables now resolve in under a second;

    2.3.0.1

    Released: October 15, 2026

    • GSSD-1409: An OffsetDateTime is written into a TIMESTAMP column;

    • GSSD-1413: A column is no longer matched by a field’s text description;

    • With DDS discovery on, the keys of a table without an SQL primary key are read from the file description, so two discoveries running at the same time no longer read each other’s keys;

    • Bulk operations: an insert and a delete, or two updates, of a row keyed by binary or array values in one batch are merged instead of leaving the row on the target or failing with a duplicate key;

    • The agent hands its pooled database back when its pipeline is deleted or detached and when its initialization fails. Before, the next pipeline writing to the same database could fail in a loop with NoClassDefFoundError;

    2.3.0

    Released: October 13, 2026

    • Agent compatibility upgrade to Gluesync 2.3;

    • Added the optional suspendCaptureForInactiveEntities setting (off by default): it suspends capture and drops the cache of an entity stopped longer than inactiveEntityCaptureSuspensionDelayMinutes (default 30); on start the entity catches up from the journal;

    • GSSD-1412: "Generate CREATE TABLE statement" in Query Studio is built from the QSYS2 catalog and works on tables and views, instead of failing with SQL0204 "SQL_IDENTIFIER in SYSIBM type *N not found";

    • Resetting every entity on a journal deletes the shared journal checkpoint, instead of resuming the reader from the old position so the reset entities received nothing;

    • The source cache saves the corrected read position after a recovery scan, so a restart no longer starts reading mid-record or discards records written after a torn record;

    • Discovery returns schemas and tables in alphabetical order, so Query Studio pages no longer skip or repeat objects;