Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!oliveb!pyramid!batcomputer!tedcrane
From: tedcrane@batcomputer.UUCP
Newsgroups: comp.os.vms
Subject: Re: Stopped Processes on the GPX - (nf)
Message-ID: <1179@batcomputer.tn.cornell.edu>
Date: Thu, 28-May-87 13:31:15 EDT
Article-I.D.: batcompu.1179
Posted: Thu May 28 13:31:15 1987
Date-Received: Sat, 30-May-87 05:33:25 EDT
References: <137900001@exunido.UUCP>
Reply-To: tedcrane@tcgould.tn.cornell.edu.UUCP (Ted Crane)
Organization: Program of Computer Graphics, Cornell University
Lines: 38

In article <137900001@exunido.UUCP> dewal@exunido.UUCP writes:
>We have got a MicroVax II (GPX). Several times it occured that proces-
>ses started on the graphic display stopped. At this point we were not
>able to use the graphic screen anymore. Trying to kill the processes lo-
>cated on the graphic screen failed. We had to reboot the system to use the
>graphic screen. 

You don't say what version of VWS software you are using, however, there
is a very general comment that applies to VWS up to V3.0 (and possibly 3.1).

Every window has virtual memory associated with it.  This memory is also
allocated physical memory.  There are several SYSGEN-type parameters that
must be increased to provide physical memory for this purpose.  The VWS
installation procedure makes a guess at how much memory you will use and
puts parameters like:
	NPAGEDYN
	PAGEDYN
	CTLPAGES
into a file called SYS$SYSTEM:VMSPARAMS.DAT.  If you look at that file,
look for lines starting with QDSS (the GPX device).  You'll see 'em.

The problem is, these parameters are not big enough!  Between VMS, VWS, and
your usage of the machine, you run out of dynamic memory.

One fix is to edit SYS$SYSTEM:MODPARAMS.DAT (not VMSPARAMS!) and put in lines
of the form:
	ADD_NPAGEDYN = xxx
You can determine "xxx" by doing a SHOW MEMORY/POOL/FULL while the system
is running (preferably when it is close to failure, with lots of windows).
SHOW MEM will show that one of the various pools is getting empty.  Increase
its size.

Another fix (and the two fixes should be applied concurrently) is to look
in SYS$MANAGER:STARTVWS.COM.  Note the parameters SYSTEM_POOL_SIZE and
P1_POOL_SIZE.  These are used to define logical names used by the window
manager.  If these logicals are defined BEFORE you run STARTVWS, the
manager will allocate more extra space.  Increase these values by defining
logicals appropriately in SYS$MANAGER:SYSTARTUP.COM before it calls STARTVWS.