|
|
|
|
|
True = The Compiler generates bridge classes that allow the COBOL programs to access RDBMS in the same way as they do with ISAM indexed files.
False = No bridge class is generated.
|
|
|
True = Generate EDBI routines suitable for IBM DB2.
False = Don’t generate EDBI routines suitable for IBM DB2.
|
|
|
True = Generate EDBI routines suitable for IBM DB2 on AS/400.
False = Don’t generate EDBI routines suitable for IBM DB2 on AS/400.
|
|
|
True = Generate generic EDBI routines.
False = Don’t generate generic EDBI routines.
|
|
|
True = Generate EDBI routines suitable for Informix
False = Don’t generate EDBI routines suitable for Informix.
|
|
|
True = Generate EDBI routines suitable for MySQL.
False = Don’t generate EDBI routines suitable for MySQL.
|
|
|
True = Generate EDBI routines suitable for Oracle.
False = Don’t generate EDBI routines suitable for Oracle.
|
|
|
True = Generate EDBI routines suitable for PostgreSQL.
False = Don’t generate EDBI routines suitable for PostgreSQL.
|
|
|
True = Generate EDBI routines suitable for Microsoft SQL Server.
False = Don’t generate EDBI routines suitable for Microsoft SQL Server.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1 = Pagination only when using a UNIQUE index
2 = Pagination for every index
|
|
|
|
|
|
|
|
|
True = Map alphanumeric COBOL fields to CHAR on the database.
False = Map alphanumeric COBOL fields to VARCHAR on the database.
|
|
|
True = Use ISAM positioning rules on end of file.
False = Don’t use ISAM positioning rules on end of file.
|
|
|
|
|
|
|
|
|
1 = Write zero instead of non-numeric values
|
|
|
0 = Don’t use the latin1_general_bin collating sequence
1 = Use latin1_general_bin during CREATE TABLE
2 = Use latin1_general_bin during ORDER BY
|
|
|
True = Every field with EFD DATE directive becomes a DATETIME, regardless of the date format string.
False = Fields with EFD DATE directive become DATE, TIME or DATETIME according to the date format string.
|
|
|
True = Use the string representation to deal with dates.
False = Use conversion functions to deal with dates.
|
|
|
True = Return records with duplicate key values in the primary key order.
False = Return records with duplicate key values as you read them from the database.
|
|
|
True = Use leading zeroes in OCCURS item names.
False = Don’t use leading zeroes in OCCURS item names.
|
|
|
True = Replace high-values with the maximum value allowed by the field.
False = Don’t replace high-values in the fields.
|
|
|
1 = Use hints but keep the ORDER BY in they query
2 = Use hints and discard the ORDER BY in the query, assuming that records will be sorted according to the index set by the hint.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 = Never wait for locks and return an error instead
1 = Always wait for locks
|
|
|
True = Enable the support for UNLOCK ALL statement.
False = It’s not possible to perform UNLOCK ALL.
|
|
|
True = Don’t check for table existence during OPEN.
False = Check for table existence during OPEN.
Note - disabling the check of table existence may improve performance, especially if your programs use the OPEN statement a lot. However, there are also few side effects, for example, since the OPEN will never fail with ‘file not found’ you will not be able to create with I$IO having io_creates=1 in the configuration. Also, if the table doesn’t exist but the OPEN doesn’t fail, you might have odd errors in the next operations.
|
|
|
True = Generate entry-points in the EDBI routine where the user can inject customized code.
False = Don’t generate entry-points.
|
|
|
|
|
|
|
|
|
True = Array boundaries are checked at Runtime in order to provide more details in case of "out of bounds" errors. If a program addresses an item that is outside the valid range, an error message is shown and the program exits. The error message informs about the data item name and the problematic index value.
False = Array boundaries are not checked. If a program addresses an item that is outside the valid range, a generic "out of bounds" error message is shown and the program exits. The -m1 option may avoid the crash and make the program access the area of the next Working-Storage item instead.
|
|
|
True = an exception is thrown for USAGE DISPLAY numeric and numeric-edited variables that don’t contain a number.
False = no exceptions are thrown for USAGE DISPLAY numeric and numeric-edited variables that don’t contain a number.
|
|
|
0 = Results are undefined.
1 = The program aborts with the error message "Attempt to divide by zero".
3 = The result is the dividend, as if the division was by 1 instead of by zero.
|
|
|
|
•
|
isrun and iscrun commands
|
|
|
|
|
|
|
|
|
|
the configuration variable jver will have the value “1.7.0_65” (assuming that you’re working with this JVM) and the configuration variable hello will have the value “Hello, World!”
|
|
|
|
|
|
1 = PASCAL (or WINAPI) convention.
|
|
|
|
|
|
0 = All messages are shown in a message box.
1 = All messages are sent to sysout. In a thin client environment, runtime error messages are sent to the server sysout while messages displayed by the program are sent to the client sysout.
2 = All messages are sent to syserr. In a thin client environment, runtime error messages are sent to the server syserr while messages displayed by the program are sent to the client syserr.
3 = Runtime error messages are printed to a file named <program_name><number>.ads.log, while messages displayed by the program are sent to the syserr (client syserr in thin client).
|
|
|
True = Produces "Abend Diagnostic Snapshot" (ADS) in addition to Java exceptions
False = No ADS is produced in addition to Java exceptions
|
|
|
True = Internal java methods are traced in exception messages. There’s no point in compiling with -g option in this case.
False = COBOL paragraph names are traced in exception messages.
|
|
|
0 = Messages are shown in a message box.
1 = Messages are sent to sysout. In a thin client environment, they’re sent to the server sysout.
2 = Messages are sent to syserr. In a thin client environment, they’re sent to the server syserr.
3 = Messages are printed to a file named <program_name><number>.ads.log
|
|
|
For example, setting iscobol.exception.prefix=/tmp/ will create the file under the /tmp directory, while setting iscobol.exception.prefix=xx will create the file under the current directory and its name will start with 'xx'.
|
|
|
|
|
|
|
|
|
True = all the computations involving a number with a fractional part are performed using a precision of 36 decimal digits.
False = all the computations involving a number with a fractional part are performed using a precision of 18 decimal digits.
|
|
|
True = literals are treated as USAGE COMP in LENGTH OF functions and other integer functions.
False = literals are treated as USAGE DISPLAY in LENGTH OF functions and other integer functions.
|
|
|
True = Native numeric data items are stored in Little Endian format.
False = Native numeric data items are stored in Big Endian format.
|
|
|
|
|
|
|
|
|
|
|
|
True = Append content to the existing log file, if it exists
False = Overwrite the existing log file, if it exists
|
|
|
|
|
|
|
|
|
|
|
|
True = Activates Acucobol-GT compatibility on configuration, that means:
False = Doesn’t activate Acucobol-GT compatibility on configuration
|
|
|
True = Working-Storage and FD data are shared between programs called in recursion.
False = Each recursive program has its own Working-Storage and FD.
|
|
|
|
|
|
|
|
|
True = Activates the RM/COBOL development mode.
False = Disables the RM/COBOL development mode.
Note - this setting has currently no effect.
|
|
|
0 = The program starts in run mode and the Remote Debugger is not active.
1 = The program starts in run mode and the Runtime Framework listens for connections from the Remote Debugger.
2 = The program starts in debug mode and the Runtime Framework waits for connections from the Remote Debugger.
|
|
|
|
|
|
|
|
|
|
|
|
True = Every program compiled with the -sddp option shows the comma as the decimal separator and the dot as the thousand separator, regardless of the DECIMAL-POINT clause in the Special Names.
False = Every program compiled with the -sddp option shows the dot as the decimal separator and the comma as the thousand separator, regardless of the DECIMAL-POINT clause in the Special Names.
|
|
|
True = No errors are returned if the dyncall native library cannot be loaded during startup.
False = An error is returned if the dyncall native library cannot be loaded during startup.
|
|
|
True = No errors are returned if the stacall native library cannot be loaded during startup.
False = An error is returned if the stacall native library cannot be loaded during startup.
|
|
|
|
|
|
|
|
|
|
|
|
True = String boundaries are checked at Runtime in order to provide more details in case of "out of bounds" errors. If a program addresses an invalid character position, an error message is shown and the program exits. The error message informs about the data item name and the problematic character position.
False = String boundaries are not checked. If a program addresses an item that is outside the valid range, a generic "out of bounds" error message is shown and the program exits. The -m1 option may avoid the crash and make the program access the area of the next Working-Storage item instead.
|
|
|
True = a reference modifier with length = 0 behaves as if length was omitted (e.g. src-item(2:0) behaves like src-item(2:), so that the content of src-item from byte 2 to the end is returned).
False = a reference modifier with length = 0 returns a variable whose length is 0 (e.g. src-item(2:0) returns "").
|
|
|
|
|
|
|
|
|
True = inquire the system to obtain the screen resolution each time TERMINAL-INFO is accepted from TERMINAL-ABILITIES.
False = inquire the system to obtain the screen resolution only the first time TERMINAL-INFO is accepted from TERMINAL-ABILITIES. Return the stored values to the next ACCEPT statements.
|
|
|
1 = Settings of environment variables. Configuration properties set in the command line or in the external environment are not traced in the logfile. Only the properties found in the configuration file and the properties set by the program are traced. The list of processed configuration files is also traced.
2 = Program starts and program ends.
4 = Paragraph starts and paragraph ends as well as method starts and method ends (program must be compiled with -d or -dx).
16 = Content of keys (works only in conjunction with 8).
32 = Content of record (works only in conjunction with 8).
64 = Client / Server activity in terms of connection and disconnection (isCOBOL Server environment).
128 = RPC calls for communication between client and server (isCOBOL Server environment).
1024 = Library routine starts and library routine ends. It works only in conjunction with the value 2.
|
|
|
True = The content of PIC N items is stored in UTF-16 Little Endian encoding.
False = The content of PIC N items is stored in UTF-16 Big Endian encoding.
|
|
|
|
|
|
True = Set the value of numeric data items to zero and non-numeric data items to spaces if a CGI variable is empty or does not exist.
False = Don’t clear the value of data items if a CGI variable is empty or does not exist.
|
|
|
|
|
|
True = "Pragma: no-cache" is added to the HTTP response header.
False = "Pragma: no-cache" is not added to the HTTP response header.
|
|
|
True = All the cookies can be read through the accept() method as if they were input fields. The cookie name is case sensitive.
False = Cookies can’t be read through the accept() method.
|
|
|
|
|
|
|
|
|
|
|
|
True = Programs are automatically cancelled from memory when the main program returns (stateless).
False = Programs remain in memory unless explicitly cancelled by a CANCEL statement (stateful)
|
|
|
|
|
|
|
|
|
|
|
|
True = Embedded values in the HTML code are expected to be prefixed by colon, E.g. <html>hello :myvar world</html>.
False = Embedded values in the HTML code are expected to be enclosed by double percent sign, E.g. <html>hello %%myvar%% world</html>.
|
|
|
|
|
|
True = Enables logging of the REST activity at global level .
False = No log of the REST activity is performed at global level .
|
|
|
True = Enables logging of the REST activity for the specified method name .
False = No log of the REST activity is performed the specified method name .
|
|
|
|
|
|
True = Enables logging of the SOAP activity at global level .
False = No log of the SOAP activity is performed at global level .
|
|
|
True = Enables logging of the SOAP activity for the specified method name .
False = No log of the SOAP activity is performed the specified method name .
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 = The background color is high intensity.
1 = The background color is forced to low intensity.
2 = The background color is forced to high intensity.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FontName is the name of the font. The default value is Sans Serif.
FontStyle is the style of the font such as bold, italic, or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard default font (Sans Serif); no error is raised.
|
|
|
|
|
|
FontName is the name of the font. The default value is Monospaced.
FontStyle is the style of the font such as bold, italic or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard fixed font (Monospaced); no error is raised.
|
|
|
|
|
|
0: VALUE_ANTIALIAS_DEFAULT is used for all controls
1: VALUE_ANTIALIAS_ON is used for all controls
2: VALUE_ANTIALIAS_OFF is used for all controls
3: VALUE_ANTIALIAS_OFF is used for Frame, List-Box and Grid controls, as it happened in version 2013 R2 and previous.
|
|
|
FontName is the name of the font. The default value is SansSerif.
FontStyle is the style of the font such as bold, italic or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard large font (Sans Serif); no error is raised.
|
|
|
|
|
|
FontName is the name of the font. The default value is SansSerif.
FontStyle is the style of the font such as bold, italic or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard medium font (Sans Serif); no error is raised.
|
|
|
|
|
|
FontName is the name of the font. The default value is SansSerif.
FontStyle is the style of the font such as bold, italic or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard small font (Sans Serif); no error is raised.
|
|
|
|
|
|
FontName is the name of the font. The default value is Monospaced.
FontStyle is the style of the font such as bold, italic or bolditalic.
FontDim is the dimension of the font.
If FontName cannot be found, then FontStyle and FontDim are applied to the standard traditional font (Monospaced); no error is raised.
|
|
|
|
|
|
True = The Accept timer is reset after each time the user inputs a new digit.
False = The Accept timer stops as soon as the user inputs the first digit.
|
|
|
True = Control whose colors are not specified by the program inherit colors from the parent window.
False = Control whose colors are not specified by the program inherit colors from the Look And Feel.
|
|
|
|
iscobol.gui.Control.event
|
Control can be one of the following:
|
|
|
|
•
|
MODFIY window-handle VISIBLE|ENABLED
|
|
|
|
|
•
|
MODIFY window-handle VISIBLE|ENABLED
|
|
|
|
|
|
|
|
•
|
MODFIY window-handle VISIBLE|ENABLED
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
True = A date validation is automatically performed when the user leaves a DateEntry field. If the date is not valid, an error message is shown and the focus is kept on the field. You can configure the message text by setting iscobol.gui.date_entry.errormessage.
False = No validation is automatically performed when the user leaves a DateEntry field.
|
|
|
0...the color specified by this property is always applied. This is the default behavior.
1...the color specified by this property is applied only if the COLOR property was not used on the Entry-Field.
|
|
|
True = An error message is shown when the user puts an alphabetic value into a numeric entry-field.
False = A beep is played when the user puts an alphabetic value into a numeric entry-field.
|
|
|
|
|
|
0...the color specified by this property is always applied. This is the default behavior.
1...the color specified by this property is applied only if the COLOR property was not used on the Entry-Field.
|
|
|
True = Moving the mouse over a read-only field, the mouse shape remains an arrow
False = Moving the mouse over a read-only field, the mouse shape changes to a vertical bar
|
|
|
|
|
|
|
|
|
True = All controls for which the EXCLUDE-EVENT-LIST property is not specified assume EXCLUDE-EVENT-LIST=1
False = All controls for which the EXCLUDE-EVENT-LIST property is not specified assume EXCLUDE-EVENT-LIST=0
|
|
|
True = Pressing F4 when the focus is on a ComboBox causes the list of values to be expanded.
False = Pressing F4 when the focus is on a ComboBox causes the Accept to be interrupted with a value of 4 in the crt status.
|
|
|
True = Entry field controls that do not have boxed style or 3-D style set use no-box style by default.
False = Entry fields controls that do not have boxed style or 3-D style set use box style by default.
|
|
|
True = During Accept the runtime has to refresh the values of the variables defined in SCREEN SECTION.
False = During Accept the runtime doesn’t refresh the values of the variables defined in SCREEN SECTION.
|
|
|
|
|
|
True = Grid columns of grids with the Adjustable-Columns style are automatically resized when the window is resized and a layout manager is involved.
False = Grid columns are not affected by layout managers.
|
|
|
True = Grids don’t fire drag events.
|
|
|
|
|
|
|
|
|
-1 = no limit on buffering
0 = disable keyboard buffering
>0 = specifies the number of keyboard events that must be bufferized
|
|
|
True = The isCOBOL logo is displayed on the windows of the program.
False = The Java logo (coffee cup) is displayed on the windows of the program.
|
|
|
False = An "Invalid handle" message is shown and the program terminates.
|
|
|
True = You can show a custom icon on INDEPENDENT, DOCKING and MDI-PARENT windows by setting their Icon property. Alternatively you can show the isCOBOL logo on independent windows by setting iscobol.gui.icon=true.
False = You can’t show a custom icon on INDEPENDENT, DOCKING and MDI-PARENT windows by setting their Icon property. The Java logo (coffee cup) is used.
|
|
|
True = Numeric and edited fields are automatically right-aligned.
False = Numeric and edited fields are left-aligned, unless otherwise specified.
|
|
|
True = Spaces on the right side of the title label are trimmed away.
False = Spaces to the right of the title label are not removed.
|
|
|
True = lists dropped by menu bar and combo-boxes as well as tool-tips are in the background and can be covered by a web-browser control on the screen.
False = lists dropped by menu bar and combo-boxes as well as tool-tips are in the foreground and cannot be covered by any control.
|
|
|
True = ListBox columns are automatically resized when the window is resized and a layout manager is involved.
False = ListBox columns are not affected by layout managers.
|
|
|
True = menu bar items with no subitems require two steps in order to be selected by keyboard: press Alt+keyletter to activate the item and press Enter to select it (Java Swing behavior).
False = menu bar items with no subitems are selected by keyboard by just pressing Alt+keyletter.
|
|
|
True = the Screen Section name of controls is shown in the message box produced by pressing Alt+Pause.
False = the internal name of controls is shown in the message box produced by pressing Alt+Pause.
|
|
|
True = a LAF dependent border is applied to all controls with a BOXED style (e.g. EntryFields, ComboBoxes, Grids...). It doesn’t work on controls with the 3-D style.
False = a standard black border is applied to all controls with a BOXED style unless the Border-Color property is set for them.
|
|
|
|
|
|
|
|
|
True = Push-Buttons can always be activated by pressing Enter when they have the focus.
False = Push-Buttons can be activated by pressing Enter when they have the focus only if the iscobol.key.enter setting includes "termination=13".
|
|
|
True = click on Push-Button is always intercepted even if the focus was forced on an input field by setting Screen-Control items in the field After Procedure.
False = click on Push-Button is not intercepted if the focus was forced on an input field by setting Screen-Control items in the field After Procedure.
|
|
|
-2 = Clicking on the close button has no effect.
0 = Clicking on the close button closes the window and the program terminates.
>0 = Clicking on the close button raises an exception on the current ACCEPT. The CRT STATUS variable is set to the value of quit_mode.
|
|
|
|
|
|
True = stuff is displayed after the last item on line line-number.
False = stuff is displayed at line line-number column 1.
|
|
|
|
|
|
|
|
|
True = leading zeroes are shown when displaying numeric data
False = leading zeroes are not shown when displaying numeric data
|
|
|
True = all graphical controls are TEMPORARY by default
False = all graphical controls are PERMANENT by default
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Setting the property to com.iscobol.gui.client.swing.JDICWebBrowser requires that you install JDIC separately, since this component is no longer distributed along with isCOBOL.
Setting the property to com.iscobol.fx.JFXWebBrowser requires Java7 or higher. With this implementation the MSG-BEFORE-NAVIGATE event is never fired.
Note - JavaFX is not a real web-browser, it's a web-view component that interpretes html, dom, css and javascript content. Therefore there are some limitations if you compare it with a real web-browser, for example:
|
•
|
mailto: and ftp: protocols are not supported
|
|
|
|
|
|
|
True = a window with the AUTO-RESIZE style can be resized only to a smaller dimension; it cannot be increased
False = a window with the AUTO-RESIZE style can resized freely
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
True = clear the area as soon as the user inputs a digit.
False = don't clear the area where the ACCEPT is performed. Keep the value on video and allow to overwrite the single digits.
|
|
|
True = antialiasing is applied to fonts on video.
False = fonts on video are shown as they are.
|
|
|
True = DISPLAY statements longer than one line will wrap around on a character-based display.
False = DISPLAY statements longer than one line will be truncated on a character-based display.
|
|
|
True = The field is filled with spaces from the cursor position until the end. If the AUTO clause was used or the program is compiled with the -va option, this causes the cursor to be automatically moved to the next input field or the termination of the accept if no more fields are available.
False = The field is filled with spaces from the cursor position until the end, but the cursor position is unchanged.
|
|
|
3 = underscore shape, becomes block while in insert mode
|
|
|
|
|
|
True = on character-based screens, the SIZE clause (either implicit or explicit) in the ACCEPT specifies the number of positions on the screen, not the number of characters. For example, an ACCEPT with SIZE 10 can accept 10 latin characters or 5 chinese characters.
False = on character-based screens, the SIZE clause specifies the number of characters.
|
|
|
True = the user can select an area in the window by dragging the mouse. On character-based screens the highlighted text is copied to the clipboard.
False = dragging the mouse in the window doesn’t produce a selection.
|
|
|
True = numeric edited fields are not cleared when the first valid character is imputed and the editing characters are automatically skipped, except for the B editing character. Only the fields whose edited picture contains characters different from '9', 'Z', '+', and '-' are affected.
False = numeric edited fields are cleared when the first valid character is imputed. The editing characters are removed as well during the cleaning.
|
|
|
True = lines and boxes whose color is black as rendered with a 3D effect.
False = lines and boxes are rendered normally.
|
|
|
True = don't clear the area where the ACCEPT is performed.
False = clear the area where the ACCEPT is performed.
|
|
|
True = clear the area as soon as the user inputs a digit.
False = don't clear the area where the ACCEPT is performed. Keep the numeric value on video and allow to overwrite the single digits.
|
|
|
|
|
|
True = read content from screen during ACCEPT.
False = don’t read content from screen during ACCEPT.
|
|
|
|
|
|
True = c-tree works in stand-alone mode. This mode supports one client process only, so it is suggested that it is used only in an Application Server environment or single-user installations.
False = c-tree works in client/server mode.
|
|
|
False = The Runtime Framework searches for the c-tree configuration in CTREE_CONF.
|
|
|
True = "EXTFH input" does not use the "isCOBOL FileManager chooser" but rather uses the "Default isCOBOL File manager"
False = "EXTFH input" uses the "isCOBOL FileManager chooser"
|
|
|
|
|
|
True = The file_prefix is also used for files whose name begins with "/" or "\".
False = The file_prefix is used only for files with a relative path name.
|
|
|
|
|
|
U / u = Data file names are converted to upper case. Conversion occurs before applying file prefix and file suffix.
L / l = Data file names are converted to lower case. Conversion occurs before applying file prefix and file suffix.
|
|
|
True = All open files are automatically closed when the program exits.
False = Open files are not closed when the program exits.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
True = The Runtime Framework searches for the name of the file among the environment variables. If found, its value is used in place of the file name:
False = The Runtime Framework searches for the name of the file among the environment variables only if it is preceded by " -E":
|
|
|
|
|
|
|
|
|
True = All files opened in EXTEND mode are treated as if they were declared OPTIONAL. If the file does not exist, it is created.
False = Standard rules are applied. Opening non-existing files when in EXTEND mode causes an error.
|
|
|
True = Does not return errors when opening an indexed file that contains more keys than are described by the program.
False = Returns a mismatch error when opening an indexed file that contains more keys than are described by the program.
|
|
|
|
|
|
True = More locks on the same record can be acquired in the same run unit.
False = Only one lock on the same record can be acquired in the same run unit.
|
|
|
True = check keys structure on OPEN and return error on mismatch.
False = don’t check keys structure on OPEN.
|
|
|
|
|
|
FileName must match the physical file name declared in the COBOL program with hyphens replaced by underscores and must be lower-case regardless of the case used in the program. Here are some examples:
Note: The names of the properties that are dynamically set inside the program using SET ENVIRONMENT are normalized by the runtime and therefore the above rules can be ignored.
|
|
|
|
|
|
True = The record data is returned to the program even if the record is locked.
False = The record data is not returned to the program if a lock condition occurs.
|
|
|
True = Wait for the record to become unlocked if a lock condition occurs.
False = Return the lock condition to the program.
|
|
|
True = A READ WITH NO LOCK returns a lock condition if the record is locked.
False = A READ WITH NO LOCK reads the record even if it’s locked.
|
|
|
True = The file extension is removed from the file name before opening the file.
False = The file extension is not removed from the file name before opening the file.
|
|
|
|
|
|
|
|
|
|
|
|
True = READ WITH LOCK, either explicit or implicit, doesn’t lock the record if the file is open in INPUT mode.
False = READ WITH LOCK, either explicit or implicit, locks the record even if the file is open in INPUT mode.
|
|
|
True = All files opened in I-O mode are treated as if they were declared OPTIONAL. If the file does not exist, it is created.
False = Standard rules are applied. Opening non-existing files in I-O mode causes an error.
|
|
|
|
|
|
FileName must match the physical file name declared in the COBOL program with hyphens replaced by underscores and must be lower-case regardless of the case used in the program. Here are some examples:
|
|
|
True = Use the com.iscobol.io.DynamicLSeqMF_N class as the default for line sequential files.
False = Use the com.iscobol.io.Dynamic=DynamicLSeq8bit as the default for line sequential files.
|
|
|
|
|
|
|
|
|
True = If a relative or sequential file is opened by a process even without using any kind of lock, no other process can lock it in exclusive mode. The Java property sun.nio.ch.disableSystemWideOverlappingFileLockCheck should be set to true as well.
False = If a relative or sequential file is opened by a process without any locking, another process can lock it in exclusive mode.
|
|
|
|
|
|
True = Print files print a page advance record when the file is closed, unless the close contains the NO REWIND phrase.
False = Print files don’t print a page advance record when the file is closed.
|
|
|
|
|
|
|
|
|
|
|
|
FileName must match the physical file name declared in the COBOL program with hyphens replaced by underscores and must be lower-case regardless of the case used in the program. Here are some examples:
|
|
|
|
|
|
|
|
|
|
|
|
True = spaces are removed from physical file names before looking for the files on disk (e.g. "C:\t m p \ file1" is treated as "C:\tmp\file1").
False = spaces are not removed from physical file names before looking for the files on disk.
Note - spaces are removed only from the name used by the COBOL program, not from file.prefix and current directory.
|
|
|
|
|
|
FileName must match the physical file name declared in the COBOL program with hyphens replaced by underscores and must be lower-case regardless of the case used in the program. Here are some examples:
|
|
|
|
|
|
|
|
|
True = Trailing spaces are automatically removed before writing a line sequential file. When reading, the destination item is automatically filled with spaces before the line is read.
False = Trailing spaces are not removed before writing a line sequential file. When reading, the destination item is not cleared before the line is read.
|
|
|
|
|
|
2 = Use extended EXTFH2 32 bit
3 = Use extended EXTFH3 64 bit
|
|
|
True = More locks on the same record can be acquired in the same run unit.
False = Only one lock on the same record can be acquired in the same run unit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A = Acucobol-GT convention
D = Data General convention
M = Micro Focus convention
R = Realia COBOL convention
|
|
|
|
|
|
|
|
|
0 = no permission, access denied to other users
1 = public permission with full access to other users
2 = public permission with read-only access to other users
|
|
|
True = The c-tree indexed file is automatically linked into isCOBOL SQL Server during the OPEN OUTPUT.
False = The c-tree indexed file is created as a standard c-tree file during the OPEN OUTPUT.
|
|
|
|
|
|
1 = . is omitted and - becomes _
2 = - is omitted and . becomes _
4 = the file extension (from the last . to the end of the name) is omitted
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
True = warnings are returned through SQLCA if the ESQL statement produces them.
False = warnings are never returned through SQLCA.
|
|
|
True = SQLCODE values different from 0 and 100 are returned as negative values.
False = SQLCODE values are always positive.
|
|
|
|
|
|
True = The JDBC driver is forced to automatically commit every SQL Statement performed by the ESQL module.
False = SQL Statements are not automatically committed. It’s program duty to COMMIT or ROLLBACK the issued statements.
|
|
|
|
|
|
|
|
|
1 = FORWARD_ONLY allows the cursor to move forward, but not backward, through the data.
2 = SCROLL_INSENSITIVE allows the cursor to move forward and backward through the data. Changes made while the cursor is open are ignored. It provides a static view of the underlying data to which the cursor refers.
3 = SCROLL_SENSITIVE allows the cursor to move forward and backwards through the data. Changes made while the cursor is open are immediately available. It provides a dynamic view of the underlying data to which the cursor refers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-1 = Trailing spaces are maintained.
0 = Trailing spaces are removed.
1 = Trailing spaces are removed and the first character of the string is always maintained, regardless of whether it is a space or not.
|
|
|
commit = Executes a COMMIT statement, then a DISCONNECT statement.
rollback = Executes a ROLLBACK statement, then a DISCONNECT statement. Note that the ROLLBACK will have effect only if you’re not working in autocommit mode, e.g. iscobol.jdbc.autocommit (boolean) must be set to false.
none = Executes only a DISCONNECT statement. A COMMIT or ROLLBACK is performed depending on the database defaults.
|
|
|
Note - Due to JDBC rules, options are evaluated only if user and password are not specified in the CONNECT statement.
|
|
|
|
|
|
|
|
|
True = Each thread created by PERFORM THREAD or CALL THREAD uses a separate database connection. The thread code is responsible to create the connection. When working with the Database Bridge, EDBI subroutines take care of managing the multiple thread connections.
False = All threads created by PERFORM THREAD or CALL THREAD share the same database connection.
|
|
|
|
|
|
|
|
|
|
|
|
True = Ignores the background color of the cell.
False = Replicates the background color of the cell.
|
|
|
True = Ignores the border style of the cell.
False = Replicates the border style of the cell.
|
|
|
True = Protects spreadsheet cells from editing.
False = Spreadsheet cells can be edited.
|
|
|
|
|
|
True = Long text wraps in the cell.
|
|
|
True = Collapse row span and avoid merging cells across rows. It implies iscobol.export.excel.remove_rows_space=true.
False = Don’t collapse row span and allow merging cells across rows.
|
|
|
True = Preserve the type of the original Report field expressions and use it for the cell data type.
False = Don’t preserve the type of the original Report field expressions and don’t use it for the cell data type.
|
|
|
True = Create page breaks in the Excel sheet.
False = Don’t create page breaks in the Excel sheet.
|
|
|
True = The Report page header is shown only on the top of the spreadsheet and is freezed during scrolling. When the content of the header changes, a new sheet is created.
False = The Report page header is shown for each Report page exported in the spreadsheet.
|
|
|
True = Ignore graphics and export only the text.
False = Export both text and graphics.
|
|
|
0 = Empty spaces that could appear between columns should not be removed.
1 = Empty spaces that could appear between columns should be removed.
2 = Empty spaces that could appear between columns should be removed. In the resulting output, useless columns are then removed as well.
|
|
|
True = Empty spaces that could appear between rows should be removed.
False = Empty spaces that could appear between rows should not be removed.
|
|
|
True = Force cell white background.
False = Don’t force cell white background.
|
|
|
|
|
|
|
|
|
True = Continue the data migration even if write errors occur.
False = Stop if a write error occurs.
|
|
|
Note: If you set this property to "vision", then ISMIGRATE requires the runcbl dynamic library to read Vision files. Set it to "com.iscobol.io.ScanVision" to have ISMIGRATE read Vision files natively.
|
|
|
|
|
|
|
|
|
|
|
|
True = The ISMIGRATE activity is traced into a log file
False = The ISMIGRATE activity isn’t traced
|
|
|
True = The output file is created with the encrypted flag. Note that some file handlers ignore such flag.
False = The encryption flag is not used to create the output file.
|
|
|
True = Don’t pass the collating sequence to the output file handler. This is useful when migrating to file systems like Dci, which do not support collating sequences.
False = Pass the collating sequence to the output file handler.
|
|
|
True = Consider the first parameter ( InputFile) as the name of the source file, and the second parameter ( OutputDir) as the name of the destination file. Useful to migrate one file at a time.
False = Consider the first parameter ( InputFile) as a list of files, and the second parameter ( OutputDir) as the name of the destination folder. Useful to migrate multiple files at a time.
|
|
|
True =Don’t perform the build of the output file. This is useful when optimizing the migration of file systems like EasyDB, which create a table when opening a file.
False = Build the output file.
|
|
|
True =Ignore the second parameter. This is useful when migrating to databases.
False = Consider the second parameter.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
True = Remove the extension from the input file name and use the resulting name as output file name.
False = Use the input file name as output file name without changes.
|
