 |
HP OpenVMS System Management Utilities Reference Manual
HP OpenVMS System Management Utilities Reference
Manual
The default value for this parameter is adequate for most systems.
However, if your site uses RMS global buffering to a significant
extent, you may need to raise the value of GBLPAGFIL. Use the /GLOBAL
qualifier of the Install utility to examine the number of pages
consumed by RMS global buffers. The global sections used by RMS for
global buffers have the prefix RMS$ followed by 8 hexadecimal digits.
Global buffers are enabled with the DCL command SET
FILE/GLOBAL_BUFFERS, which is described in the HP OpenVMS DCL Dictionary.
GBLSECTIONS (A,F,G,M)
GBLSECTIONS sets the number of global section descriptors allocated in
the system header at bootstrap time. Each global section requires one
descriptor. Each descriptor takes 32 bytes of permanently resident
memory.
The default value is sufficient for the images normally installed as
shared in the system startup command procedures. Once the system is
running and all global sections are created, you can examine the actual
requirements with the /GLOBAL qualifier of the Install utility and
reduce the value of GBLSECTIONS accordingly. However, the value of this
parameter should not be set too low. If you plan to install many user
images as shared, or if user programs are likely to create many global
sections, you must increase the value of this parameter.
If the value of GBLSECTIONS is too small, you receive a message from
the Install utility at system startup time or whenever you install
images manually. Note that too large a value for GBLSECTIONS wastes
physical memory.
GH_EXEC_CODE (A,F)
(Alpha and I64) GH_EXEC_CODE specifies the size in pages of the execlet
code granularity hint region.
GH_EXEC_DATA (A,F)
(Alpha and I64) GH_EXEC_DATA specifies the size in pages of the execlet
data granularity hint region.
GH_RES_CODE (A,F)
(Alpha and I64) GH_RES_CODE specifies the size in pages of the resident
image code granularity hint region.
GH_RES_DATA (A,F)
(Alpha and I64) GH_RES_DATA specifies the size in pages of the resident
image data granularity hint region.
If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image LDR$WRAPUP
releases all unused pages in the granularity hint region at the the end
of system startup. The unused pages of the resident image granularity
hint region are either reserved for future use, or given back to the
free memory list.
GH_RSRVPGCNT (F)
GH_RSRVPGCNT specifies the number of pages in the resident image code
granularity hint region that the Install utility can use after the
system has finished booting.
If bit 2 of the LOAD_SYS_IMAGES parameter is set, the image LDR$WRAPUP
releases all unused pages in the granularity hint region at the the end
of system startup. The unused pages of the resident image granularity
hint region are either reserved for future use, or given back to the
free memory list.
GH_RSRVPGCNT specifies the number of pages that LDR$WRAPUP attempts to
leave in the resident image code granularity hint region. If the
GH_RSRVPGCNT number of pages is larger than the unused pages in the
granularity hint region, the region is not expanded to accommodate the
number of pages requested.
GLX_INST_TMO
(Alpha Galaxy platforms only) GLX_INST_TMO is the time (in
milliseconds) that an instance in a Galaxy sharing set can fail to
increment its timeout value before the other sharing instances presume
that the instance failed and remove it from the sharing set.
The default is 20,000 milliseconds (20 seconds).
GLX_SHM_REG
For Alpha Galaxy systems, GLX_SHM_REG is the number of shared memory
region structures configured into the Galaxy Management Database
(GMDB). If set to 0, the default number of shared memory regions are
configured.
If the condition value SS$_INSF_SHM_REG is returned for the
$CRNMPSC_GDZRO_64 system service with the flag SEC$M_SHM_REG, the
Galaxy shared memory code has run out of internal SHM_REG data
structures. You need to increase the system parameter GLX_SHM_REG and
reboot all Galaxy instances with this larger parameter value.
GROWLIM (A,D,M)
GROWLIM sets the number of pages that the system must have on the
free-page list so that a process can add a page to its working set when
it is above quota. GROWLIM has no effect if the process is below its
working set quota. GROWLIM acts as a fast shutoff to the working set
extent mechanism based on the system's free memory.
IEEE_ADDRESS
IEEE_ADDRESS is reserved for HP use only.
IEEE_ADDRESSH
IEEE_ADDRESSH is reserved for HP use only.
IJOBLIM (D)
IJOBLIM sets the maximum number of interactive jobs that can be on the
system concurrently. You can control the maximum number of concurrent
interactive users on the system with the DCL command SET
LOGINS/INTERACTIVE.
IMGIOCNT
IMGIOCNT specifies the default number of pages of image I/O address
space to be allocated for the image activator if not specified at
program link time.
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
(Alpha and I64) IMGREG_PAGES is the number of pages to reserve in P1
space for images to be installed with shareable address data. If
IMGREG_PAGES is set to 0, no images are installed with shared address
data. The default is 10,000 pages.
For more information, see the INSTALL section in the HP OpenVMS System Management Utilities Reference Manual.
INTSTKPAGES (A,D,G,M)
(VAX only) INTSTKPAGES sets the size of the interrupt stack in pages.
Each page on the interrupt stack requires a page of permanently
resident memory.
Use the default value of 6 unless interrupt-stack-not-valid exceptions
occur. These may be caused by either an unusually large number of
devices or a driver that requires a large amount of stack space.
IO_PREFER_CPUS
(Alpha and I64) IO_PREFER_CPUS is a dynamic system parameter that
controls the set of CPUs that are available for use as Fast Path
preferred CPUs.
IO_PREFER_CPUS is a CPU bit mask specifying the CPUs that are allowed
to serve as preferred CPUs and that can thus be assigned a Fast Path
port. CPUs whose bit is set in the IO_PREFER_CPUS bit mask are enabled
for Fast Path port assignment. IO_PREFER_CPUS defaults to -1, which
specifies that all CPUs are allowed to be assigned Fast Path ports.
You might want to disable the primary CPU from serving as a preferred
CPU by clearing its bit in IO_PREFER_CPUS. This reserves the primary
CPU for non-Fast-Path IO operations to use.
Changing the value of IO_PREFER_CPUS causes the FASTPATH_SERVER process
to execute the automatic assignment algorithm that spreads Fast Path
ports evenly among the new set of usable CPUs.
For additional information, see FAST_PATH and FAST_PATH_PORTS.
IOTA
IOTA specifies the amount of time (in 10-millisecond units) to charge
to the current residence quantum for each voluntary wait. The correct
value approximates the cost of a disk I/O neglecting wait time.
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
IRPCOUNT (G,M)
IRPCOUNT sets the number of preallocated intermediate request packets.
Each packet requires 160 bytes of permanently resident memory. If
IRPCOUNT is too large, physical memory is wasted. If IRPCOUNT is too
small, the system increases its value automatically, as needed, to
permit proper performance. However, the system cannot increase IRPCOUNT
beyond the value of IRPCOUNTV.
Allowing this growth causes a physical memory penalty. If IRPCOUNT is
underconfigured, the penalty is 4 percent of physical memory from the
configured value to the actual value on the running system.
You can use the DCL command SHOW MEMORY/POOL/FULL to determine IRPCOUNT
usage.
IRPCOUNTV (G)
IRPCOUNTV establishes the upper limit to which IRPCOUNT can be
automatically increased by the system.
If this parameter is set too low, system performance can be adversely
affected because IRPCOUNTV cannot be used for nonpaged pool requests.
A physical memory penalty of 1 percent results for any unused growth
space (1 longword for every 3 unused intermediate request packets).
JBOBLIM
This parameter is no longer in use.
JOBCTLD
System managers do not usually alter JOBCTLD; this word of debug flags
is used in rolling upgrades of OpenVMS. If bit 0 is set, the queue
manager does not start. The default is 0.
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
KFILSTCNT
This parameter is no longer used on VAX systems and is not used on
Alpha and I64 systems.
KSTACKPAGES
(Alpha and I64) KSTACKPAGES controls the number of pages allocated for
process kernel stacks.
LAN_FLAGS (D)
(Alpha and I64) LAN_FLAGS is a bit mask used to enable features in the
local area networks port drivers and support code. The default value
for LAN_FLAGS is 0.
The bit definitions are as follows:
| Bit |
Description |
|
0
|
The default of zero indicates that ATM devices run in SONET mode. If
set to 1, this bit indicates ATM devices run in SDH mode.
|
|
1
|
If set, this bit enables a subset of the ATM trace and debug messages
in the LAN port drivers and support code.
|
|
2
|
If set, this bit enables all ATM trace and debug messages in the LAN
port drivers and support code.
|
|
3
1
|
If set, this bit runs UNI 3.0 over all ATM adapters.
|
|
4
1
|
If set, this bit runs UNI 3.1 over all ATM adapters.
|
|
5
|
If set, disables auto-negotiation over all Gigabit Ethernet Adapters.
|
|
6
|
If set, enables the use of jumbo frames over all Gigabit Ethernet
Adapters.
|
|
7
|
Reserved.
|
|
8
|
If set, disables the use of flow control over all LAN adapters that
support flow control.
|
|
9
|
Reserved.
|
|
10
|
Reserved.
|
|
11
|
If set, disables the logging of error log entries by LAN drivers.
|
|
12
|
If set, enables a fast timeout on transmit requests, usually between 1
and 1.2 seconds instead of 3 to 4 second, for most LAN drivers.
|
|
13
|
If set, transmits that are given to the LAN device and never completed
by the device (transmit timeout condition) are completed with error
status (SS$_ABORT) rather than success status (SS$_NORMAL).
|
1Auto-sensing of the ATM UNI version is enabled if both bit
3 and bit 4 are off (0).
LCKMGR_CPUID (D)
(Alpha and I64) LCKMGR_CPUID controls the CPU that the Dedicated CPU
Lock Manager runs on. This is the CPU that the LCKMGR_SERVER process
utilizes if you turn this feature on with the LCKMGR_MODE system
parameter.
If the specified CPU ID is either the primary CPU or a nonexistent CPU,
the LCKMGR_SERVER process utilizes the lowest nonprimary CPU. For more
information, refer to the LCKMGR_MODE system parameter.
LCKMGR_MODE (D)
(Alpha and I64) The LCKMGR_MODE parameter controls use of the Dedicated
CPU Lock Manager. Setting LCKMGR_MODE to a number greater than zero (0)
indicates the number of CPUs that must be active before the Dedicated
CPU Lock Manager is turned on.
The Dedicated CPU Lock Manager performs all locking operations on a
single dedicated CPU. This can improve system performance on large SMP
systems with high MP_Synch associated with the lock manager.
If the number of active CPUs is greater than or equal to LCKMGR_MODE, a
LCKMGR_SERVER process is created to service locking operations. This
process runs at a real-time priority of 63 and is always current.
In addition, if the number of active CPUs should ever be reduced below
the required threshold by either a STOP/CPU command or by a CPU
reassignment in a Galaxy configuration, the Dedicated CPU Lock Manager
automatically turns off within one second, and the LCKMGR_SERVER is
placed in a hibernate state. If the number of active CPUs is increased,
the LCKMGR_SERVER resumes servicing locking operations.
Specify one of the following:
- Zero (0) indicates that the Dedicated CPU Lock Manager is off (the
default).
- A number greater than zero (0) indicates the number of CPUs that
must be active before the Dedicated CPU Lock Manager will turn on.
When the Dedicated CPU Lock Manager is turned on, fast path devices are
not allowed on the CPU assigned to the CPU used by the Dedicated CPU
Lock Manager.
For more information about use of the Dedicated CPU Lock Manager, see
guide to OpenVMS Performance Management.
LGI_BRK_DISUSER (D)
LGI_BRK_DISUSER turns on the DISUSER flag in the UAF record when an
attempted break-in is detected, thus permanently locking out that
account. The parameter is off (0) by default. You should set the
parameter (1) only under extreme security watch conditions, because it
results in severely restricted user service.
LGI_BRK_LIM (D)
LGI_BRK_LIM specifies the number of failures that can occur at login
time before the system takes action against a possible break-in. The
count of failures applies independently to login attempts by each user
name, terminal, and node. Whenever login attempts from any of these
sources reach the break-in limit specified by LGI_BRK_LIM, the system
assumes it is under attack and initiates evasive action as specified by
the LGI_HID_TIM parameter.
The minimum value is 1. The default value is usually adequate.
LGI_BRK_TERM (D)
LGI_BRK_TERM causes the terminal name to be part of the association
string for the terminal mode of break-in detection. When LGI_BRK_TERM
is set to off (0), the processing considers the local or remote source
of the attempt, allowing break-in detection to correlate failed access
attempts across multiple terminal devices. When set to on (1),
LGI_BRK_TERM assumes that only local hard-wired or dedicated terminals
are in use and causes breakin detection processing to include the
specific local terminal name when examining and correlating break-in
attempts.
Ordinarily, LGI_BRK_TERM should be set to off (0) when physical
terminal names are created dynamically, such as when network protocols
like LAT and Telnet are in use.
LGI_BRK_TMO (D)
LGI_BRK_TMO specifies the length of the failure monitoring period. This
time increment is added to the suspect's expiration time each time a
login failure occurs. Once the expiration period passes, prior failures
are discarded, and the suspect is given a clean slate.
LGI_CALLOUTS (D)
LGI_CALLOUTS specifies the number of installation security policy
callout modules to be invoked at each login. LGI_CALLOUTS must be set
to 0 unless callout modules are present.
LGI_HID_TIM (D)
LGI_HID_TIM specifies the number of seconds that evasive action
persists following the detection of a possible break-in attempt. The
system refuses to allow any logins during this period, even if a valid
user name and password are specified.
LGI_PWD_TMO (D)
LGI_PWD_TMO specifies, in seconds, the period of time a user has to
enter the correct system password (if used). LGI_PWD_TMO also
establishes the timeout period for users to enter their personal
account passwords at login time. Also, when using the SET PASSWORD
command, LGI_PWD_TMO specifies the period of time the system waits for
a user to type in a new password, an old password, and the password
verification.
LGI_RETRY_LIM (D)
LGI_RETRY_LIM specifies the number of retry attempts allowed users
attempting to log in. If this parameter is greater than 0, and a
legitimate user fails to log in correctly because of typing errors, the
user does not automatically lose the carrier. Instead (provided that
LGI_RETRY_TMO has not elapsed), by pressing the Return key, the user is
prompted to enter the user name and password again. Once the specified
number of attempts has been made without success, the user loses the
carrier. As long as neither LGI_BRK_LIM nor LGI_BRK_TMO has elapsed,
the user can dial in again and reattempt login.
LGI_RETRY_TMO (D)
LGI_RETRY_TMO specifies the number of seconds allowed between login
retry attempts after each login failure. (Users can initiate login
retries by pressing the Return key.) This parameter is intended to be
used with the LGI_RETRY_LIM parameter; it allows dialup users a
reasonable amount of time and number of opportunities to attempt logins
before they lose the carrier.
LNMPHASHTBL (A on VAX,G)
LNMPHASHTBL sets the size of the process logical name hash table.
Logical names are hashed using a function of the name length and
contents. The LNMPHASHTBL parameter determines the number of entries
for process-private logical names. The recommended setting is the
average number of process-private logical names. Note that the hashed
values are rounded up to the nearest power of 2.
LNMSHASHTBL (A,F,G)
LNMSHASHTBL sets the size of the system logical name hash table.
Logical names are hashed using a function of the name length and
contents. The LNMSHASHTBL parameter determines the number of entries
for shareable logical names. These names include all names from the
system, group, and job logical name tables. The recommended setting
allows one to four logical names per hash table entry. The default
setting is usually adequate, unless your installation has a large
number of groups, or many jobs are active simultaneously. In that case,
an increase in the value of the next higher power of 2 might improve
logical name translation performance. Note that the hashed values are
rounded up to the nearest power of 2.
LOAD_PWD_POLICY
LOAD_PWD_POLICY controls whether the SET PASSWORD command attempts to
use site-specific password policy routines, which are contained in the
shareable image SYS$LIBRARY:VMS$PASSWORD_POLICY.EXE. The default is 0,
which indicates not to use policy routines.
LOAD_SYS_IMAGES (A on Alpha and I64)
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
LOAD_SYS_IMAGES controls the loading of system images described in the
system image data file, VMS$SYSTEM_IMAGES. This parameter is a bit mask.
On VAX systems, the following bit is defined:
| Bit |
Description |
|
0 (SGN$V_LOAD_SYS_IMAGES)
|
Enables loading alternate execlets specified in VMS$SYSTEM_IMAGES.DATA.
|
On Alpha and I64 systems, the following bits are defined:
| Bit |
Description |
|
0 (SGN$V_LOAD_SYS_IMAGES)
|
Enables loading alternate execlets specified in VMS$SYSTEM_IMAGES.DATA.
|
|
1 (SGN$V_EXEC_SLICING)
|
Enables executive slicing.
|
|
2 (SGN$V_RELEASE_PFNS)
|
Enables releasing unused portions of the Alpha and I64 huge pages.
|
These bits are on by default. Using conversational bootstrap exec
slicing can be disabled.
LOCKDIRWT (A)
LOCKDIRWT determines the portion of lock manager directory that this
system handles. The default value is usually adequate.
LOCKIDTBL (A,F,M)
LOCKIDTBL sets the initial number of entries in the system Lock ID
table and defines the amount by which the Lock ID table is extended
whenever the system runs out of locks. One entry must exist for each
lock in the system; each entry requires 4 bytes.
For simple timesharing systems, the default value is adequate. If your
application uses many locks, as in the case of heavy RMS file sharing
or a database management application, you should increase this
parameter. When you change the value of LOCKIDTBL, examine the value of
RESHASHTBL and change it if necessary.
The OpenVMS Lock Management facility is described in the HP OpenVMS Programming Concepts Manual.
You can monitor locks with the MONITOR LOCK command of the Monitor
utility.
LOCKIDTBL_MAX
LOCKIDTBL_MAX is obsolete beginning with OpenVMS Version 7.1.
LOCKRETRY
LOCKRETRY establishes the number of attempts made to lock a
multiprocessor data structure.
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
LONGWAIT (A on Alpha and I64,D,G,M)
LONGWAIT defines how much real time (in seconds) must elapse before the
swapper considers a process to be temporarily idle. This parameter is
applied to local event flag (LEF) and hibernate (HIB) waits to detect
such conditions as an inactive terminal or ACP.
MAXBOBMEM (D)
(Alpha and I64) MAXBOBMEM defines the maximum amount of physical
memory, measured in pagelets, that can be associated with a single
buffer object created by a process in user mode. The default value of 0
means there is no system-imposed limit on the size of a buffer object.
Other MAXBOB* parameters are obsolete beginning with OpenVMS Version
7.3.
MAXBUF (D)
MAXBUF sets the maximum allowable size for any single buffered I/O
packet. Buffered I/O packets are allocated from the permanently
resident nonpaged dynamic pool. The terminal, mailbox, and printer
device drivers are examples of device drivers that perform buffered I/O.
The number of bytes specified in the I/O request plus the size of a
driver-dependent and function-dependent header area determine the
required buffered I/O packet size. The size of the header area is a
minimum of 16 bytes; there is no absolute upper limit. However, this
header area is usually a few hundred bytes in size.
On OpenVMS VAX systems beginning with Version 7.1, the default value is
4112. The default value on Alpha and I64 systems continues to be 8192.
The maximum value of MAXBUF is 64000 bytes.
MAXCLASSPRI (D)
If class scheduling is enabled, MAXCLASSPRI sets the maximum range in
the priority range of class-scheduled processes.
This special parameter is used by HP and is subject to change. Do not
change this parameter unless HP recommends that you do so.
MAXPROCESSCNT (A,F,G,M)
MAXPROCESSCNT sets the number of process entry slots allocated at
bootstrap time. One slot is required for each concurrent process on the
system. Each slot requires 6 bytes of permanently resident memory.
The default value is normally configured to allow you to create the
desired number of processes. If the following message appears, you need
to increase the value of MAXPROCESSCNT:
%SYSTEM-F-NOSLOT, No PCB to create process
|
On Alpha and I64 systems beginning with Version 8.1, the default value
is 32,767.
MAXQUEPRI (D)
MAXQUEPRI determines the highest scheduling priority that can be
assigned to jobs entered in batch and output (printer, server, and
terminal) queues without the submitter process having OPER or ALTPRI
privilege. The value of this parameter can range from 0 to 255; the
default is 100. The value of MAXQUEPRI should be greater than or equal
to DEFQUEPRI.
Note
MAXQUEPRI refers to relative queue scheduling priority, not to the
execution priority of the job.
|
MAXSYSGROUP (D)
MAXSYSGROUP sets the highest value that a group number can have and
still be classified as a system UIC group number. Note that the
specification is not in octal unless preceded by the %O radix
indicator. This parameter is normally left at 8 (10 octal).
MC_SERVICES_P0 (D)
(Alpha only) MC_SERVICES_P0 controls whether other MEMORY CHANNEL nodes
in the cluster continue to run if this node bugchecks or shuts down.
A value of 1 causes other nodes in the MEMORY CHANNEL cluster to crash
with bugcheck code MC_FORCED_CRASH if this node bugchecks or shuts down.
The default value is 0. A setting of 1 is intended only for debugging
purposes; the parameter should otherwise be left at its default value.
MC_SERVICES_P1 (D)
(Alpha only) This special parameter is reserved for HP use. Its value
must be the same on all nodes connected by MEMORY CHANNEL.
MC_SERVICES_P2
(Alpha only) MC_SERVICES_P2 specifies whether to load the PMDRIVER
(PMA0) MEMORY CHANNEL cluster port driver.
PMDRIVER is a driver that serves as the MEMORY CHANNEL cluster port
driver. It works together with MCDRIVER (the MEMORY CHANNEL device
driver and driver interface) to provide MEMORY CHANNEL clustering. If
PMDRIVER is not loaded, cluster connections are not made over the
MEMORY CHANNEL interconnect.
The default value is 1, which causes PMDRIVER to be loaded when you
boot the system. When you run CLUSTER_CONFIG.COM and select the MEMORY
CHANNEL option, PMDRIVER is loaded automatically when you reboot the
system.
HP recommends that this value not be changed. This parameter value must
be the same on all nodes connected by MEMORY CHANNEL.
MC_SERVICES_P3 (D)
(Alpha only) MC_SERVICES_P3 specifies the maximum number of tags
supported. The maximum value is 2048, and the minimum value is 100.
The default value is 800. HP recommends that this value not be changed.
This parameter value must be the same on all nodes connected by MEMORY
CHANNEL.
MC_SERVICES_P4
(Alpha only) MC_SERVICES_P4 specifies the maximum number of regions
supported. The maximum value is 4096, and the minimum value is 100.
The default value is 200. HP recommends that this value not be changed.
This parameter value must be the same on all nodes connected by MEMORY
CHANNEL.
MC_SERVICES_P5 (D)
(Alpha only) MC_SERVICES_P5 is reserved for HP use only and must remain
at the default value of 8000000. This value must be the same on all
nodes connected by MEMORY CHANNEL.
MC_SERVICES_P6
(Alpha only) MC_SERVICES_P6 specifies MEMORY CHANNEL message size, the
body of an entry in a free queue, or a work queue. The maximum value is
65536, and the minimum value is 544.
The default value is 992. This value is suitable in all cases except
for systems with highly constrained memory. For such systems, you can
reduce the memory consumptions of MEMORY CHANNEL by slightly reducing
the default value of 992. The value of MC_SERVICES_P6 must always be
equal to or greater than the result of the following calculations:
- Select the larger of SCS_MAXMSG and SCS_MAXDG.
- Round that value up to the next quadword.
