Hello – we at Micro Focus are always interested in getting your feedback pertaining to new product enhancements.
This is the first in a series of poll questions that we will be asking in order to gauge interest in certain proposed features to determine if you would find these features to be beneficial to your own application needs.
Many thanks.
[Poll]Hello – we at Micro Focus are always interested in getting your feedback pertaining to new product enhancements.
This is the first in a series of poll questions that we will be asking in order to gauge interest in certain proposed features to determine if you would find these features to be beneficial to your own application needs.
Many thanks.
[Poll]It would be nice if i can lauch a Cobol application without having to set the environment in a Linux environment too ;-)
Hello – we at Micro Focus are always interested in getting your feedback pertaining to new product enhancements.
This is the first in a series of poll questions that we will be asking in order to gauge interest in certain proposed features to determine if you would find these features to be beneficial to your own application needs.
Many thanks.
[Poll]Thank you to all who responded to the poll question.
With the new release of Visual COBOL 2.2 update 1 which is now available for download on the Supportline Product Updates page, we have added two features which can help you to deploy your native COBOL applications without the need to launch them from within a .bat file.
1. Run-time Configuration settings.
You can now use the application configuration file (application.config) in native COBOL projects to specify some additional settings such as run-time tunables, environment variables and COBOL switches. You can do this from the new Run-Time Configuration tab.
When an executable is built using the IDE, the application configuration file is automatically copied to the output folder and is renamed as <executable-base-name>.exe.mfgcf.
When the program is launched the settings in this file will be read by the run-time system without the need to set them in a .bat file.
2.Run-time Launch Configuration Files
These files make it possible to specify the location of the COBOL run-time system without the requirement to set PATH or COBDIR environment variables. For network licensing scenarios where your COBOL Server and licenses are installed on a server and the application is run from user workstations this also allows you to specify the location of the licensing ces.ini file without the need to set the CES_INIT_LOCATION environment variable.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
