Enables you to set the maximum amount of memory to be made available to the run-time system, or to cause the run-time system to perform physical cancels instead of logical cancels.
Note:
Restriction:
These switches are supported for native COBOL only.
Properties:
| Default: |
The maximum number of bytes available to the run-time system. |
| Type: |
General |
Comments:
This switch is lower-case "L", not upper-case "I".
The format of this switch is lnnnnnn, where nnnnnn is the amount of memory in bytes to be made available to the run-time system.
You can use this switch to limit the amount of memory the run-time system will use. This might be useful to enable you to tune your system.
By default the run-time system performs logical cancels unless all available memory has been used up. As far as your programs are concerned, the behavior of logical and physical cancels is identical, but logical cancels are faster. A logical cancel flushes all file buffers but does not release any memory. To force all cancels to be physical, you must specify this switch with parameter zero; for example:
By default, when the run-time system requires memory space it checks that the new request does not exceed the available memory. If it does, the memory that should have been freed by any cancels is freed and the run-time system repeats its request for memory. The run-time system loads programs that have been logically canceled in preference to reloading from disk.
Statically linked COBOL programs cannot be physically canceled because they cannot be removed from memory.
Duplicate entry point names are not allowed in statically linked programs; you must ensure that all such programs have unique entry point names.
Logical cancels behave in the same way as these physical cancels under statically linked programs. Therefore, an application developed using .int and .gnt files with logical cancels should exhibit the same behavior when generated as object code files and statically linked. However, if you used physical cancels and duplicated entry point names while developing the application, the application might fail to static link.