This means that you have too many processes running, or not enough process slots have been configured.
You've already been pointed to MAXPROCESSCNT, the other part of this is to look at what is present in the MODPARAMS.DAT file -- that's a common spot for tuning a system, and an equally common spot for mistuning a system -- and find out of it makes sense. I've seen all manner of parameter settings embedded there that are outdated (whether due to subsequent application or OpenVMS changes, or old information on system tuning), or should have been entered as MIN_, MAX_ or ADD_ parameter settings and that were erroneously inserted into MODPARAMS as absolute settings.
The contents of MODPARAMS can and do constrain what AUTOGEN can do to tune the settings, and what values it can establish.
In this case, I'd look at what's in MODPARAMS with a particular eye toward any process-level settings and any (absolute) setting of MAXPROCESSCNT, clean out any cruft, and where the values are still required I'd switch to MIN_, MAX_, or ADD_ where appropriate, and would AUTOGEN with FEEDBACK.
You can then begin an investigation of physical memory and process quotas. But the immediate NOSLOT limit can be lifted by using a MIN_MAXPROCESSCNT setting and an AUTOGEN (with FEEDBACK, and reboot) pass, or by reducing the numbers of currently active processes.
There is some risk to AUTOGEN, in that there are also folks that make system parameter settings changes directly, using SYSGEN or SYSMAN, and these changes can be lost over any subsequent AUTOGEN pass, and this AUTOGEN that can be required by a subsequent product installation, ECO, or OpenVMS upgrade. (Tweaking a parameter directly without also tweaking it in MODPARAMS is a common mistake. Most everybody makes it once.)
Ok, enough verbiage. Tweak MAXPROCESSCNT up via MODPARAMS and AUTOGEN FEEDBACK and reboot, or remove a few non-system, non-critical processes and continue running until you can schedule the tweak and the reboot.
Stephen Hoffman
www.HoffmanLabs.com
