Several miscellaneous runtime configuration variables affect the Terminal Manager. These are described in detail below.
Note that for the variables AUTO-PROMPT, BELL, MONOCHROME, SCROLL and WRAP, the settings 1, on, true, and yes are synonymous, as are the values 0, off, false and no.
1. 132-MODE
This variable specifies that MS-DOS video cards for 132-column display will be used. It also describes the technique used by the video card manufacturer to enter 132-column mode.
In order to provide 132-column mode with ACUCOBOL-GT, the video card must meet two requirements. The first is that the card must be able to be placed into 132-column mode via a call to interrupt 0x10, subfunction "0". This is the normal method used by video cards to change modes (it is what the MS-DOS mode command uses).
The second requirement is that the video memory must be organized linearly when 132-column mode is used. This means that the memory location for row 2 column 1 must immediately follow the location for row 1 column 132. This is a logical extension of the normal organization used for 80-column mode. Most cards that support 132-column mode meet these requirements.
Because ACUCOBOL-GT cannot determine the method used by the card manufacturer to enter 132-column mode, you use the 132-Mode configuration file entry to describe the technique. It should be followed by the (decimal) mode value the card uses to enter 132-column text mode (with 25 rows).
For example, a Paradise VGA card can enter 25 x 132 mode by using a mode value of 0x55 (hexadecimal 55) when attached to a color monitor, or a value of 0x57 when attached to a monochrome monitor. Assuming that we had a color monitor, the proper configuration file entry would be:
132-MODE 85
| ATI Integra, VGA/Wonder, EGA/Wonder
| 35
|
| ATI Prism Elite
| 83
|
| Chips & Technologies chip sets
| 96
|
| Genoa 6000 Series
| 96
|
| Paradise Systems
| 85
|
| Trident chip sets
| 83
|
| Tseng Labs chip sets
| 35 |
When set to a non-zero value, the AUTO-PROMPT runtime configuration variable causes every ACCEPT statement without a PROMPT phrase to be treated as if PROMPT SPACES were specified. This has the effect of erasing the field where the data is about to be entered. This is provided primarily for compatibility with ACUCOBOL-85 version 1.1, which behaved this way. The default setting for this variable is zero.
3. BELL
When set to a zero value, the BELL variable suppresses all bells generated by ACCEPT and DISPLAY statements. This will make ACUCOBOL-GT totally quiet even if WITH BELL phrases are used on DISPLAY statements. The default setting is one.
4. HOT-KEY
This variable associates an exception value or values with a program. When a key with a specified exception value is pressed, the corresponding program is run. This variable is described in detail in Appendix H.
5. MONOCHROME
When set to a non-zero value, this variable disables color output for MS-DOS machines with graphics video cards.
ACUCOBOL-GT assumes that all MS-DOS machines with graphics video cards have color monitors (because the card has color abilities). If you have a monochrome monitor attached to such a machine, the results can be difficult to see. You can tell ACUCOBOL-GT to disable color output for these monitors through the Monochrome option. When this is set to a non-zero value, ACUCOBOL-GT will use only black and white. The default value is zero. Note that you may change this in your program by using the SET ENVIRONMENT verb; ACUCOBOL-GT examines the MONOCHROME setting each time it does screen output.
6. RESTRICTED-VIDEO-MODE
This variable controls the rules ACUCOBOL-GT uses when displaying data on a terminal with "non-hidden" attributes (sometimes called "magic cookies"). See the section "Restricted Attribute Handling" later in this chapter for a discussion.
7. SCROLL
When set to zero, the SCROLL variable inhibits screen scrolling, except scrolling caused by explicit SCROLL phrases in ACCEPT and DISPLAY statements. If a line wraps on the bottom line of the screen, the screen will not be scrolled if SCROLL is set to zero, but the line wrapping will still occur; it will overwrite the bottom line. Normally, ACUCOBOL-GT will scroll the screen to bring a DISPLAY line onto the screen if its line number is past the bottom edge of the screen. When SCROLL is set to zero, this does not occur and the cursor location becomes undefined (see the Note at the end of this section).
8. WRAP
The WRAP variable controls whether line wrapping is allowed. Normally, a DISPLAY statement that does not fit onto one line will wrap around to the next line. When WRAP is set to zero, this does not occur and the DISPLAY statement is truncated at the end of the line. Also, ACUCOBOL-GT normally wraps around to bring the column position specified for an ACCEPT or DISPLAY statement onto the screen. If WRAP is set to zero, the cursor location becomes undefined (see the Note at the end of this section).