OpenVMS System Management Utilities Reference Manual

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 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)

On Alpha systems, GH_EXEC_CODE specifies the size in pages of the execlet code granularity hint region.

GH_EXEC_DATA (A,F)

On Alpha systems, GH_EXEC_DATA specifies the size in pages of the execlet data granularity hint region.

GH_RES_CODE (A,F)

On Alpha systems, GH_RES_CODE specifies the size in pages of the resident image code granularity hint region.

GH_RES_DATA (A,F)

On Alpha systems, GH_RES_DATA specifies the size in pages of the resident image data granularity hint region.

GH_RSRVPGCNT (F)

On Alpha systems, GH_RSRVPGCNT specifies the number of pages in the resident image 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 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.

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 to Digital.

IEEE_ADDRESSH

IEEE_ADDRESSH is reserved to Digital.

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.

IMGREG_PAGES

On Alpha systems, 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 OpenVMS System Manager's Manual.

INTSTKPAGES (A,D,G,M)

On VAX systems, 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

On Alpha systems, IO_PREFER_CPUS excludes processors from being used as preferred CPUs for Fast Path I/O. IO_PREFER_CPUS is a 32-bit mask; if the value of a bit in the mask is 1, the processor with the corresponding CPU ID is available to be used as a preferred CPU.

The default value of IO_PREFER_CPUS, - 1, allows all available CPUs to become Preferred CPUs. The parameter is used only if Fast Path is enabled. See the FAST_PATH system parameter.

KSTACKPAGES

On Alpha systems, KSTACKPAGES controls the number of pages allocated for process kernel stacks.

LAMAPREGS (G)

On VAX systems, LAMAPREGS sets the number of UNIBUS map registers allocated to an LPA11 driver when the driver is loaded, and limits the registers for the driver to that number. A value of 0 permits dynamic allocation of an unlimited number of registers.

LAN_FLAGS (D)

On Alpha systems, LAN_FLAGS is a bitmask used to enable features in the local area networks port drivers and support code:

Bit	Description
Bit 0	The default of zero indicates that ATM devices will run in SONET mode. If set to 1, this bit indicates ATM devices will run in SDH mode.
Bit 1	If set, this bit enables a subset of the trace and debug messages in the LAN port drivers and support code.
Bit 2	If set, this bit enables all trace and debug messages in the LAN port drivers and support code.

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 will take 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 will initiate 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 off (0), association is done on user name only. LGI_BRK_TERM is set by default (1). It should be cleared if physical terminal names are created dynamically (that is, if LAT is installed) and effective break-in detection is desired.

LGI_BRK_TMO (D)

LGI_BRK_TMO specifies the number of seconds that a user, terminal, or node is permitted to attempt a login before the system assumes that a break-in attempt is occurring and takes evasive action. Note that LGI_BRK_LIM may be exceeded before the LGI_BRK_TMO timeout and vice versa. The evasive action is specified by the LGI_HID_TIM parameter.

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 will persist 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. In addition, 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 for 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 will 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 for use in conjunction with the LGI_RETRY_LIM parameter and gives 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 for 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.

LOCKDIRWT (A)

LOCKDIRWT determines the portion of lock manager directory that will be handled by this system. 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 OpenVMS Programming Concepts Manual. You can monitor locks with the MONITOR LOCK command of the Monitor utility.

LONGWAIT (A on Alpha,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)

On Alpha systems, MAXBOBMEM determines the maximum number of pagelets that can be made into buffer objects systemwide.

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.

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 will have to increase the value of MAXPROCESSCNT:

%SYSTEM-F-NOSLOT,  No PCB to create process

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 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

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 crashes other nodes in the MEMORY CHANNEL cluster if this node bugchecks or shuts down. This setting could be used for debugging SPI applications.

The default value is 0.

MC_SERVICES_P1 (D)

This parameter is reserved by Digital. Its value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P2

