True = the Filepool feature is enabled.

False = the Filepool feature is disabled.

 

If omitted, False is assumed.

 

Note - this property just enables the Filepool feature; you need to set iscobol.file.index.inpool to true in order to actually include files in the pool.

Specifies the maximum number of files that can be included in the pool.

True = trace batchadditions details.

False = do not trace batchaddition details.

 

If omitted, False is assumed.

True = trace config details, limited to the configuration set by the user.

False = do not trace config details.

 

If omitted, False is assumed.

True = trace complete config details, including the default configuration.

False = do not trace complete config details.

 

If omitted, False is assumed.

True = trace prefetch details.

False = do not trace prefetch details.

 

If omitted, False is assumed.

True = trace errors in the log file.

False = do not trace errors in the log file.

 

If omitted, True is assumed.

True = trace EOF errors.

False = do not trace EOF errors.

 

If omitted, False is assumed.

True = trace NOTFOUND errors.

False = do not trace NOTFOUND errors.

 

If omitted, False is assumed.

Specifies the name of the log file where to trace c-tree client operations.

When this property is set, some log is enabled by default: error, info and warning. Set the other iscobol.file.index.log properties to true or false if you wish to disable or enable a particular log.

 

If omitted, no log is created.

True = trace generic information in the log file.

False = do not trace generic information in the log file.

 

If omitted, True is assumed.

True = trace profile information in the log file.

False = do not trace profile information in the log file.

 

If omitted, False is assumed.

True = trace warning information in the log file.

False = do not trace warning information in the log file.

 

If omitted, True is assumed.

True = Any UNLOCK performed in the run unit on a file will remove the lock on the file even if the record was locked by another OPEN instance.

False = The lock is removed only if the UNLOCK is performed on the same OPEN instance where the READ WITH LOCK was performed.

 

This property can be set only if iscobol.file.index.autolock_allowed (boolean) is set to true.

 

If omitted, False is assumed.

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.

 

If omitted, False is assumed.

True = write operations are buffered in order to speed up performance.

False = write operations are not buffered.

 

If omitted, False is assumed.

Specifies the number of write operations that must be buffered at a time.

 

If omitted, 10 is used.

True = files open for output or extend are managed with bulk addition (indexes are written at the close of the file) to speed up performance.

False = files open for output or extend are managed without bulk addition.

 

If omitted, False is assumed.

True = connect to c-tree server during runtime initialization.

False = connect to c-tree server at the first open of a c-tree file.

 

If omitted, False is assumed.

Specifies the extension for the data file.

 

If omitted, then .dat is assumed.

True = data records are compressed using zlib algorithm.

False = data records are not compressed.

 

If omitted, False is assumed.

This property selects the zlib compression level. Valid values are between 1 and 9 where 1 gives best speed but use more disk space and 9 gives best compression at the expenses of performance.

 

If omitted, then 1 is assumed.

This property specifies the strategy for data compression. Possible values are:

0 = Use the default zlib compression strategy.

1 = Use the zlib filtered compression strategy.

2 = Use zlib Huffman only compression strategy.

3 = Use zlib RLE compression strategy.

4 = Use zlib fixed compression strategy.

 

If omitted, 0 is assumed.

Specifies the algorithm for data compression. Valid values are:

zlib = zlib algorithm is used.

rle = rle algorithm is used.

 

If omitted, then rle is assumed.

True = files are encrypted using ctCAMO encryption algorithm.

False = files are not encrypted.

 

If omitted, False is assumed.

This property specifies the list of files that should be included in the current instance. Multiple names must be separated by comma. Wildcards are supported. See Configuring multiple instances for details.

This property specifies the list of files that should be included in the current instance. Multiple names must be separated by comma. Wildcards are supported.

 

At the end of each file name you can put an ordinal number that is the number of the path between iscobol.file.index_path_mapping paths. In this way it’s possible to specify a file mapping for each path maggping.

Example:

 

iscobol.file.index.1.path_mapping=/dir1,/dir2

