Coexisting with earlier Micro Focus products

For example, this might happen if you have Net Express or Studio Enterprise Edition installed and either COBCONFIG or COBCONFIG_ is set for it.

To work around this issue, ensure that Visual COBOL is not running and then modify the configuration file by doing one of the following:

• If the invalid tunable is not needed by another application, remove it from the run-time configuration file.
• Add the following as the first line in the configuration file:

  set cobconfig_error_report=false

• Unset COBCONFIG (or COBCONFIG_) or set it to another configuration file that does not contain the invalid tunable for the particular session you are running in.

This happens when you edit files such as .dat that have a file association with Net Express or Studio Enterprise Edition. This can also happen when invoking a utility within the Net Express or Studio Enterprise Edition products as an external tool from Visual COBOL.

You can workaround this problem in Visual COBOL as follows:

1. Create a batch file that unsets COBREG_PARSED before the tool is invoked. The batch file contains:

   Set COBREG_PARSED=
   Call [PathToUtility] %1

   Where PathToUtility is the path to the Net Express or Studio Enterprise Edition utility.

2. In the Visual Studio IDE, add the batch file instead of the utility itself as an external tool.

   This ensures that the proper environment is established when running that tool.