Can infoConnect products be leveraged together?

Yes; that is the way our product suite was designed. When bundled together, they are highly complementary and supported by our in-house team members. Several customers leverage our connectors in conjunction with our CDC component for real-time, bi-directional integration capabilities.

Do you offer POCs to customers?

Absolutely. Our service team is here to assist with product configuration and first use case implementation. We can also help define tables, perform full installation of the product in sandbox or non-production environments, and configure corresponding connectors to ensure everything works from the IBM i perspective.

How do your connectors work?

Compatible with both RPG and COBOL, our connectors use native IBM i libraries and low-level socket integration (cloud or on-premise) to call backend programs directly.

How many transactions can your connectors handle?

Many of our customers deal with large peak volumes and process hundreds or thousands of transactions per second leveraging our connector. The throughput of the product depends on several factors including (but not limited to) application design, connection speed between your platform and IBM i (AS/400) servers, and the number of connections in the connection pool.

Does infoCDC require timestamps on the table?

Time stamps are not required, as the product does not poll periodically based on time stamps. infoCDC connects directly into Db2 journals, almost like how Kafka persistently logs data and events: whenever a change happens, one or more entries are pushed into a journal that is immediately made available for a process on our end.

Does infoCDC have a limit on the number of tables you can capture?

The product supports multiple tables and journals. infoCDC has one listener job per journal, with multiple tables that could be configured per journal and processed by a single job, making it rather lightweight and easy on the system. Generally, there’s no hard limit on the number of tables or journals that it can process simultaneously.

How much CPU or memory is needed for the infoCDC to run on the IBM i?

Overall, implementation will have minimal impact on IBM i system performance. Listening is handled by a specific job for each journal on IBM i, as opposed to a trigger-based solution. This approach is very lightweight, using filtering criteria to determine relevant events before sending them to a data queue for delivery to external systems.

In summary, performance and results largely depend on the combined configuration of system components, jobs, and processes within the environment.

What is impact analysis?

Impact analysis involves detecting and evaluating the positive and negative effects of a change or event on an application, system, or environment. It helps in planning effectively and making informed decisions to ensure smooth transitions and risk mitigation during changes.

How to perform impact analysis?

Traditionally, impact analysis is a manual, time consuming process of tracing relationships between programs, files, fields, and variables. Additionally, it involves scoping the change, identifying potential impacts, evaluating those impacts, and developing mitigation strategies. Due to its manual nature, this process often poses critical challenges for architects, developers, and professionals.

What are the challenges of impact analysis that IBM i professionals face?

IBM i systems comprise thousands of interconnected components and little documentation. While performing impact analysis on these systems, professionals face difficulty in identifying affected components accurately, understanding the extent of changes, and managing time and resources. Additionally, professionals struggle to meet the evolving nature of requirements, keep up with new technologies, and collaborate effectively with other team members.

How does iA help in impact analysis?

iA automates and simplifies the entire impact analysis process. It scans your IBM i environment, maps all relationships, and uses AI to generate visualizations and plain-language summaries. With iA, professionals can:

  • Scan the entire IBM i environment automatically
  • Map all relationships between fields, files, objects, programs, and variables
  • Instantly identify impacted programs, variables, and files
  • Convert core program logic into easy-to-understand summaries for simplified documentation
  • Communicate actionable insights clearly across technical and non-technical teams

These help reduce costs and time for IBM i projects significantly.

Let’s Build Your Modernization Roadmap Together

Contact us for a free strategy session with IBM i experts.

Talk to an IBM i Expert