MC_SERVICES_P2 specifies whether to load the PMDRIVER (PMA0) cluster driver. A value of 1 loads PMDRIVER and a value of 0 does not load PMDRIVER.

The default value is 1.

This parameter value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P3 (D)

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.

This parameter value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P4

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.

This parameter value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P5 (D)

This parameter is reserved by Digital, 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

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 512. A typical recommended value is SCS_MAXMSG rounded up to a quadword.

The default value is 992.

This parameter value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P7 (D)

MC_SERVICES_P7 specifies whether to suppress or display messages about cluster activities on this node. A value of 0 indicates nonverbose mode, which means that no informational messages will be displayed on the console or in the log. A value of 1 indicates verbose mode---informational messages from both MCDRIVER and PMDRIVER on the console and in the log. A value of 2 produces the same output as a value of 1, as well as PMDRIVER stalling and recovery messages.

If you suspect memory channel throughput problems, set this parameter to a value of 2 so that stalling messages will be displayed; then increase the value of P9 by increments of 25 until stalling messages stop or become infrequent. Each increment consumes more physical memory.

The maximum value is -1 and the minimum value is 0.

The default value is 0.

MC_SERVICES_P8

This parameter is reserved by Digital, and must remain at the default value of 0.

The value must be the same on all nodes connected by MEMORY CHANNEL.

MC_SERVICES_P9

MC_SERVICES_P9 specifies the number of initial entries in a single channel's free queue. The maximum value is 2048 and the minimum value is 10.

The default value is 150.

This parameter value must be the same on all nodes connected by MEMORY CHANNEL.

MINWSCNT (A)

The value specified by MINWSCNT is added to the size of the process header to establish the minimum working set size.

On VAX systems, MINWSCNT sets the minimum number of fluid pages (pages not locked in the working set) required for the execution of a process.

The value of MINWSCNT must provide sufficient space to execute any VAX instruction. Theoretically, the longest instruction requires 52 pages; however, all code can run with 20 fluid pages. An insufficient value may inhibit system performance or even put a process into an infinite loop on some instructions.

On Alpha systems, MINWSCNT sets the minimum number of pages required for the execution of a process. The default value is 20; the minimum value is 10.

MMG_CTLFLAGS (A,D)

MMG_CTLFLAGS is a bit mask used to enable and disable proactive memory reclamation mechanisms. The following values are defined:

Bit	Description
0	Reclamation enabled by trimming from periodically executing, but otherwise idle processes. This occurs when the size of the free list drops below two times FREEGOAL.
1	Reclamation enabled by outswapping processes that have been idle for longer than LONGWAIT seconds. This occurs when the size of the free list drops below FREELIM.
2-7	Reserved for future use.

MPW_HILIMIT (A,G)

MPW_HILIMIT sets an upper limit for the modified-page list. When the list accumulates the number of pages specified by this limit, writing of the list begins. The pages that are written are then transferred to the free-page list.

If MPW_HILIMIT is too low, excessive page faulting can occur from the page file. If it is too high, too many physical pages can be consumed by the modified-page list.

If you increase MPW_HILIMIT, you might also need to increase MPW_WAITLIMIT. Note that if MPW_WAITLIMIT is less than MPW_HILIMIT, a system deadlock will occur. The values for the two parameters are normally equal.

MPW_IOLIMIT (A on Alpha)

MPW_IOLIMIT specifies the number of outstanding I/Os to the modified-page writer.

MPW_LOLIMIT (A,G)

MPW_LOLIMIT sets a lower limit for the modified-page list. When writing of the list causes the number of pages on the list to drop to or below this limit, writing stops.

MPW_LOLIMIT ensures that a certain number of pages are available on the modified-page list for page faults. If the number is too small, the caching effectiveness of the modified-page list is reduced. If it is too high, less memory is available for processes, so that swap (and page) may increase.

MPW_LOWAITLIMIT (A,D)

MPW_LOWAITLIMIT specifies the threshold at which processes in the miscellaneous wait state MPWBUSY are allowed to resume. MPW_LOWAITLIMIT increases system performance for fast processors with large memories by reducing the amount of time processes spend in the MPWBUSY wait state.

