HP 3000 Manuals

Run-Time Tuneables [ COBOL/HP-UX Operating Guide for the Series 700 and 800 ] MPE/iX 5.0 Documentation


COBOL/HP-UX Operating Guide for the Series 700 and 800

Run-Time Tuneables 

The following sections describe the run-time tuneables available.

cobconfig_error_report 

Syntax: 

set cobconfig_error_report={TRUE|FALSE}

Value:

TRUE or FALSE

If FALSE, do not report any errors during processing the configuration
file.

Default: 

TRUE. Any errors detected will be reported and the RTS will terminate.

command_line_accept 

Syntax:

set command_line_accept={TRUE|FALSE}

Value: 

TRUE or FALSE

If TRUE, the first ACCEPT takes the input from the command line.

Default: 

FALSE. The first ACCEPT will take the input from the user.  This provides
direct ANSI conformance.  You should set this if you wish to execute a
program which has been generated from convert3 or convert5.

dynamic_memory_limit 

Syntax: 

set dynamic_memory_limit=integer

Value:

integer

where integer is the maximum size of memory to be allocated dynamically
at run time, and is operating system dependent.  Any CANCELs performed
before this memory limit is reached will not release the memory occupied
by the program being CANCELed, so that the program is available to be
reused and hence CALL/CANCEL performance will be greatly increased.  This
mode of working is called "logical Cancels".

Note that as far as your program is concerned, the behavior of logical
and real CANCELs is identical.  If the dynamically allocated memory
requirements exceed the size you set for dynamic_memory_limit, then all
the memory that should have been freed by any CANCELs is freed.  If you
set this limit to zero, logical CANCELs will be disabled.

Default: 

Logical cancels will be used.  This run-time tuneable is equivalent to
the -I run-time switch.

Note that the value of -I will be used if the values are different.

dynamic_dictionary_limit 

Syntax: 

set dynamic_dictionary_limit=integer

Value:

integer

where integer is the maximum size of memory to be allocated dynamically
at run time for use by virtual heaps.

The Compiler and Generator use virtual heaps when processing your
programs, and this size is operating system dependent.  If the memory
limit is exceeded, the memory allocated to virtual heaps will be paged by
the Micro Focus COBOL system onto disk.  If the amount of memory
allocated to virtual heaps is not large enough to process your programs,
then the compilation and generation times may be increased due to the
overheads of paging the virtual heap accesses to disk.  This run-time
tuneable is equivalent to the -d run-time switch.  Note that the value of
-d will be used if the values are different.

Default:

30 buffers of 8k.

isam_block_size 

Syntax: 

set isam_block_size={512|1024|2048|4096}

Value: 

512, 1024, 2048 or 4096

Selects the block size to use when creating indexed files.  Uses 512 to
create files with a block size of 1/2k, 1024 to create files with a block
size of 1k, 2048 to create files with a block of of 1 and 1/2k and 4096
to create files with a block size of 2k.  This tuneable replaces the
cobcf utility which was available on some earlier products.

Default: 

1024.

isam_open_key_check 

Syntax:

set isam_open_key_check={TRUE|FALSE}

Value: 

TRUE or FALSE

Specifies whether or not the key descriptions specified in the program
should be verified with those in an existing file during open processing.

Default:

FALSE.

lock_mode 

Syntax: 

set lock_mode={0|1|2}

Value: 

0, 1 or 2

Selects the locking implementation to be used, as follows:

0        uses the locking mechanism provided by V1.3.0 and earlier
         versions.

1        provides compatibility with DOS and OS/2 locking mechanisms.

2        provides interlanguage locking.  This method causes record locks
         to lock the physical record.

Default: 

0

same_proc_excl_detection 

Syntax: 

set same_proc_excl_detection={TRUE|FALSE}

Value:

TRUE or FALSE

Detects if you have tried to open a file multiple times in one run-unit.
If TRUE, any OPEN request will have conditions applied to determine
whether or not it is already open, and, if so, if it was opened
exclusively, in which case a file error is generated.  Currently, if the
same file is opened twice by the same run-unit, no file error is
generated.  This flag should be set to TRUE for RMCOBOL compatibility.

Default: 

FALSE.



MPE/iX 5.0 Documentation