Scribd
Upload
877 views

Ab Initio - Invoking Dependency Analysis

Dependency Analysis in Ab Initio

Uploaded by

Luis Yañez
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
877 views

Ab Initio - Invoking Dependency Analysis

Dependency Analysis in Ab Initio

Uploaded by

Luis Yañez
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Invoking dependency analysis Page 1 of 1

Co>Operating System Help > Graph development > Dependency analysis > Invoking dependency analysis

Invoking dependency analysis


You can invoke dependency analysis in the GDE or from the command line.

In the GDE
There are two ways to invoke dependency analysis in the GDE:
Using a menu command — Choose Project > Analyze from the GDE menu bar. Analysis results are reported on the
Dependency Analysis tab of the Application Output window.
When you check in the graph — Unless you have set the analysis level to Do not analyze, the analysis results are
reported on the Summary page of the Checkin Wizard, before you actually check in the files. For step-by-step instructions,
see “How to check in a sandbox, graph, plan, or file”.

From the command line


Dependency analysis is performed automatically at checkin using the air project import command. Use the -dry-run argument
to skip the actual checkin.

To invoke dependency analysis explicitly from the command line, issue the air project analyze-dependencies command. By
providing the appropriate arguments, you can have the command analyze everything in a project or analyze particular objects:
Specify -all to analyze all graphs and to parse all record format and transform files in the project.
Specify one or more paths to files you want to analyze.
If you specify a directory, all graphs, record format files, and transform files in that directory are analyzed.

The air project analyze-dependencies command is useful for project architects who need to see the results for an entire
project. For example, you might run it after changing some code in a common project — the command reanalyzes all affected
graphs.

How warnings are reported


air project analyze-dependencies reports any dependency analysis warnings. By default, the warnings are grouped by specific
warning messages rolled up for all objects analyzed, but you can provide command-line arguments to organize the reported
warnings by object, to generate parsable output (for example, output that could be processed by an Ab Initio graph), or to
present the warnings in the format used by previous versions of the Co>Operating System.

For more information on air project analyze-dependences, see the Technical Repository Command Reference.

Analysis level of a graph


The level of analysis actually performed on a graph by air project analyze-dependencies is determined by the arguments you
provide to the command as well as by the value you have set for dependency analysis for the graph. For more information
about specifying the amount of analysis to be performed, see “Specifying the level of dependency analysis”.

Related topics
air project analyze-dependencies
air project import
Introduction to dependency analysis
Why use dependency analysis?
Specifying the level of dependency analysis
Examples of analysis setup

Copyright © 1997-2010, Ab Initio, Confidential and Proprietary. All rights reserved.

mk:@MSITStore:C:\Users\lyc\Documents\Proyectos%20TeSI-ZUMA\Payments%20Hu... 30/08/2019

You might also like