MPW_THRESH (A on Alpha,D)

MPW_THRESH sets a lower bound of pages that must exist on the modified-page list before the swapper writes this list to acquire free pages. If this requirement is met, the swapper tries to write the modified-page list rather than taking pages away from or swapping out a process.

MPW_WAITLIMIT (A,D)

MPW_WAITLIMIT sets the number of pages on the modified-page list that will cause a process to wait until the next time the modified-page writer writes the modified list. This parameter limits the rate at which any single process can produce modified pages. If this value is less than MPW_HILIMIT, a system deadlock occurs. The value for this parameter is normally equal to MPW_HILIMIT.

MPW_WRTCLUSTER (A,G)

MPW_WRTCLUSTER sets the number of pages to be written during one I/O operation from the modified-page list to the page file or a section file. The actual size of the cluster may be limited by the number of pages available for the I/O operation. This parameter can range in value from 16 to 120, in multiples of 8. Each page in the cluster requires 6 bytes of permanently resident memory.

If MPW_WRTCLUSTER is too small, it takes many I/O operations to empty the modified-page list. If MPW_WRTCLUSTER is too large for the speed of the disk that holds the page file, other I/O operations are held up for the modified-page list write.

On VAX systems, the MPW_WRTCLUSTER default value and maximum value is 120 512-byte pages; its minimum value is 16 512-byte pages.

On Alpha systems, the MPW_WRTCLUSTER default value is 64 8192-byte pages; its maximum value is 512 8192-byte pages; and its minimum value is 16 8192-byte pages.

MSCP_BUFFER (A,F)

This buffer area is the space used by the server to transfer data between client systems and local disks.

On VAX systems, MSCP_BUFFER specifies the number of pages to be allocated to the MSCP server's local buffer area.

On Alpha systems, MSCP_BUFFER specifies the number of pagelets to be allocated to the MSCP server's local buffer area.

MSCP_CMD_TMO (D)

MSCP_CMD_TMO is the time in seconds that the OpenVMS MSCP server uses to detect MSCP command timeouts. The default value for MSCP_CMD_TMO is 0, which is normally adequate. A nonzero setting increases the amount of time before an MSCP command times out.

If command timeout errors are being logged on client nodes, setting this parameter to a nonzero value on OpenVMS servers reduces the number of errors logged. Increasing the value of this parameter reduces the number of client MSCP command timeouts and increases the time it takes to detect faulty devices.

If you need to decrease the number of command timeout errors, Digital recommends you set an initial value of 60. If timeout errors continue to be logged, you can increase this value in increments of 20 seconds.

MSCP_CREDITS

MSCP_CREDITS specifies the number of outstanding I/O requests that can be active from one client system.

MSCP_LOAD (A)

MSCP_LOAD controls the loading of the MSCP server during a system boot. Specify one of the following values:

Value	Description
0	Do not load the MSCP server. This is the default value.
1	Load the MSCP server and serve disks as specified by the MSCP_SERVE_ALL parameter.

MSCP_SERVE_ALL

MSCP_SERVE_ALL controls the serving of disks during a system boot. Specify one of the following values:

Value	Description
0	Do not serve any disks. This is the default.
1	Serve all available disks.
2	Serve only locally attached (non HSC) disks.

If the MSCP_LOAD system parameter is 0, MSCP_SERVE_ALL is ignored.

MULTIPROCESSING

MULTIPROCESSING controls loading of the system synchronization image.

On VAX systems, specify one of the following values:

Value Description

0 Load the uniprocessing synchronization image SYSTEM_SYNCHRONIZATION_UNI.EXE.

1 Load the full-checking multiprocessing synchronization image SYSTEM_SYNCHRONIZATION.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. Otherwise, load uniprocessing synchronization image.

2 Always load the full-checking version SYSTEM_SYNCHRONIZATION.EXE, regardless of system configuration or CPU availability.

