Setting Up a Build with Sample Files
The API call analysis is supported by the AD extensibility feature. You can try out the feature by setting up a build with the API extensibility sample files. For more information about the sample files, see topic API Extensibility Sample Files.
Procedure
- Create an AD project, and add the sample program files
SQLCALL1.cbl and SQLGET.cbl into the project.
- For more information about creating a project, see topic Creating a project.
- For more information about adding files into a project, see topic Adding Files to Project Folders.
- Enable the API extensibility feature. After the API extensibility feature is enabled, the
API Config virtual folder is added into the project. This folder is used to
store the extensibility configuration files.
- Click Project > Settings > Extensibility.
- In the Extensibility pane, select the Enable API/Macro handling by using a configuration file check box.
- Click OK.
- Add the following two sample files into the API Config virtual folder of
the project. The files are the API extensibility configuration files.
- Api_Config.json
- ue-config.json
- Modify the paths in the ue-config.json file according to your settings.
- Modify the class path of the sample JAR files according to your local environment.
- Specify a path to store the input JSON files. This setting is optional and for debug purposes.
- Specify a path to store the output JSON files.
- Build the project. For more information about building an AD project, see topic Building Projects.
With the API extensibility feature enabled, after a project build is completed, the following
callgraph is generated for the SQLCALL1 program. In addition to the standard
output log file, an extensibility log file is generated by the build process and stored in the
<User folder name>\AD\comp\log folder.

Without the API extensibility feature enabled, after a project build is completed, the following
callgraph is generated for the SQLCALL1 program:
