[fa.info-vax] How can you run out of virtual memory?

info-vax@ucbvax.ARPA (03/18/85)

From: Jeff Cameron <jcameron%NRTC@USC-ECL.ARPA>

	Every account on a VAX/VMS system has a quota called PGFLQUOTA.
	it specifies the maximum number of virtual pages an account (or
	process) can have.

	There is also a non-dynamic sysgen parameter called VIRTUALPAGECNT,
	that specifies the maximum number of virtual pages any process on the
	system may have.

	On the last page of your LINK map file, there is a description of
	the number of virtual pages needed to link. See your system
	administrator to have your PGFLQUOTA raised to accomodate your needs.
	The sysgen parameter VIRTUALPAGECNT must be as large as the greatest
	PGFLQUOTA of all the accounts.

	Changing VIRTUALPAGECNT requires a re-boot, to place into operation.

info-vax@ucbvax.ARPA (03/19/85)

From: Gail Rubin <grubin@bbn-spca>

I suspect the message of Monday March 18th about PGFLQUOTA and
VIRTUALPAGECNT was sent because of my original query about running out of
virtual memory on a LINK of a shareable image.  Unforunately, my
department's connection to the ArpaNet was down for 5 days and I didn't see
any messages on the topic other than this one. What did the original
message with a subject line of "How can you run out of virtual memory?"
say? (If it was NOT a result of my question, please let me know.)

In any case, our VIRTUALPAGECNT and PGFLQUOTA are already quite large.
Our VIRTUALPAGECNT is over 15000 and my page file quota is 10000. The
map said it was using 3705 pages; well below either of these numbers.
I also have sufficient privilege to make any necessary changes to our quotas
and sysgen parameters. It isn't that simple; anyone have any other
parameters for me to check? I knew of these 2 and had checked them before I
asked my original question.

Thanks for any help or replies.
-- Gail Rubin (grubin@bbn-spca or @bbn-unix)