3 Load the optimized streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_SPC.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. Otherwise, load uniprocessing synchronization image. The default value is 3.

4 Always load the streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system configuration or CPU availability.

Value	Description
0	Load the uniprocessing synchronization image SYSTEM_SYNCHRONIZATION_UNI.EXE.
1	Load the full-checking multiprocessing synchronization image SYSTEM_SYNCHRONIZATION.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. Otherwise, load uniprocessing synchronization image.
2	Always load the full-checking version SYSTEM_SYNCHRONIZATION.EXE, regardless of system configuration or CPU availability.
3	Load the optimized streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_SPC.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. Otherwise, load uniprocessing synchronization image. The default value is 3.
4	Always load the streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system configuration or CPU availability.

On Alpha systems, specify one of the following values:

Value Description

0 Load uniprocessing synchronization image SYSTEM_SYNCHRONIZATION_UNI.EXE.

1 Load full-checking multiprocessing synchronization image SYSTEM_SYNCHRONIZATION.EXE, if CPU type is capable of SMP and two or more CPUs are present on the system.

2 Always load the full-checking multiprocessing synchronization image, SYSTEM_SYNCHRONIZATION.EXE, regardless of system configuration or CPU availability.

3 Load streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_MIN.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. The default value is 3.

4 Always load streamlined multiprocessing synchronization image SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system configuration or CPU availability.

Value	Description
0	Load uniprocessing synchronization image SYSTEM_SYNCHRONIZATION_UNI.EXE.
1	Load full-checking multiprocessing synchronization image SYSTEM_SYNCHRONIZATION.EXE, if CPU type is capable of SMP and two or more CPUs are present on the system.
2	Always load the full-checking multiprocessing synchronization image, SYSTEM_SYNCHRONIZATION.EXE, regardless of system configuration or CPU availability.
3	Load streamlined multiprocessing image SYSTEM_SYNCHRONIZATION_MIN.EXE if CPU type is capable of SMP and two or more CPUs are present on the system. The default value is 3.
4	Always load streamlined multiprocessing synchronization image SYSTEM_SYNCHRONIZATION_MIN.EXE, regardless of system configuration or CPU availability.

MULTITHREAD (A)

On Alpha systems, MULTITHREAD controls the availability of kernel threads functions. Specify one of the following values:

Value	Description
0	Both Thread Manager upcalls and the creation of multiple kernel threads are disabled.
1	Thread Manager upcalls are enabled; the creation of multiple kernel threads is disabled.
2-16	Both Thread Manager upcalls and the creation of multiple kernel threads are enabled. The number specified represents the maximum number of kernel threads that can be created for a single process.

MVTIMEOUT (A on Alpha,D)

MVTIMEOUT is the time in seconds that a mount verification attempt continues on a given disk volume. If the mount verification does not recover the volume within that time, the I/O operations outstanding to the volume terminate abnormally.

NET_CALLOUTS (D)

NET_CALLOUTS is normally set to 0. A value of 255 indicates that no attempt is to be made to assign a new proxy connection to an active server, but that a new process must be started in order to be certain to invoke installation security policy callout modules in LOGINOUT.EXE. Values 1 through 254 are reserved for future use.

NISCS_CONV_BOOT

NISCS_CONV_BOOT controls whether a conversational boot is permitted during a remote system boot. The default of 0 specifies that conversational boots are not permitted.

NISCS_LAN_OVRHD

NISCS_LAN_OVRHD defines the number of bytes that are reserved by NISCA for data reformatting or encapsulation in a local area network (LAN) packet. The reserved space in the packet allows devices, such as the DESNC, to perform their operations. Currently, this value must be nonzero only when NISCA is run in an environment that uses the DESNC for LAN data encryption. Refer to the description of the NISCS_MAX_PKTSZ parameter for interactions.

  6048P066.HTM
  OSSG Documentation
  26-NOV-1996 12:44:03.70

Legal