Configuring Compiling and Debugging
You can specify settings for compiling and debugging in the global settings for the Rocket COBOL extension. These apply to Rocket Enterprise as well.
Location of a licensed Rocket Software product
- Micro Focus COBOL: Install Location
- The root folder of the licensed prerequisite Rocket Software product.
Ant and Java settings
You need to set values for the following settings to be able to compile COBOL projects created in Eclipse:
- Ant: Ant_home Path
- Specify the path to an Ant installation folder.
- Ant: Ant_home Resolve
- Specify how
Visual Studio Code should determine the location of Ant when compiling Eclipse projects:
- Use Current Environment - Default. Uses the values set in the current process environment. Ant must be on the PATH and ANT_HOME must be set before you start Visual Studio Code.
- User Defined - Visual Studio Code uses the value specified in the Ant: Ant_home Path field.
- Ant: Java_home Path
- Specify the path to the install folder of Java.
- Ant: Java_home Resolve
- Specify how
Visual Studio Code should determine the location of Java when compiling Eclipse projects:
- Use Current Environment - Default. Uses the values set in the current process environment. Java must be on the PATH and JAVA_HOME must be set before you start Visual Studio Code.
- User Defined - Visual Studio Code use the value specified in the Ant: Java_home Path setting.
CTF setting
- COBOL.CTF: Configuration File
- Specify the path to a Consolidated Tracing Facility File (CTF) to be used when launching the debugger or build tasks.
Default Compiler directives to use during compiling
- COBOL: Default Directives
- Default directives to use to compile a COBOL file when no task with a suffix
compileCurrentFile is present. For example, these directives are applied with the commands available through the
(Debug/Run) button in the top right corner of the editor task bar, and by the COBOL language server.
- PL/I: Default Directives
- Default directives to use to compile a PL/I file when no task with a suffix
compileCurrentFile is present. For example, these directives are applied with the commands available through the
(Debug/Run) button in the top right corner of the editor task bar.
MSBuild settings
The following settings apply when you build COBOL projects created in Visual Studio:
- MSBuild: Path
- Specify the path to the MSBuild executable on your machine.
- MSBuild: Resolve
- Specify how
Visual Studio Code should determine the location of MSBuild:
- Autodetect - Default. Visual Studio Code locates and sets the location of MSBuild automatically. It uses the first MSBuild installation it finds.
- Use Current Environment - Uses the value set in the current process environment. You must add the MSBuild location to the PATH before you start Visual Studio Code
- User Defined - Visual Studio Code uses the value specified in the MSBuild: Path setting.
Other build settings
- Suppress Build Assets Prompt
- Disabled by default. When the folder opened in Visual Studio Code contains a Visual Studio COBOL project for creating a .NET COBOL application, Visual Studio Code displays a warning if the launch.json or tasks.json files are not available and prompts to create them. If you do not want to build or debug the application, enable this check box to avoid receiving this message each time you open the folder in Visual Studio Code.
- Suppress File Associations Prompt
- Disabled by default. Check this if a warning is displayed that file associations have been defined which conflict with this extension.
- Terminal: 32bit
- Check this to use a 32-bit terminal so that t just sets the environment before starting the terminal so that commands you run in the terminal have the selected bitism.