- From the Search Paths Order window, modify the default search paths, add
several search paths for a resource type, and set the order in which these paths are
accessed.When resources such as COBOL, Natural, PL/I are built in IBM® AD Build Client, the corresponding include/copybook, control, proc, and macro files are searched, according to the default extensions in the default project folders.
- Generate a log file under each project folder during the build process. This procedure takes up more disk space but allows a detailed inspection of the build process if an error occurs. It is recommend to keep this option cleared. You may use it if detailed debug information is required.
- Determine whether a file or all the files from a project folder is included or not in the
analysis (Build). For the Include folders (Natural Include, Cobol
Include, Assembler Include), use Settings to
override the default extensions for these files. More parameters are available for each resource
- Set up an IMS DB Environment for COBOL programs that use EXEC
DLI commands and DL/I calls.
A corresponding IMS DB Environment needs to be set up for the programs that access IMS databases and/or IMS transactions.
IBM AD Build Client analyzes COBOL programs that use EXEC DLI commands and DL/I calls. All programs that access IMS databases and/or IMS transactions need to have a corresponding PSB, therefore an appropriate environment needs to be set up at the folder's project level.
To set up an IMS DB Environment, follow these steps:
- Select Show the project tree check box and expand the project tree.
- Select zOS Cobol folder and choose the appropriate IMS DB
Environment as in the following image.Note: The None option is selected by default.
Select the Using EXEC DLI (IMS related) check box to analyze COBOL programs with EXEC DLI commands that are present in the project.
When Using EXEC DLI (IMS related) check box is selected, two builds are triggered, increasing the build operation time.The second build is triggered when program "A" calls subprogram "B", where "A" is the main COBOL program that has a corresponding PSB, and "B" is the subprogram that contains the EXEC DLI commands.Note: As a result, a message is shown in the output window, informing that Building programs related to IMS EXEC DLI in subprograms.During the first build, a IMSExecDliInSubprograms.txt file is generated automatically and has the following format:
<called program name "B">, <parameter number 1>, <OffsetStart1>, <OffsetLength1>, <LinkageSectionVariable1>, <PCBNumber>
The generated file is used to resolve the parameters that are parsed from the main COBOL program "A" to the subprogram "B".Examples of the generated IMSExecDliInSubprograms.txt file:
- When a program name is called together with the parameters and their positions, where
-1 represents the PCB number
- When a program name is called together with the PCB number, where -1 represents
the parameters and their positions
- When a program name is called together with the parameters and their positions, where -1 represents the PCB number
- Enable the Extensibility features:
- Enable API/Macro handling by using a configuration file.
- Enable handling of before and after preprocessed source code.
For more information about using the setting options, see Using the Settings Option.
For more information about saving project properties by using CLI commands, see 7. Save Project Properties from command line interface.