iscobol.file.index.1.file_mapping_p=customers1,invoices1,reports2,discounts

 

The instance mapping is valid for the files customers and invoices when they’re are under /dir1, for reports when it’s is under /dir2 and for discounts, wherever it is.

 

See Configuring multiple instances for details.

This property specifies the backward compatibility for every new file created in the current c-tree instance. It affects default attributes such as the default compression algorithm.

Set this property if you plan to use the same c-tree files also with previous c-tree major versions.

Possible values are:

1 = create files compatible with c-tree v1

2 = create files compatible with c-tree v2

3 = create files compatible with c-tree v3

 

The default value is 3.

 

Note - the compatibility with previous versions might be affected also by the PAGE_SIZE setting in the server configuration. Be sure to use the same page size between the current c-tree version and the previous c-tree version you want to be compatible with.

True = files are created with fixed length records.

False = files are created with variable length records.

 

If omitted, False is assumed.

True = if a file segment is missing, DELETE FILE deletes the other segment.

False = if a file segment is missing, DELETE FILE returns a ‘file corrupted’ error.

 

If omitted, False is assumed.

Specifies the extension for the index file.

 

If omitted, then .idx is assumed.

True = files are included in a pool to speed up the next OPEN operations.

False = files are not included in a pool.

 

If omitted, False is assumed.

 

Note - the iscobol.file.index.filepool global setting must be set to true, otherwise this property will be ignored.

True = extra keys in the file are not allowed.

False = extra keys in the file are allowed.

 

If omitted, True is assumed.

True = index files are compressed using zlib algorithm. Leading and padding compression are applied.

False = index files are not compressed.

 

If omitted, False is assumed.

True = leading compression is applied on index files.

False = leading compression is not applied on index files.

 

If omitted, False is assumed.

True = padding compression is applied on index files.

False = padding compression is not applied on index files.

 

If omitted, False is assumed.

True = RLE compression is applied on index files.

False = RLE compression is not applied on index files.

 

If omitted, False is assumed.

True = Only RLE and PADDING compression are allowed on index files.

False = Only LEADING and PADDING compression are allowed on index files.

 

If omitted, True is assumed.

True = locked records are returned.

False = locked records are not returned.

 

If omitted, False is assumed.

True = if a record is locked, wait until lock is released.

False = if a record is locked, return a record locked error.

 

If omitted, False is assumed.

True = trace batchadditions details.

False = do not trace batchaddition details.

 

If omitted, False is assumed.

True = trace prefetch details.

False = do not trace prefetch details.

 

If omitted, False is assumed.

True = trace errors in the log file.

False = do not trace errors in the log file.

 

If omitted, False is assumed.

True = trace EOF errors.

False = do not trace EOF errors.

 

If omitted, False is assumed.

True = trace NOTFOUND errors.

False = do not trace NOTFOUND errors.

 

If omitted, False is assumed.

Specifies the name of the log file where to trace c-tree client operations.

 

If omitted, no log is created.

True = trace generic information in the log file.

False = do not trace generic information in the log file.

 

If omitted, False is assumed.

True = trace profile information in the log file.

False = do not trace profile information in the log file.

 

If omitted, False is assumed.

This property specifies how many instances can be created. It is mandatory in order to work with multiple instances. The value must range between 2 and 99. Any value less than 2 is considered as 2 while any value greater than 99 is considered 99. Note that the default instance is counted, so you should calculate the value of this property by adding 1 to the highest instance number you put in your property names.

See Configuring multiple instances for details.

True = return an error if record is larger than maxlen bytes..

False = record larger than maxlen bytes is allowed.

 

If omitted, False is assumed

True = files are created in memory rather than on disk.

False = files are created on disk.

 

If omitted, False is assumed.

True = memory files are removed when the c-tree Server is shut down.

False = memory files are removed when the client session that creates them terminates.

 

If omitted, True is assumed.

True = use optimistic strategy when adding records. Unique key violation is not checked before writing the whole record. This provides better performance.

