Deep dive analysis includes interdependencies, as well as the resources, databases, and variables that are accessed. This can be done by reviewing all of the code in the application and architectural diagrams OR using an analysis tool, like ADDI, you can run the reports to collect the same information. Examples of what you can do in ADDI are:

• Generate program call graphs to show how programs, transactions, databases and files are connected in complex environments. For a demonstration, watch this video: Creating a CICS Transaction Callgraph.
• Leverage usage reports to show where certain resources or variables are accessed. For a demonstration, watch this video Accessing Batch Job Usage Inventory.
• Use impact analysis reports to show multi-level impacts of changes to variables and databases across programs. Learn more: Impact Analysis Report
• Locate complex programs which could be candidates for refactoring by generating complexity reports. Learn more: Complexity Reports
• Generate cross application flow graphs to gain insights into interactions with other applications. Learn more: Cross Applications Callgraph

Hogan® Core Banking and CAMS application calls look like a black box to the developer, making it difficult, if not impossible, to analyze, debug, and understand the relationship between Hogan and non-Hogan applications.

IBM worked with DXC™ to create a Hogan®/CAMS™ Connector for ADDI. Rather than manually reviewing code and architectural diagrams, developers can use ADDI with the Connector from DXC™ to gain visibility into the relationships, including process dictionary components like maps, transactions, and activities.

Watch this video to earn more about Hogan and CAMS application support.

An application can be made up of thousands of programs and copy books. Moving to a modern SCM, like Git, allows for the opportunity to better organize these files so that they can be more easily maintained.

To do this, developers need to review the application to discover the relationships of programs, as well as their local copybooks, which could take days or months depending on the size of the application.

Using a tool, like ADDI, you can quickly identify clusters of programs and their local copybooks that should be stored together. In addition, you can identify shared copybooks to be stored in a separate Git repository to ensure there is no duplication of copybooks.

Learn more on ADDI and Git by watching these videos:

ADDI and Git Support - Part 1

ADDI and Git Support - Part 2

Applications use cryptography to protect, authenticate, and validate sensitive information from cyber-security threats. As quantum computers become more powerful, they will be able to break classic encryption algorithms, so the industry has developed new quantum-safe algorithms that are resistant to attacks from both traditional computers and quantum computers.

The architect must manually go through their COBOL applications to pinpoint where cryptography is used in an application and what Integrated Cryptographic Service Facility (ICSF) Crypto API calls exist, including encryption rules and other important parameters.

Or, using ADDI, security architects can auto-discover where applications use cryptography and what crypto algorithms they use. In addition, it discovers calls to the ICSF. If customers have created their own custom abstraction layer for cryptography, then they can also configure ADDI to discover calls to that abstraction layer.

The data collected by ADDI is then passed to a cryptography dashboard where security architects can assess the vulnerability of both the cryptography and ICSF calls within an application. This information is then used in the planning process to protect against harvesting of confidential data.

Learn more by watching Quantum-Safe Cryptography and the ADDI Tool.

Prior to migrating to a later version of COBOL, it’s important to first address any old syntax issues and application dependencies to ensure the correct parameters are being sent between applications.

Manual analysis can be done to discover syntax issues and application dependencies, OR ADDI can be used to quickly identify these parameters to accelerate your migration journey.

Learn more or connect with IBM COBOL experts directly on the COBOL Migration Portal.

A change to a field in a database has a rippling effect to all the applications that query and update it (i.e., increase size of account number). This is referred to as data lineage.

To discover data lineage, the architect or developer must manually analyze data to determine its dependencies with other applications OR use ADDI to generate a report that provides a deep dive analysis into where the data originates and the extent to which it is shared across programs within an application.

This report provides the insight needed to discover exactly where changes need to be made.

In addition, auditors may require proof of where data is sourced (i.e., GDPR). This can be complicated when applications that reference fields in a database use different names for that field (i.e., customer name vs client name).

Manually analyze the data to determine where data is sourced OR use ADDI to run a data lineage report.

This report quickly identifies the specific field within a database from where the data is sourced, satisfying auditors and making your organization compliance ready.

Learn more: Datasets Reports

Unleashing data on Z to the broader organization starts with providing a simple way to access it. To do this, organizations need a way to access non-relational data the same they with would a relational database. In order to accomplish this, you need the metadata and a means to generate a virtual table that emulates that experience.

• To do this, customers create a map for the fields in each file via a manual configuration process. This can be very time consuming for thousands or tens of thousands of files.
• Using ADDI, you can auto-discover and auto-document the non-relational metadata.
• IBM Data Virtualization Manager (DVM) then uses this meta data to auto-generate the virtual tables.

Learn more: Datasets Reports

Companies leveraging AI need a comprehensive data fabric. By incorporating IBM Z into a data fabric, organizations can access current transactional data at its source to deliver real-time insights from that data to make better decisions and maintain a competitive advantage. Much of the information is stored in non-relational databases on IBM Z. By modernizing this non-relational data on IBM Z, it can be easily integrated into the data fabric.

To do this, customers create a map for the fields and define the metadata in each file via a manual configuration process. This can be very time consuming for thousands or tens of thousands of files. Alternatively, you can use ADDI to auto-discover and auto-document the non-relational metadata. IBM Data Virtualization Manager (DVM) then uses this meta data to auto-generate the virtual tables. This data is then ready to be integrated into the data fabric.

Learn more: IBM Data Virtualization Manager