[an error occurred while processing this directive]

HP OpenVMS Systems Documentation

HP OpenVMS System Management Utilities Reference Manual

If you increase ERRORLOGBUFF_S2, you must either run AUTOGEN or manually increase the size of both the system dump file and the error log dump file.

ERRORLOGBUFFERS (A on Alpha and I64)

ERRORLOGBUFFERS specifies the number of S0 space error log buffers reserved for system error log entries. Each buffer is ERLBUFFERPAGES in length. If ERRORLOGBUFFERS is too low, messages might not be written to the error log file. If it is too high, the buffers can consume unnecessary physical pages.

EXECSTACKPAGES (D)

(Alpha and I64) EXECSTACKPAGES controls the number of pages allocated for each RMS exec stack.

EXPECTED_VOTES (A)

EXPECTED_VOTES specifies the maximum number of votes that can be present in a cluster at any given time. Set it to a value that is equal to the sum of the vote parameters of all cluster members, plus any votes that are contributed by the quorum disk. This value is used to automatically derive the number of votes that must be present for the cluster to function (quorum).

EXTRACPU (D)

EXTRACPU sets the time, in units of 10 ms, allotted to each of a process's exit handlers (for each access mode) after the process times out (that is, reaches its CPU time limit).

FAST_PATH

(Alpha and I64) FAST_PATH is a static system parameter that enables (1) or disables (0) the Fast Path performance features for all Fast Path-capable ports.

Starting in OpenVMS Version 7.2, FAST_PATH is enabled by default. In Versions 7.0 and 7.1, FAST_PATH was disabled by default.

For additional information, see FAST_PATH_PORTS.

FAST_PATH_PORTS

(Alpha and I64) FAST_PATH_PORTS is a static parameter that deactivates Fast Path for specific drivers.

FAST_PATH_PORTS is a 32-bit mask, with a bit assigned for each Fast Path port driver. The following table describes the bit values:

Bit Value	Description
1	Indicates that Fast Path is disabled for ports serviced by the corresponding driver.
0	Indicates that Fast Path is not disabled for ports serviced by the corresponding driver.

Beginning in OpenVMS Version 7.3-1, values of specific bit positions are those described in the following table:

Bit Position	Description
0	Controls Fast Path for PKQDRIVER (for parallel SCSI).
1	Controls Fast Path for FGEDRIVER (for Emulex LP7000, LP8000, LP9002, LP9802, LP10000 FibreChannel).
2	Controls Fast Path for PKADRIVER (for Adaptec AIC-78xx Ultra3 SCSI).
3	Controls Fast Path for PEDRIVER (for LAN).
4	Controls Fast Path for PKRDRIVER (for SMART Array 5300).
5	Controls Fast Path for PKMDRIVER, the LSI Logic LSI53C1030 SCSI port driver.
6	Controls Fast Path for PGQDRIVER, the Qlogic ISP23xx FibreChannel port driver.

Currently, the default setting for FAST_PATH_PORTS is 0, which means that Fast Path is enabled for all drivers that appear in the table.

In addition, note the following:

CI drivers are not controlled by FAST_PATH_PORTS. Fast Path for CI is enabled and disabled exclusively by the FAST_PATH system parameter.
FAST_PATH_PORTS is relevant only if the FAST_PATH system parameter is enabled (equal to 1). Setting FAST_PATH to zero has the same effect as setting all the bits in FAST_PATH_PORTS to 1.

For additional information, see FAST_PATH. For an explanation of how to set the bits, see the HP OpenVMS I/O User's Reference Manual.

FREEGOAL (A,D,M)

FREEGOAL establishes the number of pages that you want to reestablish on the free-page list following a system memory shortage. Memory shortages occur when the system drops below the minimum number of pages required on the free-page list (FREELIM). The value of FREEGOAL must always be greater than or equal to the value of FREELIM.

FREELIM (A,M)

FREELIM sets the minimum number of pages that must be on the free-page list.

The system writes pages from the modified-page list, swaps out working sets, or reduces the size of the working sets to maintain the minimum count.

While the larger free-page list generally means less page I/O, it also means less space for the balance set, which tends to result in more swap I/O. You can monitor the size of the free-page list, the amount of page, and the amount of swap with the MONITOR IO command of the Monitor utility.

GALAXY

(Alpha Galaxy platforms only) The GALAXY parameter sets memory sharing.

Specify one of the following:

Value	Description
0	The default. Do not participate in a memory sharing.
1	Participate in a memory sharing.