False = use pessimistic stragety when adding records.. Unique key violation is checked before writing the whole record.

 

If omitted, True is assumed

This property specifies the password for the connection to the c-tree Server.

This property specifies the list of paths that should be included in the current instance. Multiple paths must be separated by comma. See Configuring multiple instances for details.

True = read operations are buffered in order to speed up performance.

False = read operations are not buffered.

 

If omitted, False is assumed.

 

The number of buffered records is controlled by iscobol.file.index.prefetch.records.

The locking on these records is controlled by iscobol.file.index.prefetch.allowwriters (boolean).

True = prefetched records are not locked.

False = prefetched records are locked.

 

If omitted, False is assumed.

 

Note - if the file has an implicit or explicit LOCK MODE AUTOMATIC WITH LOCK ON MULTIPLE RECORDS, then all the prefetched records are locked, since these records are retrieved with the same options of the READ NEXT that instigates the read a-head operation.

Specifies the number of read operations that must be buffered at a time.

 

If omitted, 10 is used.

 

Note - this value should be set carefully according to the number of read operations between a Start and another. Having an high value for this setting and few read operations between a Start and another might slow down performance as useless records are loaded in memory even if the program will not read them.

This property specifies how many seconds the prefetched records should be kept in memory.

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.

 

If omitted, False is assumed.

True = enable support for creating a ROWID field/index.

False = disable support for creating a ROWID field/index.

 

ROWID is required for creating Full-Text Indexes, so this option is necessary if Full-Text Search is desired.

 

If omitted, False is assumed.

This property sets the size of the rowid hidden field in the record header.

Accepted values are 8 and 4.

 

The default value is 8.

True = use RPC calls to communicate with c-tree server

False = use standard c-tree calls to communicate with c-tree server (recommended only for diagnostic purposes)

 

If omitted, True is assumed

True = enable CRC checks on the RPC data buffers that are sent/received over the network. Recommended only for diagnostic purposes.

False = disable CRC checks on the RPC data buffers that are sent/received over the network.

 

If omitted, False is assumed

This property specifies the server name and IP address.

The value can be one of the following syntaxes:

 

If omitted, then FAIRCOMS is assumed.

True = advance to the next record when a locked record is encountered.

False = do not advance to the next record when a locked record is encountered.

 

If omitted, False is assumed.

True = use SSL (Secure Socket Layer) to connect to the c-tree Server.

False = do not use SSL (Secure Socket Layer) to connect to the c-tree Server.

 

If omitted, False is assumed.

This property specifies the path and name of the pem file for SSL certificate.

True = transaction support is on.

False = transaction support is off.

 

If omitted, True is assumed.

True = turn on optimization that improves performance for functions that use autocommit.

False = turn off optimization that improves performance for functions that use autocommit.

 

If omitted, False is assumed.

 

When set to True, it still guarantees atomicity and consistency of transaction but not durability because the last transaction could be lost.

True = file operations are transaction dependent.

False = file operations performed within an active transaction are not affected by the transaction ending operation (commit or abort).

 

If omitted, False is assumed

 

Note - this setting doesn’t match with the ‘dependent’ information shown by the command ctutil -info.

True = turns on transaction logging. It is indicated when data safety is more important than performance. Files are created with c-tree file mode ctTRNLOG and are automatically recovered after a crash.

False = turns off transaction logging. It is indicated when performance is more important than data safety.

 

If omitted, False is assumed.

True = only the locks on records updated during the transaction are released at transaction commit while all other locks not specifically released are held. At transaction rollback instead records locks are held unconditionally.

False = all pending locks are released during a transaction commit or rollback.

 

If omitted, False is assumed.

This property specifies the user name for the connection to the c-tree Server.

 

If omitted, then guest is assumed

True = check if c-tree client and server versions match during the connection at runtime initialization.

False = do not check if c-tree client and server versions match during the connection at runtime initialization.

 

If omitted, False is assumed.