BluInsights offers dependencies analysis for multiple languages (see the complete list). It is also possible to import your own analysis if needed.
Launch dependencies analysis
The proposed dependencies analysis is performed leveraging advanced parsing features for multiple languages. Launching the analysis is as simple as selecting the programming language (or its related platform). The last analysis date and time is displayed on the top right of the page. The analysis can be launched or re-imported as many as you want. The intermediate results will not be saved.
The analysis of large projects (thousands of programs) may take a few minutes. You will receive an email when the results are available. In the meantime, you can use the other features. Each entry menu in the list of the supported language is related to one or multiple technologies.
|Language||Files Extensions or Technologies|
|PowerBuilder||All (SRM, SRU, SRW, SRD...)|
|Ideal||All (programs, panels, reports...)|
|Mainframe and iSeries||COBOL (including Copybooks), RPG and RPGLE (including PF, LF, DSPF, PRTF, PPF), JCL, CL, ASM, PROC, SCL, etc.|
|Natural||All (NSP, NSM, NSN, NSC, NSH...)|
|Powerhouse||All (QTS, QZS, CMS...)|
Files without extensions will be first automatically processed by the classification in order to detect their types and apply the right parsers. This step may add extra time to perform the dependencies analysis. If you already know the types of your files, we recommend you add the corresponding extensions (e.g. .COB or .CBL for Cobol programs, .CPY for Copybooks...).
In addition to the table mode, BluInsights provides a graph visualization of the dependencies analysis. The files are presented as nodes and their relationships as edges. Nodes can be colored according to their types or their status.
BluInsights applies an automatic layout which fits the generated graph in terms of number of nodes and edges.
- Most of utility programs related to the underlying platforms are specified as "SYSTEM" dependencies.
- Detected missing dependencies are also inserted in the graph as "MISSING". The complete list can be found and downloaded by clicking on the exclamation mark button (on the top-right of the graph but visible only in case of missing dependencies).
Multiple actions are possible on the graphs (select all through CTRL+A, simple/multiple selection, subgraph extraction, etc.). All the possible actions are explained in the embedded help on the graph (Question mark on the top right corner of the graph).
The graph offers a filter that can be applied to the nodes in order to look for specific programs according to their names (including with RegEx), types (including missing and system), lines of code, workpackages, etc.). The filter allows also to find nodes with respect to the number of parents and children. This is important especially to detect "entry points" programs, i.e. files that are not called by others.
Subgraphs extraction, merge and layout
It is also possible to extract a subgraph (a set of nodes and their associated edges) in order to create a new one or to merge it with an existing subgraph. You can also extract subgraphs defined in an Excel file following a simple format (name of the program, name of the workpackage). BluInsights will automatically extract all the dependencies of each program and add it directly to the indicated workpackage. The related subgraph will be also generated with the same name as the workpackage.
Hide and reveal nodes
It is possible to hide and reveal nodes from the graphs. This feature is not available for the original graph that contains all the nodes of the project.
Neighbors: Parents and Children
It is also possible to incrementally start with a specific node and reveal its relations (neighbors). This can be made for children (called programs) and parents (called by programs).
- The Select action select the nodes if they are in the graph.
- The Show action reveal the nodes if they are NOT in the graph. Ctrl + Z/Y actions are possible on this feature.
Create workpackages and subgraphs with dependencies from Excel
You can create workpackages using an imported Excel file. Assigning a file to a workpackage assigns all it's dependencies to the same workpackage. The Excel file should contain in the first column the files names and their workpackages in the second column.
Import dependencies analysis
If you prefer to use your own dependencies analysis, BluInsights allows to import a JSON file (the required format is shown when the question mark is clicked).
Download the analysis result
It is also possible to download the generated json result. This can be useful in order to add extra information (project-specific dependencies, languages, etc.) and re-upload it again.
The dependencies result is displayed as a tree with nested programs (or any other specific input, e.g. reports, views, routines...). All the actions performed on a given file is automatically updated for all the instances of the same file.
MISSING and SYSTEM entries cannot be edited but they can be exported in the Excel file.