File, Project and IDE Properties and Settings

Exploring the IDE settings

1. In Visual Studio, click Tools > Options.
2. Expand Projects and Solutions and click General.

   This page enables you to configure the default folder for storing Visual Studio projects as well as the defaults for the Output Window, Task List and Solution Explorer.

   The Projects location field defines the default location for storing new projects. You can change this path if you are using a different working folder.

   

3. In the Options dialog box, expand Environment and click Fonts and Colors.
4. Look in the list in the Display Items pane and note the COBOL, BMS and JCL items whose font and color you can change.
5. In the Options dialog box, expand Text Editor and then expand Micro Focus COBOL.

   You can use the settings in this section to configure features of the editor such as tab size, COBOL margins, some syntax checking rules, and others.

Configuring the COBOL editor

You can configure how the editor wraps the code around the margins, or how it indents the code in the different COBOL areas, or how the Home and End keys move the cursor in the different areas. You can also choose the style of the ruler, and change the colors of the text and the margins. You can change the default editor settings and experiment with the new behavior by opening one of the COBOL programs in the editor.

You can now experiment by changing the following settings:

• Click Tools > Options > Text Editor > Micro Focus COBOL > Margins - modify the settings for the Smart edit mode which controls the word wrapping and the indentation in the different COBOL areas. Click Toggle Smart Edit Mode, , in the COBOL toolbar to turn on or off the smart editing mode.
• On the same page in the IDE options, change the behavior of the Home and End keys.
• On the same page in the IDE options, check Show the ruler and check Mainframe style.

Project Properties

The properties you set on project level apply to all files in the project. To set properties for your COBOL project:

1. Select the BankDemo project in Solution Explorer and click Project > BankDemo Properties.

   This opens the tabbed property pages for the project in the main Visual Studio window.

2. Click the Dependency Paths tab.

   Type should be set to COBOL Copybook Paths. Note that this has C:\MFETDUSER\Bankdemo\Sources\copybook set. This is the folder where the IDE is going to look for the copybook files required by this project.

   

3. Click the BMS tab.
4. Note the following paths in the Output section:
   • C:\MFETDUSER\Bankdemo\Sources\copybook in the Copybook Output Path field
   • C:\MFETDUSER\BankDemo\System\loadlib in the Load Module Output Path field

   These are the paths for the copybooks and load modules that will be produced from the BMS files during the build.

5. Click the COBOL tab.
   • Note that the COBOL dialect is set to Enterprise COBOL for z/OS for the entire project.
   • Important: You need to set Character set to EBCDIC. You may need to scroll the COBOL property page to the right or to expand your IDE to see the setting.
   • Note that the Output path is set to C:\MFETDUSER\BankDemo\System\loadlib. This is where the build will produce the application executables.
   • See what other directives have been set in the Additional Directives field.
   • Build Settings is a read-only field that shows all directives that are set on the project.

   

6. As you have made changes to the project properties, click File > Save All in order to keep them.

File Properties

The individual source files can have their own local properties which override the project settings. To check the file properties:

1. In Solution Explorer, right-click BBANK10P.cbl and click Properties.

   This opens the COBOL-specific file properties.

   

   Notice that CICS Directives is set to CICSECM(). This has been set when you added the file to the project or performed a directives scan of the COBOL sources in your project.

2. In Solution Explorer, click the .bms file in your project.
3. Click the View main menu and then click Properties Window.

   This opens the Visual Studio properties window. Note that the Build Action is set to BMS Compile which means the build invokes the BMS Compiler.

   

4. Similarly, check the properties for the .dat, the .jcl and the .cpy files and see the .dat file and the copybooks will not be compiled.