Adding Files to Project Folders
- Project folders depend on the type of selected project at project creation time. Therefore, for some projects, some of the following folders are not available.
- When adding files, if the limit of 40000 files is reached, additional virtual folders are
created at the project's level. They do not have correspondent on disk and they cannot be deleted
manually from IBM® AD Build Client. The additional virtual folders are different than the
existing virtual folders by having a special naming convention, suffixed by
@&@<incremental_number>
. Examples of additional virtual folders forzOS Cobol
:zOS Cobol@&@1
zOS Cobol@&@2
Environment | Folders- Description |
---|---|
z/OS® |
|
- Files under the project directory on the hard disk
-
- Control files
- These files can be placed by default into the CTRL directory that is
automatically created under the project directory. Control files must not have any extension in
order for IBM AD Build Client to locate them. In case
you have several control files with the same name that are taken from different libraries and used
by the JCL files according to the search order, create a directory under the project directory for
each library. For example, if two control files with the same name that are taken from two libraries
LIB1.MYCTRL and LIB2.MYCTRL, create two directories that
are named LIB1.MYCTRL and LIB2.MYCTRL under the default
CTRL directory and place each procedure in the corresponding directory. The
IBM AD Build Client JCL compiler searches for the right
folder according to the search order specified in the JCL.Note: This procedure is needed only if you have two control files with the same name, in which case they cannot be both put in the default directory CTRL.
The Control files (or the PARM files) are the source members referenced in DD cards in the format of DSN=MY.PDS.NAME(CTRLMMBR). These Control files may contain SORT parameters, or SYSIN data, or Db2® command (if in SYSTSIN card for Db2 invocation programs), all depending on the step they are used in and the DD card name.
The JCL include files are files that are included in the JCL source using the INCLUDE command, e.g.//LABEL001 INCLUDE MEMBER=INCFILE1INCFILE1 is the JCL include member. Usually these will have list of DD cards commonly used together in many JCL sources, and put into one shared file to simplify maintenance in case you want to add/remove/change a DD card. They can also contain full steps.
- Procedure files (also known as PROCS)
- These files, which are referenced from JCL files, can be placed by default into the
SYS1.PROCLIB directory that is automatically created under the project
directory. Procedure files must not have any extension in order for IBM AD Build Client to locate them. In case you have several
procedure files with the same name that come from different libraries and used
by the JCL files according to the search order, create a directory under the project directory for
each library. For example, if two procedure files with the same name that are
taken from two libraries LIB1.MYPROC and LIB2.MYPROC,
create two directories that are named LIB1.MYPROC and
LIB2.MYPROC under the project directory and place each procedure file in the corresponding directory. The IBM AD Build Client JCL compiler searches for the right folder according to the search
order specified in the JCL.Note: This procedure is needed only if you have two procedure files or include files with the same name, in which case they cannot be both put in the default directory SYS1.PROCLIB.
- PSB files
- These files, used only by the IMS application, must be placed in a directory that is named PSB under the project directory. This directory is not created automatically and therefore must be created if needed.
- The AAuto scheduling folder
- This folder can host two types of files: AAuto scheduling files and
AAuto Dataset Flag report files.
Before you run the build process, make sure to set the correct type for the AAuto Dataset Flag report file: In the Project pane, right-click on the Dataset flag report file that is loaded in the AAuto Scheduling folder of the project and select Properties. In the File Properties window, verify that the Type is set to AAuto Dataset Flag Report. (the file type verification can be done either when the file is loaded in the project or at a later moment, but before the build step is run).
- The CICS CSD configuration file
- A CICS administrator can use the LIST command of CICS utility DFHCSDUP to extract CSD information into a report. The report can be stored under the Configuration virtual folder and can be added to a build project as a CSD type of file. The build process parses the CSD configuration file and stores the information into the MFCICS tables.
- The IMS transaction mapping file
- This configuration file is used to map between IMS transactions and programs. The file must be placed under the
Configuration virtual folder in the project. The type of the file must be IMS/T
PGM. See the following example of mapping configurations in an IMS transaction mapping
file:
TRANSACTION(TRAN1) PROGRAM(PROG1) IMS-TM TRANSACTION(TRAN2) PROGRAM(PROG2) IMS-TM
- The Pgm_Aliases file
- This configuration file for aliases is used to specify external alias names coming from outside
the source files. The file will be added in the Configuration virtual folder,
in the project, with type PGM Aliases. The configuration file for aliases is a
comma separated file, having the following
format:
In case the alias name is not configured with a file path, the file format is as following:* - a commented line starts with '*' <optional disambiguation file path>, <procedure/program name defined in file>, <alias name 2>, <alias name 3>
PGM Aliases (Configuration) Files Example:<program/procedure defined in file>, <alias name 1>, <alias name 2> * procedure name in case of PLI/I file
* this is a commented line \\shared-resoures-dir\Projects\Pgm_Alias_002\PL1\PLI1, PLI1, PLI01, PLI001 \\shared-resoures-dir\Projects\Pgm_Alias_002\PL1\PLI1_1, PLI01, PLI_1, PLI_01, PLI1 PLI2, PLI002, PLI0002 PLI3, PLI03
Note:- These program aliases, <program/procedure defined in file>, <alias name 2>, <alias name 3>, can be declared in any order, provided <program/procedure defined in file> exists among the aliases names. Example: if only <alias name 2>, <alias name 3> are present and <alias name 3> is called, while <alias name 2> is not found as a program/procedure definition in any source file, then <alias name 3> will not be replaced with <alias 2> in the call.
- The first item <optional disambiguation file path> which is the fully-qualified-name of the file, is optional and only needed when the same alias name refers to actually different programs: in the example above, the same program alias name PLI01 refers to two different programs, defined in two different files. If only one fully-qualified-file-names of the two will be present or the two lines meant to be told apart have no alias name in common, the fully qualified file name would not make any difference.
- If disambiguation between two alias groups is needed, the fully-qualified-file-name of a PL/I file must be added in the 1st position, as it shows in PGM Aliases file. . Example: if the file was added with a network path, the same syntax must be used into the
- After adding new alias name(s) into the PGM Aliases configuration file, it
is recommended to (re)compile both the configuration and the PL/I files, where
<procedure/program name defined in file> exists, in this order. Example: .Note: When (re)building the entire project, the configuration file is build first by default.
Important: Currently, the external alias names feature is only available for PL/I programs. - The CheckReportConfiguration file
- In Check Report, programs from a z/OS system and subsystems (MQ, CICS, Db2, IMS...) are reported to be missing and it's not possible to load them in IBM AD. Actually, these programs should not be reported as missing since they are part of the system or subsystems. The missing components that need to be excluded from the Missing Component Report can be added in a configuration file.
- The PgmModuleMap file
- This file is used to map between load module and the first program that is called in the module
(relevant only for batch applications). By default, IBM AD
Build Client assumes the module name and the name of first program that is called are identical.
In case they are not identical, a mapping must be described in the
PgmModuleMap.txt file, which must be placed under the project directory.
Following is an example of the file
content:
OKC82 OKC8201 OKC75 OKC7501 OJC07 OJC0701
On the left side, the module name is specified and on the right side, the first program name is specified. - The PSBmap file
- This file is used to link the program and the PSB file names (the format contains: PgmName,
PgmType, PSBFileName).
If IMS related calls (CBLTDLI and CEETDLI for Cobol programs and PLITDLI for PL1 programs) are used, IBM AD Build Client assumes the program name and the name of the PSB file are identical. In case they are not identical, a PSBmap.txt file needs to be created and configured to describe the mapping between the program name and the name of the PSB file.
If EXEC DLI (IMS related) is used, IBM AD Build Client assumes the program includes the schedule command EXEC DLI SCHD PSB. In case that the EXEC DLI SCHD PSB command is not present in the program, a PSBmap.txt file needs to be created and configured to describe the mapping between the program name and the name of the PSB file.
Important: The PSBmap.txt file needs to be placed in the root of the project's directory, to <Project Path>\<ProjectName>\ folder. The ProjectName folder was created when the project was initially defined in IBM AD Build Client. It is located, by default, directly under the Default project path filled in .Following is an example of the file content:On the left side, the program name is specified, in the middle the program type (Cobol or PL1) is specified, and on the right side, the PSB file name is specified. For Cobol programs, in case the PROGRAM-ID and the file name are not identical, PROGRAM-ID name is used to map (link) the Cobol program with the PSB file name.EDADL3M,Cobol,EDADL3P EDADM2M,Cobol,EDADM2P EDADM4M,PL1,EDADM4P EDADN2M,PL1,EDADN2P
- In the Project tab, click the folder name, and then select . Alternatively, right-click the folder name and choose Add Files. A file selection window opens.
- Locate the files (they can be on any drive and directory) and select them individually or in groups (by using the Windows SHIFT key or CTRL key mechanism).
- Click OK to add the selected files to the project. The names of the files appear in the expanded file structure in the project tree.
- Repeat the Add Files procedure to add all necessary files to each of the project folders.
- If you need to add a long list of files, you can use the option Add
All Files from Folder. Selecting this option presents
you with the following window:Note: Make sure that the folder path is correct; click OK to add all the files from that folder to the corresponding project folder.
- To save the programs, files, and projects in their current states,
select File / Save All.Note: It is possible that the process of adding files can take a long time during which you cannot use the application. If you need to use the application, you can run the Add files process in the background. To make the Add files operation to run in the background, follow these steps:
- Click Start, select Run then type cmd to open the command window.
- Go to the folder where your IBM AD Build Client is installed and locate the IBMApplicationDiscoveryBuildClient.exe file. Drag the IBMApplicationDiscoveryBuildClient.exe file into the command window then enter “/?” and press ENTER. A window is displayed containing detailed instructions about how to make a specific process to run in the background.