Page File Quota of a VMS process

[Sk Noorul Hassan]

Hi,
The Page file quota of a process is getting decreased slowly as i/o goes on increasing. The process is responsible for serving a user request from the server. After the Page file quota reached a certain level, it is unable to serve the request and starts giving erroron main server against the process name. Some times the error clears automatically, may be due to user logged out or may be due to cancellation of some request by user. Once the user logs off & logs in freshly it worked normally till it reaches the limit again. Any suggestion to improve the situation.

[Kris Clippeleyr]

Hi,
Based on your information, I guess that the app is suffering from a memory leak.
Do the I/Os ever complete?
A (temporary) remedy would be to increase the PGFLQUOTA of the process in question.
Regards,
Kris (aka Qkcl)

[Peter Zeiszler]

Also check the pagefile quota for the account that starts it and the PQL_DPGFLQUOTA & PQL_MPGLQUOTA for the system. The process might be starting with those values.

I received a file from DEC awhile ago called quota that is useful for watching quotas. I am attaching that file.

[Peter Zeiszler]

I also have had issues with memory leaks and have created script that creates a log file with long term monitoring in mind.

[Peter Zeiszler]

http://h18000.www1.hp.com/support/asktima/operating_systems/0097011D-61669060-1C02A1.html

The original source of the quota file.
Wanted to make sure others knew where it might reside.

I still like askcompaq :D

[Volker Halle]

As others have already indicated, this clearly looks like a memory leak in the application.

You would need to find out, exactly which operation (and code path) in the application triggers the consumption of memory. You will most likely need help of the application programmer responsible for that application.

If the application has any built-in tracing functions, consider to enable it to log the operations being performed by the application.

If you can watch this application with SHOW PROC/CONT/ID=xxx, you could type 'V' which shows you the virtual address space layout of this process. If the leak is severe enough, you may be able to watch the address space expand. This would then enable you to look at the contents of those pages with SDA and maybe spot repeating data patterns.

Volker.