VSI OpenVMS Forum

I'm running into the problem that the C-compiler complains about "Insufficient Virtual Memory" According to the C-manual
one should than "Increase the PAGEFILEQUO process quota and/or the VIRTUALPAGCNT sysgen parameter"
However on my system they are 2147483632 and 2147483647 respectively which appears to be the maximum.

Are there other settings to be considered to overcome this problem?

Is the memory + pagefile too small?

Give us some more context!
Small or humongous program?
Did it used to work? What changed - more code? more includes?
Does it happen right-away or does it compute for a while before blowing up?
Do the virtual pages build up all the time or suddenly jump? What is the last observeable number?
Check with $show proc /cont/id =...

Is the process you are running the compiler in spawned or something with reduced quota? GETJPI?

Hein.

Jouk,

OpenVMS version and architecture ?

VIRTUALPAGECNT is obsolete since OpenVMS Alpha V7.0 and defaults to %X7FFFFFFF

Your SYSUAF /PGFLQUOTA quota seems unusually high. Did you increase it, when encountering the INSVIRMEM error ? Or had this quota been previously increased (by whom and why) ?

Volker.

The problem occurs while porting an open source software package called libxc. So if you are interested I can post the code. It uses some includes and gives the error after some time compiling. It is compiled from the command line of an "set host" session either using MMS or just the CC command.

I'm using VSI C V7.4-001 on OpenVMS IA64 V8.4-2L3

The pagefile quota were raised much earlier. I run sometimes very memory intensive programs.

Added in 3 hours 21 minutes 28 seconds:
Hi,

I found a "work-around" for this package: Compiling the files that give the problem with the C++ compiler (and adding some extern"C" {} statements for for linking) gave a test program, which I could run giving the correct results.

Jouk.

Jouk,

are you sure, that you have enough pagefile space ? SHOW MEM/FILES ? Your PGFLQUOTA allows up to nearly 1 TB of VA space.

If you would want to drill down on the INSVIRMEM error, you could run system service logging (SET PROC/SSLOG) and find out, which system service call actually failed ...

Volker.