HP OpenVMS Systems

AUTOGEN and altering the working set (WSMAX) size?

» close window

The Question is:

 
I have two AlphaServer 1200 systems and one is giving me autogen problems.
The first system I put up (the one with the problem) I had installed DECnet
OSI and had to backtrack to DECnet Phase IV. The second system which came
several weeks later was able t
o have all the startup files copied along with MODPARAMS.DAT (changing the
node name and id number).
 
I need WSMAX >= 12,000 for DECwindows along with other stuff (Oracle,..) on
the second system autogen uses the MIN_WSMAX and sets it to >65,000 but on
the first system is refuses to make it anything but 1024.
 
Short of copying the system disk from the second system I have copied lots
of PAR and DAT files and have used SYSGEN to force values. I let the system
run for days as I use it heavily and still autogen won't raise WSMAX.
 
Any clues as to what to look at?
 
 

The Answer is :

 
  Please contact the customer support center -- copies of your MODPARAMS
  file and the resulting reports from the AUTOGEN passes, as well as
  specific information on the system hardware configuration for these
  AlphaServer 1200 systems, and possibly additional information, will
  be required in order to work to resolve this.
 
  As a test, clean out the cruft in MODPARAMS that tends to build up
  over time -- beware of any local performance tuning steps, as these
  can cripple AUTOGEN's ability to alter parameter settings -- sticking
  to those MIN_, MAX_, or ADD_ settings that you know you need.  SYSBOOT
  USE DEFAULT during a conversational bootstrap to switch to default
  parameters, and AUTOGEN from GETDATA to REBOOT with NOFEEDBACK to
  reset the parameters.
 

  

     

     
answer written or last revised on ( 19-NOV-1998 )
     
» close window