When you set GALAXY to 1 in a hard partition, OpenVMS instances will share memory between soft partitions within that hard partition. (You can run more than two soft partitions in a hard partition, and you might might not want to share memory among all of them.) Note that GALAXY specifies only if a node uses shared memory. You do not need to use the parameter to run multiple cooperative instances of OpenVMS; you do this by console setup of the configuration tree that you want.

GBLPAGES (A,D,F,G,M)

GBLPAGES sets the number of global page table entries allocated at bootstrap time. Each global section requires 1 global page table entry per section page, plus 2 entries, with the total rounded up to an even number.

Users with CMKRNL privilege can change this parameter on a running system. Increasing the value of this parameter allows the global page table to expand, on demand, up to the maximum size.

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 (INSTALL) and reduce the value of GBLPAGES accordingly. However, do not set the value of this parameter too low, because the page table entries use little permanently resident memory. 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.

GBLPAGFIL (A,D)

GBLPAGFIL defines the maximum number of systemwide pages allowed for global page-file sections (scratch global sections that can be used without being mapped to a file). These global page-file sections can be temporary, permanent, system, or group, and are allocated from the page file specified in the system process header at bootstrap time. When you allow pages for global page-file sections, you must increase the size of the page file accordingly. Users with CMKRNL privilege can change this parameter value on a running system.

Global page-file sections are created with the Create and Map Section system services ($CREATE_GPFILE, $CRMPSC, and $CRMPSC_GPFILE_64) without an explicit disk file. These sections are used for the RMS global buffers required for shared files. Users of shared files should note that global page-file sections cause both the global page table and the default system page file (PAGEFILE.SYS) to be used. If the value of GBLPAGFIL is too small, $CRMPSC issues an error message when you attempt to create global page-file sections.

You must have scratch global sections if you use RMS global buffers. Each file using global buffers requires, in the system page file, the file's bucket size multiplied by the number of global buffers for that file. If the file's bucket size varies, as with RMS indexed files, use the maximum bucket size. For shared sequential files, use the multiblock count of the first stream to perform the $CONNECT service in place of the file's bucket size.

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.

GB_CACHEALLMAX (D)

(Alpha and I64) If a file is connected to RMS with the RMS global buffer DEFAULT option enabled, the number of of blocks cached is either a maximum of the GB_CACHEALLMAX parameter or a percentage of the file, whichever results in a larger global count.

Note that although a maximum cache size of %x7FFFFFFF is supported for an indexed file, sequential and relative file organizations are restricted to a maximum cache size of 32767.

GB_DEFPERCENT (D)

(Alpha and I64) If a file is connected to RMS with the RMS global buffer DEFAULT option enabled, either a percentage (GB_DEFPERCENT) of the file is cached or up to GB_CACHEALLMAX blocks of it are cached, whichever results in a larger global buffer count. A percentage greater than 100 percent can be specified for GB_DEFPERCENT to provide growing room for a file in the global cache.

Note that although a maximum cache size of %x7FFFFFFF is supported for an indexed file, sequential and relative file organizations are restricted to a maximum cache size of 32767.

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.

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 ms (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.

IMGREG_PAGES

(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 can be caused by either an unusually large number of devices or a driver that requires a large amount of stack space.

IO_PRCPU_BITMAP

(Alpha and I64) This parameter is a bitmap representing up to 1024 CPUs. Each bit set in this bitmap indicates that the corresponding CPU is available for use as a Fast Path preferred CPU.

IO_PRCPU_BITMAP defaults to all bits set. (CPU 0 through CPU 1023 are all enabled for Fast Path port assignment.)

You might want to disable the primary CPU from serving as a preferred CPU by leaving its bit clear in IO_PRCPU_BITMAP, which reserves the primary CPU for non-Fast Path IO operations to use.

To change the value of IO_PRCPU_BITMAP in SYSBOOT or SYSGEN, specify a list of individual bits or contiguous groups of bits. For example:

   SYSGEN> SET IO_PRCPU_BITMAP 0,5,17-21

This command sets bits 0, 5, 17, 18, 19, 20, and 21 in the bitmap and clears all other bits.

Changing the value of IO_PRCPU_BITMAP causes the FASTPATH_SERVER process to run 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.

This parameter replaces IO_PREFER_CPU.

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 ¹	If set, this bit runs UNI 3.0 over all ATM adapters.
4 ¹	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 seconds, 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).

¹Auto-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, see 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 assigned to the CPU used by the Dedicated CPU Lock Manager.

For more information about use of the Dedicated CPU Lock Manager, see the OpenVMS Performance Management manual.

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.

Contents

Index