RSVNONR
RSVNONR=nnnnnn - This parameter specifies the number of entries in the address
space vector table that are to be reserved for replacing entries that
are marked non-reusable. RSVNONR entries are used to keep the
number of entries specified by MAXUSER and RSVSTRT at their specified
levels. If RSVNONR entries are not available, an address space that
is marked non-reusable will result in the total number of available
address spaces being depleted.
A non-reusable address space is one where a job that ended had been running in a cross memory environment. When such a job ends, the system ends the address space and marks its associated ASVT entry non-reusable (unavailable) until all of the address spaces the job had cross memory binds with have ended.
The value you choose for RSVNONR depends on what subsystems you are running, how often you restart the subsystems, and how often you IPL. The more subsystems you have, the higher the RSVNONR value must be. Frequent restarts of subsystems also require a higher RSVNONR value. Conversely, the more often you IPL, the lower the RSVNONR value needs to be. The ASIDs are reset each time you IPL. If you IPL frequently you are less likely to exhaust the available ASIDs, and you need not reserve as many entries in the address space vector table. For example, if you IPL once every three months, you need a RSVNONR value that is three times higher than if you IPL every month.
However, too large a buffer can cause the system to allocate more system resources than are needed during a given IPL. The excessive allocation of system resources because of incorporating too large a buffer can lead to potential problems such as the following examples:- An aggressively large RSVNONR value could cause a wait state 040 to occur at IPL time. Wait state 040 means the system abended a task during nucleus initialization program (NIP) processing.
- An aggressively large MAXUSER, RSVSTRT, and RSVNONR can cause the system to allocate an excessive amount of storage, which can potentially lead to a wait state 204 reason 008 at IPL time. (Wait state 204 with reason 008: An error occurred during allocation initialization; the system could not obtain storage for device information.)
If started tasks or batch jobs that create non-reusable ASIDs end enough times, they will exhaust all available ASIDs and an IPL will be required. When loading the initial program is not an acceptable option, determine which programs caused the problems and fix them. For methods that prevent running out of ASIDs, see .
Value range: 0-32767. Note that the sum of the values specified for the RSVNONR, RSVSTRT, and MAXUSER system parameters cannot exceed 32767.Default: 100Associated parmlib member: None