Problem / Current Behaviour
•  Fivetran must read QSYS2.QJOJRNOBJS for every table attached to the log journal.
•  When the journal contains >300 objects, the Schema tab in the Dashboard times-out or hangs indefinitely.
•  Competing tools (e.g. Informatica) allow a schema/library filter before discovery, making the UI responsive even with large journals.

Proposed Solution
Expose an optional field in the connector Setup Form (or an Advanced Setting) called “Schema / Library Filter”.  When filled, the connector passes that value into the display_journal / QJOJRNOBJS call so only objects in that schema are returned.  This keeps the effective object list under 300 without forcing customers to physically split their Db2 journal or create multiple connectors.

Business Impact
•  Allows large IBM i environments (frequently 5 000 – 100 000 tables in one journal) to use a single connector without UI freezes.
•  Eliminates the operational overhead of maintaining dozens of duplicate journals just for Fivetran.
•  Reduces initial-sync time because unnecessary metadata isn’t transferred.