 |
The Question is:
What is the cause of a NOSLOT error when a SHOW SYSTEM only reflects 61
processes yet maxproccesscnt is 110???
This started after I raised the SPTE's on this VAX and besides being unable to
create new processes, other processes that are still alive hang.
I could really benefit from a prompt answer on this.
Regards,
Barry
The Answer is :
The OpenVMS Wizard will assume you have used AUTOGEN and MODPARAMS.DAT
to make the specified change to the system parameters.
The OpenVMS Wizard expects you have probably encoutered the limit on
the total size of VAX system space.
The process data structures, the VAX process page tables, as well as
paged and non-paged pool and the operating system code must all fit
into the available VAX system space. VAX systems with large virtual
address space, with large pool, with large numbers of processes, or
often with a combination of these can exhaust the available VAX address
space.
You could try to increase the number of balance set slots (BALSETCNT)
available, reduce the virtual page limits (VIRTUALPAGECNT), reduce the
number of processes, or enable and use the virtual balance set slots
(VBSS*) mechanism.
Other considerations include reducing the loaded code and drivers, and
reducing the number of reserved page table entries. Also review the
system hardware configuration for the availability of free physical
memory.
OpenVMS Alpha moves various large data structures into 64-bit space,
and moves the page tables into page table space.
|
|
|
|
|
