|Title: What is the recommended method for specifying isCOBOL framework properties?|
From the documentation it seemed that the best or recommended practice is to put all property settings in c:/etc/iscobol.properties. However, with this method it is difficult to maintain different settings for different programs. I have to edit the c:/etc/iscobol.properties file every time I want to switch programs.
What is the recommended solution?
Unless iscobol.conf.only is set (or the corresponding command line option -conly is used, where applicable), isCOBOL can use several configurations at the same time. They are loaded in the following order, and the properties they contain are set in the order in which they appear in the respective files:
In this case iscobol.properties is loaded from the same directory as class_name
If a property is set in multiple places, isCOBOL will use the last read value.
Veryant recommends putting only the global property settings in c:/etc/iscobol.properties. These are the properties you want all programs for all purposes to use on the machine. It is common practice to put only the iscobol.license property in c:/etc/iscobol.properties.
For other properties there are two methods for reducing confusion:
When using the debugger, the properties must be specified after the -d or debugger class name (GraphDebugger).
Notice that the properties file is specified as the value of the iscobol.conf property. You can also specify other properties and "environment" variables for the COBOL program directly on the command line.
For example, to setup your program for remote debugging you could set iscobol.rundebug=2 as follows:
For another example, suppose your program has
You could set env_var on the command line as follows:
|Authored by: Veryant Support on Fri, Aug 28th, 2009 at 7:00 PM
This question has been viewed 8186 times so far.
|Online URL: http://support.veryant.com/support/phpkb/question.php?ID=3|
Powered by PHPKB Knowledge Base Software