uVAX 3900 out to lunch after inactivity

5 May 2013

...
   With VAX/VMS,
having lots of physical memory is neither necessary nor
 sufficient.  More important is how the virtual memory system is configured.
 Perhaps you are low on pagefile space or non-paged pool or something like
 that? 
 I was musing on this while reviewing the install manual and it does
 mention that at least 24 MB physical memory is necessary for TCP/IP
 5.1.  I don't know how hard and fast that is, but it's possible that
 the changes I made to the pool allocation per the manual have
 destabilized the system.  Since I don't have much running on there,
 I've reinstalled from scratch to see if I have the same problem with
 no TCP/IP installed/running.

I would worry more about DECWindows needing large amounts of memory rather
than TCP/IP but having said that, I've always used Multinet rather than TCP/IP
services so I don't know a lot about it.

I suspect the manual is saying that a typical workload on a more capable VAX
than an MVII would need 24 MB for good performance.  I think you should be able
to get by with rather less memory than that, particularly if you don't have a
graphics card.

It should not be necessary to reinstall to see the effect of not running TCP/IP
services.  Just comment out the command to start it
(probably in sys$manager:systartup_vms.com) and reboot.

Regards,
Peter Coghlan.

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

uVAX 3900 out to lunch after inactivity