Virtual memory shortages when COBOL programs are executing may be caused by one of the problems listed below. In each case, the process is to review the environment and program structure at the time of the memory shortage, and apply the appropriate remedy.
Too little installed memory.
Extend the memory.
Too little virtual memory.
Increase the space available for virtual memory.
Other applications executing at the same time are consuming the available memory.
Stop one or more of the other applications.
Too many files open at the same time in the execution unit.
Reduce number of files open at the same time.
Too many data items or file declarations use the EXTERNAL phrase in the execution unit.
Reduce the use of EXTERNAL data.
Too many objects (instances) are used simultaneously in the execution unit.
Reduce the number of simultaneously active objects.
[Win32] The executed application destroys the memory area.
Use the interactive debugger, CHECK function, or memory check function to investigate the cause and correct the program. Refer to "How to Use the Interactive Remote Debugger", "Using the CHECK Function", and "Using the Memory Check Function" in the "NetCOBOL Debugging Guide".
[Winx64] The executed application destroys the memory area.
Use the remote debugging function of NetCOBOL Studio, CHECK function, or memory check function to investigate the cause and correct the program. For the remote debugging function of NetCOBOL Studio, refer to the "NetCOBOL Studio User's Guide". For the CHECK Function and the Memory Check Function, refer to the "NetCOBOL Debugging Guide".
