The
IMS pages in your project properties enable you to specify output folders for the generated files, or DBD, PSB or MFS build settings.
Note: The properties set on IMS files in your project might differ from the IMS properties set for the project. To reset a file's properties to the values set for the project, right-click the file in Solution Explorer, and click
Reset item directives (to project).
You can specify the following properties:
- Output Folders
-
- Generated file path
- Use this field to specify the folder to contain the output from the generation of the DBD and the PSB files in your project.
- MFS output path
- Use this field to specify the folder to contain the output from the generation of the MFS files in your project.
- Database path
- Use this field to specify the folder to use when looking for IMS databases for the current project.
- Configuration file path
- Use this field to specify a folder to contain the IMS System Configuration data indexed file,
imsconfg.dat, created at build time (the build also sets the ES_IMSCFG environment variable). If no folder is specified, the file is created in the project directory.
- Clean also removes all DBD/PSB generated files
- Check this to delete all DBD/PSB generated files when cleaning the project. This also deletes the DBDGEN3.DAT, DBDGEN3F, PSBGEN2.DAT files that would not normally be deleted.
- DBD Build Settings
-
- Message level
- Choose the level of error message reporting when generating DBDs.
Levels are cumulative, that is, if you select
Severe, you only see Severe errors, while if you select
Error, you see messages at Severe and Error level, and if you select
Warning, you see all messages.
- Generate listing file
- Check this to generate a listing file,
filename.lst, containing the original DBD source statements with any warning or error messages included, for each
filename.dbd file in your project.
By default, the files are saved in a
Listing subfolder within the project directory. Use the browse button to specify a different location for the files.
Rebuilding the project updates all listing files. Cleaning the project deletes the listing files.
- Generate Map for DBD
- Check this to cause the DBDMAP utility to be run and generate a .MAP file in the directory of the .DBD source file.
- Additional directives
- Specify any DBDGEN directives to be used when genning DBD files in the current project. Separate directives with a space.
- PSB Build Settings
-
- Message level
- Choose the level of error message reporting for PSBGEN.
Levels are cumulative, that is, if you select
Severe, you only see Severe errors, while if you select
Error, you see messages at Severe and Error level, and if you select
Warning, you see all messages.
- Generate listing file
- Check this to generate a listing file,
filename.lst, containing the original PSB source statements with any warning or error messages included, for each
filename.psb file in your project.
By default, the files are saved in a
Listing subfolder within the project directory. Use the browse button to specify a different location for the files.
Rebuilding the project updates all listing files. Cleaning the project deletes the listing files.
- Validate PSB against DBDGENs
- Check this to validate the genned PSB against the current DBDGEN library.
If
Generate listing file is checked, the validation report will appear in the listing after the PSB source statements.
- Additional directives
- Specify any PSBGEN directives to be used when genning PSB files in the current project. Separate directives with a space.
- MFS Build Settings
-
- Message level
- Choose the level of error message reporting for MFSGEN.
Levels are cumulative, that is, if you select
Severe, you only see Severe errors, while if you select
Error, you see messages at Severe and Error level, and if you select
Warning, you see all messages.
- Generate listing file
- Check this to generate a listing file,
filename.lst, containing the original MFS source statements with any warning or error messages included, for each
filename.mfs file in your project.
By default, the files are saved in a
Listing subfolder within the project directory. Use the browse button to specify a different location for the files.
Rebuilding the project updates all listing files. Cleaning the project deletes the listing files.
- STACK handling
- Choose a method of processing STACK and UNSTACK statements. The STACK and UNSTACK statements are often used to define different device types for one format. With Mainframe Subsystem Support, only one device type can be 'active' at a time, thus, the STACKs for the other device types are not needed and would slow the processing of the MFSGEN.
- Use preprocessor
- Only use this if you need to enable a preprocessor that will modify the MFS source before MFSGEN processes it.
- Additional directives
- Specify any MFSGEN directives to be used when genning MFS files in the current project. Separate directives with a space.
Note: If you store all listing files in the same folder and two of the files have the same name, the second file created by the build replaces the one created first.
