Page tree
Skip to end of metadata
Go to start of metadata

Available in AIP Console ≥ 1.26.


Dependencies are an important component of the CAST analysis process: they determine some client/client and client/server links between objects. For the vast majority of situations, dependencies are automatically configured by AIP Console at Application level for each technology and are configured between individual Analysis Units/groups of Analysis Units. You can find out more about them in Advanced onboarding - review analysis configuration and execution.

Sometimes, however, dependencies are not configured automatically by AIP Console, particularly for languages managed via the Universal Analyzer - typically HTML5/JavaScript, SQL etc.) and this can sometimes lead to missing links and therefore issues with transactions and other analysis results produced by CAST. In this situation, during the analysis review and configuration (as explained in Advanced onboarding - review analysis configuration and execution) dependencies may need to be created manually, however, this can be a time consuming process.

To counter this, it is possible to force AIP Console to create a dependency between specific languages managed by the Universal Analyzer and which is valid for every single application managed on a specific AIP Node in AIP Console - in other words, once this is configured, users will no longer need to manually create dependencies between Universal Analyzer languages when AIP Console has not automatically created them.

Creating a permanent dependency

The creation of a permanent dependency between two Universal Analyzer technologies is actioned via a file called dependencies-matrix.xml located on an AIP Node (open using a text editor) - you will need to repeat this process for each AIP Node on which you want the same configuration. The file already contains default rules and information that should not be altered:


New dependencies can be added anywhere between the existing <dependencies> tags. The following syntax is required:

<language symbol="source_language,source_language">
	<allow symbol ="target_language"/>
	<allow symbol ="target_language"/>
  • the language tag can contain either a single language name or a comma-separated list of languages
  • the allow tag for target languages should contain one language only. You cannot provide a list. If you need to specify more than one target, add an additional <allow> tag.

Where source_language and target_language are the names of the languages you want to configure as dependencies, for example:

  • PLI
  • PLC
  • SQL
  • RPG400
  • PERL
  • PHP
  • HTML5
  • ...

For example, the following will create a permanent dependency between the client language PHP and the target language SQL:

<language symbol="PHP">
	<allow symbol ="SQL"/>

Save the file so that the changes you have made are taken into account. The AIP Node does not need to be restarted after changing the file.

  • No labels