SET

Purpose

Use at the server console to view and configure operating system parameters.

NOTE: You can also use SERVMAN or MONITOR to configure and set operating system parameters.

The default SET parameters give maximum performance for most systems. Network supervisors should seldom need to change parameters.

Syntax

SET [parameter] = [value]

Entering Parameters

You can use most SET parameters at the console prompt. The system is immediately configured to that setting. Any setting in the AUTOEXEC.NCF file is overridden until the server is rebooted.
You can save SET commands you execute at the console prompt in the AUTOEXEC.NCF file. When a parameter is saved, the server configures itself to the parameter each time the server is booted.
If the parameter isn't saved in the file, the system returns to the default setting for the parameter when the server is booted. Some commands can be saved in the STARTUP.NCF file.

Edit the AUTOEXEC.NCF or the STARTUP.NCF file with INSTALL. If you use SERVMAN to change SET parameters, you are prompted to update .NCF files before exiting the utility.

Parameters that Control the Allocation of Services

Some SET parameters control how the system dynamically allocates services. Three types of parameters interact to control the allocation of a service:

Maximum limits control how many resources the operating system can allocate for a particular service.
Minimum limits allow the operating system to allocate a minimum number of resources as soon as a request is received.
Low minimum limits slow the growth of a particular service. High minimum limits allow rapid growth.

For example, if the minimum number of directory cache buffers is set to 20, the system allocates another buffer resource as soon as a request is made until 20 cache buffers have been allocated.

When 20 directory cache buffers are allocated, the system waits 2.2 seconds (default) when a request comes in, and then allocates another buffer if the request is still active.

However, if the minimum number of directory cache buffers is set to 40, the system allocates 40 directory cache buffers before it starts slowing the growth by waiting 2.2 seconds after each request.
Wait time limits control how rapidly the operating system can allocate a new resource.

Communication Parameters

Communication parameters control settings for communication buffers. Four parameters configure packet receive buffers; four control the watchdog.

Packet Receive Buffers are areas in the server's memory that are set aside to hold data packets. The packets remain in the buffers while the server processes them.
To view the number of packet receive buffers allocated, use MONITOR.
Watchdog Packets make sure stations are connected. If the server doesn't receive a packet from a station within a set time (Delay Before First Watchdog Packet), a watchdog packet is sent to the station.
If the station doesn't respond within a set time (Delay Between Watchdog Packets), another packet is sent. If the station doesn't respond to a set number of packets, the server assumes that the station is no longer connected and clears the station's connection.

See Table 7 for a description of communication parameters.

Table 7. Communication Parameters

Parameter	Use to
Maximum Packet Receive Buffers = number	Specify the maximum number of packet receive buffers the operating system can allocate. Supported values: 50 to 25000. Default: 100. Note: For SFT III systems, the default is 400. Before increasing this parameter, use MONITOR to view the server's use of packet receive buffers and service processes. If the number of packet receive buffers is at maximum, increase this parameter in increments of 10 until you have one packet receive buffer per workstation. If you have EISA or microchannel bus master boards in your server, increase this parameter to provide at least five buffers per board. If the board is producing No ECB available count errors, provide 10 buffers per board. Use MONITOR (LAN Information) to determine if the board is producing errors. If the number of allocated service processes is at maximum, you can increase the Maximum Service Processes parameter to decrease the need for more packet receive buffers. The value of this parameter should be greater than the value of the Minimum Packet Receive Buffers parameter. If it is less, the system increases the value to match that of the Minimum Packet Receive Buffers parameter. This parameter can be set in the appropriate startup .NCF file.
Minimum Packet Receive Buffers = number	Specify the minimum number of packet receive buffers the operating system can allocate. The operating system allocates this number of buffers as soon as the server boots. You must add this command to the STARTUP.NCF file. You cannot change the setting at the console prompt. Supported values: 10 to 20000. Default: 50. Note: For SFT III systems, the default is 100. This parameter must be set to the same value in the MSSTART.NCF and IOSTART.NCF files. Before increasing this parameter, use MONITOR to view the server's use of packet receive buffers. If you have EISA or microchannel bus master boards in your server and are receiving No ECB available count errors (see LAN Information in MONITOR) right after the server boots, increase this parameter so that each board can have at least five packet receive buffers. If the allocated number is higher than 10 and the server doesn't respond immediately after booting, increase this parameter. In NetWare 4.11, the value of this parameter must be less than the value of the Maximum Packet Receive Buffers parameter. If it is greater, the system increases the value of the Maximum Packet Receive Buffers parameter to match that of the Minimum Packet Receive Buffers parameter.
Maximum Physical Receive Packet Size = number	Specify the maximum size of packets that can be transmitted on the network. You must add this command to the STARTUP.NCF file. You cannot change the setting at the console prompt. Supported values: 618 to 24682. Default: 4202. The default allows 2 KB (data with the packet header). If you use token ring or Ethernet boards, the default is acceptable. If some of your network boards transmit more than 512 bytes of data per packet, set this parameter for the largest packet size.
IPX NetBIOS Replication Option = number	Specify how the IPX router handles replicated NetBIOS broadcasts. Supported values: 0 = Do not replicate NetBIOS broadcasts. 1 = Duplicate broadcasts when there are redundant routes. 2 = Suppress duplicate broadcasts. Default: 2.
Maximum Interrupt Events = number	Specify the maximum number of interrupt time events (such as IPX routing) allowed before a thread switch is guaranteed to have occurred. Supported values: 1 to 1000000. Default: 10.
Reply to Get Nearest Server = value	Specify whether the server responds to Get Nearest Server requests from stations trying to locate directory and file servers. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: ON.
Number of Watchdog Packets = number	Specify the number of unanswered watchdog packets that the server sends to a workstation before closing its connection. Supported values: 5 to 100. Default: 10.
Delay Between Watchdog Packets = time	Specify the amount of time between watchdog packets. Supported values: 9.9 seconds to 10 minutes 26.2 seconds. Default: 59.3 seconds. After a server sends out the first watchdog packet, it waits the specified time before sending out succeeding packets if it receives no reply.
Delay Before First Watchdog Packet = time	Specify the amount of time the server waits without receiving a request from a workstation before sending out the first watchdog packet to that station. Supported values: 15.7 seconds to 14 days. Default: 4 minutes 56.6 seconds.
New Packet Receive Buffer Wait Time = time	Specify how long the operating system waits after receiving a request for a packet receive buffer before granting a new buffer. Supported values: 0.1 second to 20 seconds. Default: 0.1 second. This parameter prevents the system from granting too many buffers during a sudden peak in usage. If you have an EISA bus master board in your server, don't change this parameter.
Console Display Watchdog Logouts = value	Specify whether a console message is displayed when a connection is cleared. Supported values: ON, OFF. Default: OFF. If your network is running smoothly, you don't need to display watchdog logouts. If your workstations are having connection problems, the watchdog logout messages can help you isolate which stations aren't receiving or sending watchdog packets.

Memory Parameters

Memory parameters control the size of the dynamic memory pool and the automatic registering of memory on EISA bus computers.

For a description of memory parameters, see Table 8.

Table 8. Memory Parameters

Parameter	Use to
Allow Invalid Pointers = value	Specify whether invalid pointers are allowed to cause a nonexistent page to be mapped in with only one notification. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: OFF.
Read Fault Notification = value	Specify whether the console and error log are notified of emulated read page faults. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: ON.
Read Fault Emulation = value	Specify whether a read that occurs from a nonpresent page is emulated. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: OFF.
Write Fault Notification = value	Specify whether the console and error log are notified of emulated write page faults. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: ON.
Write Fault Emulation = value	Specify whether a write that occurs from a nonpresent page is emulated. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: OFF.
Garbage Collection Interval = number	Specify the maximum time between garbage collections. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: 1 minute to 1 hour. Default: 15 minutes.
Number of Frees for Garbage Collection = number	Specify the minimum number of times memory must be freed before a garbage collection can occur. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: 100 to 100000. Default: 5000.
Minimum Free Memory for Garbage Collection = number	Specify the minimum free allocation bytes needed for garbage collection. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: 1000 to 1000000. Default: 8000.
Alloc Memory Check Flag = value	Specify whether the server will do corruption checking in the alloc memory nodes. This parameter can be set in the STARTUP.NCF file, if desired. Supported values: ON, OFF. Default: OFF.
Auto Register Memory Above 16 Megabytes = value	Control the automatic registering of memory above 16 MB in EISA computers. Supported values: ON, OFF. Default: ON. You must set this parameter in the STARTUP.NCF file. You cannot set the value at the command line. Use OFF if you have installed a network board or a disk adapter board that uses an online DMA or AT bus. (The board can address only 16 MB of memory correctly.) If you install one of these boards and the server addresses more than 16 MB of memory, the board corrupts server memory because it addresses low memory instead of its assigned high memory and corrupts the low memory in use. Use ON if you want memory above 16 MB to be registered with the operating system.
Reserved Buffers Below 16 Meg = number	Specify the number of file cache buffers reserved for device drivers that can't access memory above 16 MB. Supported values: 8 to 300. Default: 16. You must set this parameter in the STARTUP.NCF file. You cannot set the value at the command line.

File Caching Parameters

File caching allows faster access to frequently used files by holding a file (or a portion of it) in memory. Files being read from or written to are kept in file cache buffers.

The number of files kept in memory depends on the number of file cache buffers allowed. This is determined by the amount of memory available and the Minimum File Cache Buffers parameter.

See Table 9 for a description of file caching parameters.

Table 9. File Caching Parameters

Parameter	Use to
Read Ahead Enabled = value	Specify whether the system conducts background reads to cache in advance of blocks soon to be requested. Supported values: ON, OFF. Default: ON Read-aheads can happen only when sequential file accesses are occurring.
Read Ahead LRU Sitting Time Threshold = number	Specify the minimum cache LRU (least recently used) sitting time for read-aheads to take place. Supported values: 0 seconds to 1 hour. Default: 10 seconds.
Minimum File Cache Buffers = number	Set the minimum number of cache buffers the operating system can allow for file caching. Supported values: 20 to 1000. Default: 20. All memory not allocated for other processes is given to file caching. As memory is requested for other processes, the server gives up cache buffers. This limit specifies when the server must stop giving file cache buffers to other processes. If you set the minimum too high, other processes may not be able to allocate necessary memory resources. For example, a module could fail to load because the server is out of available memory.
Maximum Concurrent Disk Cache Writes = number	Specify the number of write requests for changed file data that can be put in the elevator before the disk head begins a sweep across the disk. Supported values: 10 to 4000. Default: 50. A high number creates more efficient write requests. A low number creates more efficient read requests. Monitor the number of dirty cache buffers on the information screen in MONITOR. If this number is above 70% of total cache buffers, optimize the write speed by increasing this parameter.
Dirty Disk Cache Delay Time = time	Specify how long the system keeps a write request (that does not fill a cache buffer) in memory before writing the request to disk. Supported values: 0.1 second to 10 seconds. Default: 3.3 seconds. Increasing the time makes disk writing more efficient if your users make many small write requests. Decreasing the time can reduce performance drastically, and reduces the chances of losing data only slightly.
Minimum File Cache Report Threshold = number	Specify how few cache buffers can be available before the operating system warns you that the number of buffers is getting low. Supported values: 0 to 1000. Default: 20 For example, if the Minimum File Cache Buffers parameter is set to 20 and this parameter is set to 25, you are warned when all but 45 cache buffers are allocated for other processes. Regardless of how this parameter is set, the operating system warns you when it reaches the minimum number of cache buffers. You receive the following message: Cache memory allocator exceeded minimum cache buffer left limit.

Directory Caching Parameters

Directory caching allows fast access to frequently used directories. A directory cache buffer is a portion of NetWare server memory that holds entries from the directory table.

A directory entry stays in a cache buffer as long as it is accessed frequently (default: 33 seconds). The system can overwrite the directory entry if the allocated directory cache buffers are accessed more frequently.

See Table 10 for a description of directory caching parameters.

Allocation of Directory Cache Buffers

When the server boots, the system allocates a minimum number of directory cache buffers (default: 20). It creates these buffers immediately when it receives a request for a new buffer.

When the minimum number of buffers is allocated and another is needed, the system must wait a specified amount of time before allocating another buffer.

If necessary, the system allocates buffers until it reaches the maximum. If enough directory cache buffers are allocated and enough memory is available for directory caching, all directory tables can be cached in memory.

How Directory Caching and File Caching Work Together

As directory cache buffers increase, file cache buffers decrease. Thus, a tradeoff exists between directory caching and file caching.

Directory caching and file caching must be balanced carefully for maximum performance.

If you adjust the system to use too much memory for directory caching, you can leave too little memory for file caching, and vice versa.

Table 10. Directory Caching Parameters

Parameter	Use to
Dirty Directory Cache Delay Time = time	Specify how long the system keeps a directory table write request in memory before writing it to disk. Supported values: 0 to 10 seconds. Default: 0.5 second Increasing the delay time gives slightly quicker performance but increases the probability of the directory tables becoming corrupted. Decreasing the delay time slightly reduces the chance of directory tables becoming corrupted, but can reduce performance slightly. A zero setting reduces performance dramatically.
Maximum Concurrent Directory Cache Writes = number	Specify how many write requests from directory cache buffers are put in the elevator before the disk head begins a sweep across the disk. Supported values: 5 to 50. Default: 10. A high number creates more efficient write requests. A low number creates more efficient read requests.
Directory Cache Allocation Wait Time = number	Specify how long the system must wait after allocating a new directory cache buffer before it can allocate another buffer. Supported values: 0.5 second to 2 minutes. Default: 2.2 seconds. During this time, all requests for a new directory cache buffer are ignored. If the wait time is too low, peak usage requests cause more resources than necessary to be allocated to directory caching. If the wait time is too high, the system is very slow in allocating the directory cache buffers necessary to service the usual number of directory requests. If directory searches seem slow even after the server has been running for 15 minutes, you may want to decrease this parameter.
Directory Cache Buffer NonReferenced Delay = time	Specify how long a directory entry must be cached before it can be overwritten by another directory entry. Supported values: 1 second to 5 minutes. Default: 5.5 seconds. Increasing this parameter speeds directory access. The system allocates more directory cache buffers, and a directory is more likely to be cached in memory. Decreasing this parameter slows directory access but also reduces the need for directory cache buffers.
Maximum Directory Cache Buffers = number	Specify the maximum number of cache buffers that the system can allocate for directory caching. Supported values: 20 to 4000. Default: 500. This parameter keeps the system from allocating too many directory cache buffers so that memory is available for other server processes. Increase this limit if the server responds slowly to directory searches. Decrease this limit if too much memory is being allocated for directory caching. If users are warned that the server is low on memory, this parameter should be one of the first to be reduced. (Reboot the server to return the memory to the cache buffer memory pool.) When a directory cache buffer is allocated, the allocation is permanent until the server reboots; the buffers don't return to file caching when the need for directory cache buffers decreases. This parameter can be set in the STARTUP.NCF file, if desired.
Minimum Directory Cache Buffers = number	Specify the minimum number of cache buffers that the system can allocate for directory caching. Supported values: 10 to 2000. Default: 20. The number needs to be high enough that directory searches can be done quickly, but no higher than necessary. If the system doesn't need the minimum number of directory cache buffers, the buffers can't be reallocated to file caching. The unneeded portion remains unused. If the server responds slowly to directory searches after it is booted, monitor the number of directory cache buffers usually allocated for directory caching. If the number is significantly higher than this limit, consider increasing the limit to remove the delay time that normally occurs while the server is self-configuring. Use MONITOR to view the current statistics. This parameter can be set in the STARTUP.NCF file, if desired.
Maximum Number of Internal Directory Handles = number	Specify the maximum number of directory handles available for internal NLMs that use connection 0. Supported values: 40 to 1000. Default: 100. A directory handle is a version of the directory access rights that is held in cache memory. Caching the access rights speeds mapping to the rights. Connection 0 is the connection number reserved for use by the server itself and by NLMs operating within the server. Each time an NLM program using connection zero accesses a file or directory, a directory handle is allocated (up to the total specified by this parameter). This value represents the total number of handles available to be shared by all NLMs using connection 0.
Maximum Number of Directory Handles = number	Specify the maximum number of directory handles available for each connection. Supported values: 20 to 1000. Default: 20. A directory handle is a version of the directory access rights that is held in cache memory. Caching the access rights speeds mapping to the rights. Each time a connection accesses a file or directory, a directory handle is allocated (up to the total specified by this parameter).

File System Parameters

Three parameters control warnings about volumes that are almost full.
Four parameters control file purging. File-purging parameters influence other parameters, which in turn control warnings about almost-full volumes.
All deleted files remain on the disk for a specified minimum amount of time. The system calculates a volume's remaining space by subtracting the following from the total space:
- Actual files
- Salvageable files that can't be purged because their Minimum File Delete Wait Times have not expired
One parameter controls the reuse of turbo FATs.
Eight parameters control file compression.

See Table 11 for a description of file system parameters.

Table 11. File System Parameters

Parameter	Use to
Minimum File Delete Wait Time = time	Specify how long a deleted file remains salvageable on the volume. Supported values: 0 seconds to 7 days. Default: 1 minute 5.9 seconds. Files deleted for less than this minimum aren't automatically purged even if the volume is full and users can't create new files.
File Delete Wait Time = time	Specify when a salvageable file can be purged to create free space on a volume. Supported values: 0 seconds to 7 days. Default: 5 minutes 29.6 seconds. Set this parameter as high as is useful for your users, but this parameter doesn't guarantee that a file remains salvageable. The system tries to keep at least 1/32 of available space on the volume free for new files. This parameter only guarantees that files aren't purged to maintain this free disk space. Files that haven't met this time limit are purged if the volume is full and the system needs space for a user to create a new file. When a deleted file remains on the server longer than the File Delete Wait Time parameter setting, the system marks the file as purgeable. When the volume is full of purgeable files and needs free space, the oldest purgeable files are purged.
Allow Deletion of Active Directories = value	Specify whether a directory can be deleted when another connection has a drive mapped to it. Supported values: ON, OFF. Default: ON.
Maximum Percent of Volume Space Allowed for Extended Attributes = percentage	Limit the portion of volume space used for extended attribute storage. The setting takes effect only when the volume is being mounted. Supported values: 5 to 50. Default: 10.
Maximum Extended Attributes per File or Path = number	Limit the number of extended attributes that can be assigned to a file or path (subdirectory). This limit applies to all volumes on the server. Supported values: 4 to 512. Default: 16.
Fast Volume Mounts	Increase the speed at which volumes are mounted. Supported values: ON, OFF Default: ON. The operating system checks o only the most important fields during the mounting process. Use this parameter only if volumes were dismounted normally. This parameter can be set in the STARTUP.NCF file.
Maximum Percent of Volume Used by Directory = percentage	Limit the portion of a volume that can be used as directory space. Supported values: 5 to 85. Default: 13.
Immediate Purge of Deleted Files = value	Controls whether deleted files can be salvaged. If this parameter is set to OFF, files can be salvaged with the FILER utility. See FILER Supported values: ON, OFF. Default: OFF. If this parameter is set to ON, all files are purged immediately when they are deleted.
Maximum Subdirectory Tree Depth = number	Specify how many levels of subdirectories the system supports. Supported values: 10 to 100. Default: 25. You must set this parameter in the STARTUP.NCF file. You cannot set the parameter at the command line. Increase the number if your applications support trees deeper than 25. Decrease the number if your applications support only shallow tree structures. (Some DOS applications can't support more than 10 levels if the subdirectories have 11-character names.)
Volume Low Warn All Users = value	Have the system notify users when a volume is almost full. Supported values: ON, OFF. Default: ON. If you choose not to have your server warn users, monitor volume statistics at least daily with SERVMAN or MONITOR.
Volume Low Warning Reset Threshold = number	Control how much disk space must be freed up before a second warning is issued that the volume is almost full. (The first warning is controlled by the Volume Low Warn All Users parameter.) Supported values: 0 to 100000 blocks. Default: 256 blocks. When a volume is almost full, it can hover at its warning threshold as users create and delete files. This parameter controls the minimum amount of space that must be made available above the threshold before the warning message disappears. Example: Assume the volume block size is 4 KB, the Volume Low Warning Reset Threshold is set to 256, the Volume Low Warning Threshold is set to 256, and the volume has less than 1 MB of free space. Given these conditions, the volume must gain at least 1 MB of free space (for a total of 2 MB of free space) and then dip below 1 MB before the system sends another warning that the volume is almost full.
Volume Low Warning Threshold = number	Specify the number of blocks of free disk space that can remain on a volume before the system issues a warning. Supported values: 0 to 1000000 blocks. Default: 256 blocks. Consider the following: A block is the minimum space allocated to a file; a file can grow only in multiples of the block size. The block's physical size is determined when the volume is created. A volume can be assigned these block sizes: 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB. For example, if you enter 256 blocks for this parameter and the volume's block size is 4 KB, the system warns you that the volume is full when about 1 MB of space is left. If your volumes are assigned different block sizes, each volume has a different amount of free space when the warning is issued.
Turbo FAT Re-Use Wait Time = time	Specify how long a turbo FAT buffer remains in memory after an indexed file is closed. Supported values: 0.3 second to 1 hour 5 minutes 54.6 seconds. Default: 5 minutes 29.6 seconds. Once the wait-time value has passed, the system can allocate the buffer to another indexed file. Increase the wait time if You want the turbo FAT index to remain in memory for long periods of time, even when the file is closed. You frequently reopen the same file after a specific delay and know that another file opened during that delay will reuse the index. Decrease the wait time if you want the memory released immediately to service the next file that needs to be indexed. When a program randomly accesses a file that contains more than 64 FAT entries, the system builds a turbo FAT index for the file so that information is accessed quickly. (The NetWare 3 system indexes any randomly accessed file with 64 entries in the FAT.) The system doesn't immediately delete the index from its buffer when the file is closed. Having the turbo FAT index in memory makes reopening the file and accessing information faster.
Compression Daily Check Stop Hour = number	Specify the hour when you want the file compressor to stop scanning enabled volumes for files that need to be compressed. Supported values: 0 to 23. Default: 6. Hours are specified by a 24-hour clock: 0 = midnight; 23 = 11 p.m. This parameter can be set in the STARTUP.NCF file, if desired.
Compression Daily Check Starting Hour = number	Specify the hour when you want the file compressor to start scanning enabled volumes for files that need to be compressed. Supported values: 0 to 23. Default: 0. Hours are specified by a 24-hour clock: 0 = midnight; 23 = 11 p.m. Note: If the Compression Daily Check Stop Hour parameter is the same as the Compression Daily Check Starting Hour, then the file compressor starts checking every day at the Compression Daily Starting Hour time and runs as long as necessary to finish all files that meet the compressible criteria. This parameter can be set in the STARTUP.NCF file, if desired.
Minimum Compression Percentage Gain = number	Set the minimum percentage a file must compress to remain in a compressed state. Supported values: 0 to 50. Default: 20. This parameter can be set in the STARTUP.NCF file, if desired.
Enable File Compression = value	Specify whether file compression is suspended. Supported values: ON, OFF. Default: ON. ON allows file compression on compression-enabled volumes. OFF suspends compression; immediate compress requests are queued until value is reset to ON, when the files meeting criteria will be compressed. This parameter can be set in the STARTUP.NCF file, if desired.
Maximum Concurrent Compressions = number	Specify the maximum concurrent or simultaneous compressions allowed. Supported values: 1 to 8. Default: 2. Concurrent compressions can occur only if there are multiple volumes. This parameter can be set in the STARTUP.NCF file, if desired.
Convert Compressed to Uncompressed Option = value	Specify what the system does with an uncompressed version of a file after the server has uncompressed it. Supported values: 0 = Always leave the file compressed. 1 = Leave the file compressed until second access if it is read only once during the time specified by the Days Untouched Before Compression parameter. 2 = Always leave the file uncompressed. Default: 1 This parameter can be set in the STARTUP.NCF file, if desired.
Decompress Percent Disk Space Free to Allow Commit = number	Specify the percentage of free disk space required on a volume for file uncompression to permanently change compressed files to uncompressed. Supported values: 0 to 75. Default: 10. This parameter prevents newly uncompressed files from filling up the volume. This parameter can be set in the STARTUP.NCF file, if desired.
Decompress Free Space Warning Interval = number	Specify the time between alerts when the file system is not changing compressed files to uncompressed because of insufficient disk space. Supported values: 0 seconds to 29 days 15 hours 50 minutes 3.8 seconds. Default: 31 minutes 18.5 seconds. This parameter can be set in the STARTUP.NCF file, if desired.
Deleted Files Compression Option = number	Specify whether and when deleted files are compressed. Supported values: 0 = Don't Compress deleted files. 1 = Compress deleted files the next day. 2 = Compress deleted files immediately. Default: 1. This parameter can be set in the STARTUP.NCF file, if desired.
Days Untouched Before Compression = number	Specify the number of days the system waits after a file was last accessed before it is compressed Supported values: 0 to 100000. Default: 14. This parameter can be set in the STARTUP.NCF file, if desired.
Allow Unowned Files To Be Extended = value	Specify whether files can be modified when the owner has been lost or deleted. Supported values: ON, OFF. Default: ON This parameter can be set in the STARTUP.NCF file, if desired.

Lock Parameters

Lock parameters control

How many open files each workstation can have
How many open files the system can handle
How many record locks each connection can have
How many record locks the system can handle

There are three types of locks:

File locks secure the file and prevent other stations from accessing it.
Physical record locks control data access by multiple users. They prevent other users from accessing or changing a range of bytes (a record) in a file.
Physical record locks are enforced by the system. If a user tries to access a range of bytes that is physically locked, the user receives an Access Denied error message.
Logical record locks also control data access by multiple users. The application assigns a name to each section of data that needs to be locked. The application then locks this name whenever it accesses the data.
Logical locks are enforced only to the extent that the application checks the name each time it needs access to data.

See Table 12 for a description of lock parameters.

Table 12. Lock Parameters

Parameter	Use to
Maximum Record Locks Per Connection = number	Control how many record locks a workstation can use at one time. (Use MONITOR to view how many record locks a station is using.) Supported values: 10 to 100000. Default: 500. Increase this parameter when an application can't lock enough records and fails. Decrease this parameter if stations are using too many server resources.
Maximum File Locks Per Connection = number	Control how many opened and locked files a station can use at one time. (Use MONITOR to view how many opened and locked files a station is using.) Supported values: 10 to 1000. Default: 250. Increase this parameter when an application can't open enough files and fails. (An OS/2 station might need a higher default than 250. You may also need to increase the number of file handles in the station's NET.CFG file.) Decrease this parameter if stations are using too many server resources.
Maximum Record Locks = number	Control how many record locks the operating system can handle. (Use MONITOR to view how many record locks a station is using on that server.) Supported values: 100 to 400000. Default: 20000. Increase this parameter if users have problems running applications and receive messages indicating that not enough record locks are available. Decrease this parameter if users are using too many server resources.
Maximum File Locks = number	Control how many opened and locked files the operating system can handle. (Use MONITOR to view the number of files that are open during peak usage.) Supported values: 100 to 100000. Default: 10000. Increase this parameter if the number of open files is near or equal to the default. Decrease this parameter to restrict the number of available server resources.

Transaction Tracking Parameters

A transaction is a set of write operations that must be completed together to maintain file and database integrity.
Write operations consist not only of data and data records, but also of changes to the index and the key structures that are important to an application's continual operation.
The Transaction Tracking System^TM (TTS) guarantees that a transaction is written to disk in its complete form or is backed out if incomplete. This ensures database integrity in case a failure occurs before a transaction is completed.

See Table 13 for a description of transaction tracking parameters.

Table 13. Transaction Tracking Parameters

Parameter	Use to
Auto TTS Backout Flag = value	Specify whether a crashed server with transactional files can automatically back out of incomplete transactions when the server is booted. Supported values: ON = The server backs out incomplete transactions when booting. OFF = The server waits for you to answer a prompt before it boots. Default: ON. You must set this parameter in STARTUP.NCF. You cannot set the parameter at the command line.
TTS Abort Dump Flag = value	Specify whether a file is created to log transactional backout data. Supported values: ON = The information is saved in TTS$LOG.ERR. OFF = The information backed out is not saved. Default: OFF. When a server fails during a data write to a file flagged Transactional, the system can back out the incomplete write. The backed-out information is written to file TTS$LOG.ERR on volume SYS:. You can print the file or view it with a text editor.
Maximum Transactions = number	Specify how many transactions can occur at the same time. Supported values: 100 to 10000. Default: 10000.
TTS UnWritten Cache Wait Time = time	Specify how long a block of transactional data can be held in memory. Supported values: 11 seconds to 10 minutes 59.1 seconds. Default: 1 minute 5.9 seconds. Some blocks of transactional data wait for other transactional blocks to be written first. If one of these blocks reaches its maximum time limit, other write requests are held up and this block is written to disk.
TTS Backout File Truncation Wait Time = time	Specify how long allocated blocks remain available for the TTS backout file when these blocks are not in use. Supported values: 1 minute 5.9 seconds to 1 day 2 hours 21 minutes 51.3 seconds. Default: 59 minutes 19.2 seconds.

Disk Parameters

Disk parameters control one part of Hot Fix^TM redirection. Hot Fix redirection can occur during a write request, a read request, or a read-after-write verification.

Write redirection occurs when the disk reports an error during a write request. The system marks the block as bad and redirects the data to a different block.
Read redirection occurs when a disk error happens during a read request.
If the disk is mirrored, the system retrieves the data from the mirrored disk and redirects the data on the primary disk. If the disk isn't mirrored, the data is lost, but the block is marked as bad.
Read-after-write verify redirection occurs after data is written to disk. The data on disk is then read and compared to that in memory.

If the two don't match, the system marks the block as bad and redirects the data to a different block.

See Table 14 for a description of disk parameters.

Table 14. Disk Parameters

Parameter	Use to
Enable Disk Read After Write Verify = value	Control whether information written to disk is compared with that in memory. Usually, you shouldn't disable this portion of Hot Fix. Supported values: ON, OFF. Default: ON. If your disks are mirrored and reliable and you need extra speed on disk writes, using OFF can almost double the speed of disk writes. Some disks and drivers provide their own read-after-write verify procedure. In this case, set the parameter to OFF, so the read-after-write-verify operation isn't done twice. Changing this value affects only disks loaded after the parameter is changed. To set this value for currently loaded disks, use the Disk Information option of the MONITOR utility. See MONITOR You can set this parameter in the STARTUP.NCF file.
Remirror Block Size = value	Sets the remirror block size in 4 KB increments. (1=4 KB, 2=8 KB, 8=32 KB, etc.) Supported values: 1 to 8. Default: 1.
Concurrent Remirror Requests = value	Sets the number of remirror requests per logical partition. Supported values: 2 to 32. Default: 4.
Mirrored Devices Are Out of Sync Message Frequency = time	Sets the frequency (in minutes) for checking out-of-sync devices. Supported values: 5 to 9999 minutes. Default: 30 minutes. You can set this parameter in the STARTUP.NCF file.
Ignore Disk Geometry = value	Create nonstandard and unsupported partitions. Supported values: ON, OFF. Default: OFF. If you set this parameter to ON before modifying or creating a partition, the software ignores disk geometry when reading or writing the disk partition. This allows you to create nonstandard partitions. Caution: Setting this parameter to ON may harm other file systems contained on the disk. You can set this parameter in the STARTUP.NCF file.
Enable IO Handicap Attribute = value	Enable drivers and applications to set an attribute to inhibit read requests from one or more devices. Supported values: ON, OFF. Default: OFF. Setting this parameter to ON enables the inhibit attribute to function. Setting this parameter to OFF prevents the attribute from functioning. Do not set this attribute to ON unless instructed to do so by a device manufacturer. You can set this parameter in the STARTUP.NCF file.

Time Synchronization Parameters

Time parameters control time synchronization, the TIMESYNC.CFG file, and time zone settings to insure that the time reported by all servers is consistent, or synchronized. (See Time Synchronization in Concepts.)

See Table 15 for a description of time parameters.

Table 15. Time Synchronization Parameters

Parameter	Use to
TIMESYNC ADD Time Source = server name	Specify a server as a time source. Use EDIT, rather than this parameter, to add a server to the time source list in the TIMESYNC.CFG file. Maximum: 48 characters.
TIMESYNC Configuration File = path	Specify the path where the TIMESYNC.CFG configuration file is located. Maximum: 255 characters. Example: SET TIMESYNC CONFIGURATION FILE = SYS:SYSTEM\TIMESYNC.CFG
TIMESYNC Configured Sources = value	Specify what time sources the server listens to. Supported values: ON = The server ignores SAP time sources and relies on time sources custom-configured with the TIMESYNC Time Source parameter. OFF = The server listens to any advertising time source. Default: OFF.
TIMESYNC Directory Tree Mode = value	Control the use of SAP packets in the Directory tree. Supported values: ON = Time synchronization ignores SAP packets that don't originate from within the Directory tree the server is on. OFF = The server can receive SAP packets from any time source on the network. Default: ON. Don't set this parameter to OFF if SAP is set to ON. Using OFF could corrupt the time synchronization for this server's Directory tree.
TIMESYNC Hardware Clock = value	Controls hardware clock synchronization. Supported values: ON = The Primary and Secondary time servers set the hardware clock, and the Single Reference and Reference Servers set their time from the hardware clock at the beginning of each polling interval. OFF = Use only if this server uses an external time source (such as a radio clock). Default: ON.
TIMESYNC Polling Count = number	Specify how many time packets to exchange while polling. Increasing the number of packets adds unnecessary traffic to the network. Supported values: 1 to 1000. Default: 3.
TIMESYNC Polling Interval = number	Specify the long polling interval, in seconds. Supported values: 10 to 2678400 seconds (31 days). Default: 600 seconds (10 minutes). All servers in the same tree must use the same setting.
TIMESYNC REMOVE Time Source = server name	Delete a server as a time source. Use EDIT, rather than this parameter, to delete a server from the time source list in the TIMESYNC.CFG file. Maximum: 48 characters.
TIMESYNC RESET = value	Reset time synchronization and clear the time source list. Use EDIT, rather than this parameter, to reset values in the TIMESYNC.CFG file and to remove the time source list from the file. Supported values: ON = Selected internal values are reset and the configured server list is cleared. Flag automatically resets to OFF. Default: OFF.
TIMESYNC Restart Flag = value	Control restarts of time synchronization. Supported values: ON, OFF. Default: OFF. Set this parameter to ON only if you want to reload TIMESYNC without rebooting the server.
TIMESYNC Service Advertising = value	Control time source advertising. Supported values: ON = The Single Reference, Reference, and Primary time source advertise using SAP. OFF = Use only if you are using a custom-configured list of time sources. Default: ON. Note: Secondary time services do not advertise.
TIMESYNC Synchronization Radius = number	Control the maximum time adjustment (in milliseconds) a server is allowed while still being considered synchronized. Supported values: 0 to 2147483647 milliseconds. Default: 2000. Increase this parameter to allow a wider margin of error for time synchronization between servers. Important: Lowering the synchronization radius increases the chance of servers losing synchronization due to randomness between clocks. Setting the synchronization radius for under 2000 milliseconds (2 seconds) is not recommended. Set the synchronization radius for under 2 seconds only if you are using an application that uses synchronized time stamps which do not tolerate a 2-second deviation between time sources.
TIMESYNC Time Adjustment = [+ or -] hour:minute:second [at month/day/year hour:minute:second AM or PM]	Specify when a time adjustment will take place. Note: You cannot use this parameter on a Secondary time server. Maximum: 99 characters. Default: None scheduled. Use this parameter sparingly to correct network-wide time errors. Default date and time is six polling intervals or 1 hour (whichever is longer) from the current time. Misuse of this parameter can corrupt time synchronization and the order of events on your network.
TIMESYNC Time Source: server name	Specify a server as time source. If no server name is entered, the parameter displays the list of configured servers. Use EDIT, rather than this parameter, to add a server to the configuration list in the TIMESYNC.CFG file. Maximum: 48 characters.
TIMESYNC Type = type of time source	Specify the default time source type. Use EDIT, rather than this parameter, to specify the default time source type in the TIMESYNC.CFG file. Supported types: Reference, Primary, Secondary, Single Reference. Maximum: 23 characters. Default: Single Reference.
TIMESYNC Write Parameters = value	Specify whether parameters specified by the TIMESYNC Write Value parameter are written to the configuration file. Supported values: ON, OFF. Default: OFF.
TIMESYNC Write Value = number	Control which parameters are written by TIMESYNC Write Parameters. Supported values: 1 = Write internal parameters only. 2 = Write configured time sources only. 3 = Write both parameters and configured time sources. Default: 3
Time Zone = time zone string	Specifies the time zone string, which indicates: The abbreviated time zone name. The offset from Universal Time (UTC). The alternate abbreviated time zone name to be used when daylight saving time is in effect. Maximum: 80 characters. Default: No Time Zone. This parameter causes UTC time to be recalculated from local time. You can set this parameter in the STARTUP.NCF file.
Default Time Server Type = type of time source	Specify the default time synchronization server type. This parameter can be overridden by other time synchronization parameters. Supported types: Reference, Primary, Secondary, Single Reference. Maximum: 50. Default: Secondary. You can set this parameter in the STARTUP.NCF file.
Start of Daylight Savings Time = date and time	Specify the local date and time when the change to daylight saving time should occur. Maximum: 79 characters. Important: You must set both the start and end of daylight saving time before either date is actually scheduled.
End of Daylight Savings Time = date and time	Specify the local date and time when the change from daylight saving time should occur. Maximum: 79 characters. Important: You must set both the start and the end of daylight saving time before either date is actually scheduled.
Daylight Savings Time Offset = [+ or -] hour:minute:second	Control the offset applied to time calculations when daylight saving time is in effect. Default: +1:00:00. This parameter causes UTC time to be recalculated from local time. You can set this parameter in the STARTUP.NCF file.
Daylight Savings Time Status = value	Indicate whether daylight saving time is in effect. Supported values: ON, OFF. Default: OFF. If this parameter is set to ON, you should also use the Daylight Savings Time Offset parameter. Changing the daylight saving time status does not change the local time. You can set this parameter in the STARTUP.NCF file.
New Time With Daylight Savings Time Status = value	Control the adjustment of local time when daylight saving time is in effect. Supported values: ON, OFF. Default: OFF. ON = Adjust the local time by adding or subtracting the Daylight Saving Time Offset parameter.

NCP Parameters

With NetWare Core Protocol^TM (NCP) parameters, you can

Control NCP^TM packets
Control boundary checking
Assign the NCP Server Packet Signature levels

See Table 16 for a description of NCP parameters.

Table 16. NCP Parameters

Parameter	Use to
NCP File Commit = value	Control whether applications can flush pending file writes to disk. Supported values: ON, OFF. Default: ON. If the value is set to ON then when a File Commit NCP is issued, a file is sent from cache to disk immediately, instead of waiting for the cache manager to send it to disk later.
Display NCP Bad Component Warnings = value	Control whether NCP bad component alert messages are displayed. Supported values: ON, OFF. Default: OFF. This parameter can be set in the STARTUP.NCF file, if desired.
Reject NCP Packets with Bad Components = value	Specify whether NCP packets that fail component checking are rejected. Supported values: ON, OFF. Default: OFF. This parameter must be set to ON for the NetWare operating system to run in the Enhanced Security configuration. If the Enable SECURE.NCF parameter is set to ON, the Reject NCP Packets with Bad Components parameter is automatically set to ON at server startup. The Enable SECURE.NCF parameter is located in the Miscellaneous parameters. This parameter can be set in the STARTUP.NCF file, if desired.
Display NCP Bad Length Warnings = value	Control whether NCP bad length alert messages are displayed. Supported values: ON, OFF. Default: OFF. This parameter can be set in the STARTUP.NCF file, if desired.
Reject NCP Packets with Bad Lengths = value	Specify whether NCP packets that fail boundary checking are rejected. This parameter can be used as a debugging tool. Supported values: ON, OFF. Default: OFF. This parameter must be set to ON for the NetWare operating system to run in the Enhanced Security configuration. If the Enable SECURE.NCF parameter is set to ON, the Reject NCP Packets with Bad Lengths parameter is automatically set to ON at server startup. The Enable SECURE.NCF parameter is located in the Miscellaneous parameters. This parameter can be set in the STARTUP.NCF file, if desired.
Maximum Outstanding NCP Searches = number	Specify the maximum number of NCP directory searches that can be processed simultaneously. Supported values: 10 to 1000. Default: 51. Normally, only one NCP directory search occurs at a time. Increase the default only if you use applications that support multiple outstanding directory search operations and you have problems with corrupted or invalid directory information.
NCP Packet Signature Option = number	Control the NCP packet signature level on the server. Supported values: 0 = Server doesn't sign packets (regardless of the client level). 1 = Server signs packets only if the client requests it (client level is 2 or higher). 2 = Server signs packets if the client is capable of signing (client level is 1 or higher). 3 = Server signs packets and requires all clients to sign packets (or logging in will fail). Default: 1. NCP Packet Signature prevents packet forgery on servers and clients using NCP by requiring server and client to sign each NCP packet. Note: Because Packet Signature consumes CPU resources and slows performance on both client and server, NCP Packet Signature is optional. This parameter can be set in the STARTUP.NCF file, if desired.
Enable IPX Checksums = number	Specify the enabling of IPX checksums. Supported values: 0 = For no checksums. 1 = To checksum if enabled at the client. 2 = To require checksums. Default: 1. This parameter can be set in the STARTUP.NCF file, if desired.
Allow Change to Client Rights = value	Control whether a job server can assume the rights of a client for NCP packet signatures. Supported values: ON, OFF. Default: ON. Note: Some job servers and third-party applications can't function without changing to client rights. Using OFF may prevent some job servers from getting access to the files they need, but it prevents the forging of a packet through the job or print server. This parameter can be set in the STARTUP.NCF file, if desired.
Allow LIP = value	Set Large Internet Packet (LIP) support. Supported values: ON, OFF. Default: ON. This parameter can be set in the STARTUP.NCF file, if desired.

Miscellaneous Parameters

These parameters include various alert settings, as well as other miscellaneous parameters.

If you have loaded the NetWare Symmetric MultiProcessing (SMP) system, this category includes SMP parameters.

See the parameter descriptions in Table 17.

Table 17. Miscellaneous Parameters

Parameter	Use to
Command Line Prompt Default Choice = value	Specify a default response to an optional command in a .NCF file. An optional command in a .NCF file is preceded by a question mark (?). The question mark causes the file to prompt you to execute the command. For information about optional commands in .NCF files, see Chapter 7, Maintaining the NetWare Server, in Supervising the Network. Supported Values: ON, OFF. Default: ON. ON means the default response to the command prompt is Y (yes). If the user does not respond to the prompt within a specified time period, the command is executed by default. OFF means the default response to the command prompt is N (no). If the user does not respond to the prompt within a specified time period, the command is not executed. To specify the time period before the response is executed, use the Command Line Prompt Time Out parameter.
Command Line Prompt Time Out = time	Specify how long a .NCF file waits before executing the default response to an optional command. An optional command in a .NCF file is preceded by a question mark (?). The question mark causes the file to prompt you to execute the command. For information about optional commands in .NCF files, see Chapter 7, Maintaining the NetWare Server, in Supervising the Network. Supported Values: 0 to 4294967295 seconds. Default: 10 seconds.
Sound Bell for Alerts = value	Control whether a bell sounds when an alert message appears on the console. Supported values: ON, OFF. Default: ON.
Replace Console Prompt with Server Name = value	Control whether the console prompt is replaced with the NetWare server name. Supported values: ON, OFF. Default: ON. You can set this parameter in the STARTUP.NCF file.
Alert Message Nodes = number	Specify the number of alert message nodes that have been previously allocated. Supported values: 10 to 256. Default: 20. You can set this parameter in the STARTUP.NCF file.
Worker Thread Execute In a Row Count = number	Specify the number of times the scheduler consecutively dispatches new work before allowing other threads to run. Supported values: 1 to 20. Default: 10.
Halt System on Invalid Parameters = value	Specify whether to stop the system when invalid parameters are detected. Supported values: ON = You want the system to halt when an invalid parameter or condition is detected. OFF = You want the system to display an alert and continue running when an invalid parameter or condition is detected. Default: OFF. You can set this parameter in the STARTUP.NCF file.
Upgrade Low Priority Threads = value	Specify whether low-priority threads are scheduled at regular priority. Some modules can freeze up low-priority threads, causing file compression to shut down and other problems. Supported values: ON, OFF. Default: OFF.
Display Relinquish Control Alerts = value	Control whether messages about CPU control are sent to the server console. This parameter can be used as a debugging tool. Supported values: ON = Use if you're writing your own loadable modules. OFF = Use if you're not writing your own loadable modules. Default: OFF. If a module uses the processor for more than 0.4 second without relinquishing control to other processes, the following types of messages appear: <process name> Process did not relinquish control frequently. Module: <module name> Code offset in module: <memory address> You can set this parameter in the STARTUP.NCF file.
Display Incomplete IPX Packet Alerts = value	Specify whether alert messages are displayed when IPX receives incomplete packets. This parameter can be used as a debugging tool. Supported values: ON, OFF. Default: ON. You can set this parameter in the STARTUP.NCF file.
Display Old API Names = value	Control messages about NetWare 3 API calls. This parameter can be used as a debugging tool. Supported values: ON = Use if you write your own modules and you are upgrading NetWare 3.0 modules to modules using newer APIs. OFF = Use if you aren't upgrading modules. Default: OFF The following types of messages appear when a module is loaded that uses the old APIs: Module is using old API: SetInterruptVector Module is using old API: ReturnPermanentMemory Module is using old API: AllocateReturnablePermMemory The old APIs work, but more slowly than the new APIs. If you receive these messages, contact the vender of the module. You can set this parameter in the STARTUP.NCF file.
Developer Option = value	Control whether options associated with a developer environment are enabled. Supported values: ON, OFF. Default: OFF. You can set this parameter in the STARTUP.NCF file.
Display Spurious Interrupt Alerts = value	Control alert messages about spurious interrupts. Supported values: ON, OFF. Default: ON. A spurious interrupt occurs when hardware in the server creates an interrupt that is defined and reserved for another device. Spurious interrupts generate the following message: Spurious hardware interrupt <number> detected. This message indicates a serious error in the hardware. If your server console displays this message, remove all add-on boards and run SERVER. If the message doesn't appear, add the boards one at a time to determine the hardware creating the spurious interrupt. Then contact the vendor. Set the parameter to OFF while you are waiting for a resolution. You can set this parameter in the STARTUP.NCF file.
Display Lost Interrupt Alerts = value	Control alert messages about lost interrupts. Supported values: ON, OFF. Default: ON. A lost interrupt occurs when a driver or board requests a service with an interrupt call and then drops the request before the CPU can respond. Lost interrupts generate the following message: Interrupt controller detected a lost hardware interrupt. This message indicates a hardware or driver problem that could degrade performance. Unload all drivers and then reload them one at a time to determine which driver has a problem. Then contact the vender of the driver. Set the parameter to OFF while you are waiting for a resolution. You can set this parameter in the STARTUP.NCF file.
Pseudo Preemption Count = number	Specify the number of times threads are allowed to make file read or write system calls before a relinquish is forced. Supported values: 1 to 4294967295. Default: 10.
Global Pseudo Preemption = value	Specify whether or not all threads use pseudo preemption. Supported values: ON, OFF. Default: OFF
Minimum Service Processes = number	Specify the minimum number of service processes the operating system can create without having to wait for the time specified by the New Service Process Wait Time parameter. Supported values: 10 to 500. Default: 10.
Maximum Service Processes = number	Specify the maximum number of service processes that the operating system can create. (View the number of service processes in MONITOR.) Supported values: 5 to 1000. Default: 40. Decrease this parameter temporarily if the server is low on memory. If the server is always low on memory, add memory. Increase this parameter if the number of service processes is at the maximum. Increasing this number helps only if more than 20 requests are being delayed simultaneously for a disk I/O to be completed.
New Service Process Wait Time = number	Specify how long the system should wait to make an allocation when it receives a request for another service process. Supported values: 0.3 second to 20 seconds. Default: 2.2 seconds.
Automatically Repair Bad Volumes = value	Specify whether VREPAIR runs automatically on a volume that fails to mount. Supported values: ON, OFF. Default: ON. This parameter must be set to ON for the NetWare operating system to run in the Enhanced Security configuration. If the Enable SECURE.NCF parameter is set to ON, the Automatically Repair Bad Volumes parameter is automatically set to ON at server startup. The Enable SECURE.NCF parameter is located in the Miscellaneous parameters. You can set this parameter in the STARTUP.NCF file.
Enable SECURE.NCF=value	Execute the SECURE.NCF file at server startup. Supported values: ON, OFF. Default: OFF. When this parameter is set to ON, the SECURE.NCF file is executed at server startup. The SECURE.NCF file sets the options required to run the NetWare operating system in the Enhanced Security configuration. For more information about the Enhanced Security configuration, seeAuditing the Network. You can set this parameter in the AUTOEXEC.NCF or STARTUP.NCF file.
Allow Audit Passwords = value	Specify whether passwords can be used to identify auditors. Supported values: ON, OFF. Default: OFF. This parameter must be set to OFF for the NetWare operating system to run in the Enhanced Security configuration. If the Enable SECURE.NCF parameter is set to ON, the Allow Audit Passwords parameter is automatically set to OFF at server startup. The Enable SECURE.NCF parameter is located in the Miscellaneous parameters.
Allow Unencrypted Passwords = value	Control the use of unencrypted passwords. If your servers run NetWare 3.1x, use OFF. Supported values: ON, OFF. Default: OFF. This parameter must be set to OFF for the NetWare operating system to run in the Enhanced Security configuration. If the Enable SECURE.NCF parameter is set to ON, the Allow Unencrypted Passwords parameter is automatically set to OFF at server startup. The Enable SECURE.NCF parameter is located in the Miscellaneous parameters. If your servers run versions of NetWare earlier than NetWare 3.0 and you leave the parameter set to OFF, your users might have problems logging in. If you have servers that run NetWare 2.12 and later versions, copy the NetWare 3.1x utilities to those servers and set this parameter to OFF. If you don't copy NetWare 3.1x utilities to NetWare 2 servers, use ON.
SMP Stack Size = number	Specify the minimum stack size for threads created by the SMP kernel APIs. Allocation requests for stacks smaller than this size will return the smallest value specified by this SET parameter. Do not change this parameter value unless an application package instructs you to specify a certain minimum stack size. A NetWare Loadable Module^TM (NLM) program can specify stack sizes on a per-thread basis independently of this parameter. Minimum value: 8192. Maximum value: 1048576. Default: 8192.
SMP Polling Count = number	Specify the maximum number of thread switches that will occur before NetWare runs symmetric polling procedures. Do not change this value unless an application package instructs you to do so. Polling procedures affected by this parameter include network board, disk adapter, and internal maintenance routines. Minimum value: 70 Maximum value: 200 Default: 70
SMP NetWare Kernel Mode = value	Specify whether processor 0 is dedicated to native NetWare, shared by both the SMP and native NetWare kernels, or shared but with priority given to native NetWare. Dedicated means native NetWare has exclusive access to processor 0. Shared means native NetWare threads and SMP threads share processor 0, and SMP threads preempt native NetWare threads. Priority means that native NetWare threads have priority while sharing processor 0. This setting is most useful when your system runs more than seven processors. Supported values: Dedicated, Shared, Priority Default: Shared
SMP Flush Processor Cache = value	Issue a WBINVD instruction that will cause the entire level 1 and level 2 processor caches to be flushed into core memory on processor shutdown. This is often necessary in systems that do not maintain the cache controller in a warm state following processor shutdown. Do not change this value unless your hardware documentation instructs you to do so. Supported values: ON, OFF Default: OFF
SMP Intrusive Abend Mode = value	Specify whether the server starts the SMP debugger when the server abends. When this parameter is set to ON, the server starts the SMP debugger whenever the system abends. When this parameter is set to OFF, the server does not start the debugger. Instead, it halts the offending thread and continues to run. However, if the system abends during an interrupt, the server starts the debugger even if the parameter is set to OFF. To exit the debugger, type x at the debugger prompt. For more information about the SMP debugger, see the NetWare SMP Software Developer Kit. Supported values: ON, OFF Default: ON
SMP Developer Option = value	Specify whether the server starts the SMP debugger both when the server abends and when the server memory protection detects a memory fault. When this parameter is set to ON, the server starts the SMP debugger both when the server abends and when the server memory protection detects a memory fault. When this parameter is set to OFF, the server does not start the debugger. Instead, it halts the offending thread and continues to run. However, if the server abends during an interrupt, the server starts the debugger even if the parameter is set to OFF. To exit the debugger, type x at the debugger prompt. For more information about the SMP debugger, see the NetWare SMP Software Developer Kit. Supported values: ON, OFF Default: OFF
SMP Memory Protection = value	Enable memory protection. When this parameter is set to ON, the server automatically handles page faults and general protection interrupts and tries to halt the thread causing the problem. The processor continues to operate. However, if the problem occurs during an interrupt, the server starts the SMP debugger. When this parameter is set to OFF, memory protection is disabled. To exit the debugger, type at the debugger prompt. For more information about the SMP debugger, see the NetWare SMP Software Developer Kit. Supported values: ON, OFF Default: OFF

Error Handling Parameters

Error handling parameters control the size of error logs and what happens when logs exceed the specified size.

See Table 18 for descriptions of error handling parameters.

Table 18. Error Handling Parameters

Parameter	Use to
Server Log File State = number	Control what happens when the SYS$LOG.ERR file is larger than the size specified by the Server Log File Overflow Size parameter. Supported values: 0 = Use to leave SYS$LOG.ERR as is. 1 = Use to delete SYS$LOG.ERR. 2 = Use to rename SYS$ERR.LOG. Default: 1 You can set this parameter in the STARTUP.NCF file.
Volume Log File State = number	Control what happens when the VOL$LOG.ERR file is larger than the size specified by the Volume Log File Overflow Size parameter. Supported values: 0 = Use to leave VOL$LOG.ERR as is. 1 = Use to delete VOL$LOG.ERR. 2 = Use to rename VOL$ERR.LOG. Default: 1. You can set this parameter in the STARTUP.NCF file.
Volume TTS Log File State = number	Control what happens when the TTS$LOG.ERR file is larger than the size specified by the Volume TTS Log File Overflow Size parameter. Supported values: 0 = Use to leave TTS$LOG.ERR as is. 1 = Use to delete TTS$LOG.ERR. 2 = Use to rename TTS$ERR.LOG. Default: 1. You can set this parameter in the STARTUP.NCF file.
Server Log File Overflow Size = number	Specify the maximum size of the SYS$LOG.ERR file before the action specified by the Server Log File State parameter occurs. Supported values: 65536 to 4294967295. Default: 4194304. You can set this parameter in STARTUP.NCF.
Volume Log File Overflow Size = number	Specify the maximum size of the VOL$LOG.ERR file before the action specified by the Volume Log File State parameter occurs. Supported values: 65536 to 4294967295. Default: 4194304. You can set this parameter in the STARTUP.NCF file.
Volume TTS Log File Overflow Size = number	Specify the maximum size of the TTS$LOG.ERR file before the action specified by the Volume TTS Log File State parameter occurs. Supported values: 65536 to 4294967295. Default: 4194304. You can set this parameter in the STARTUP.NCF file.
Enable Deadlock Detection = value	Detect deadlocks in code. Supported values: ON, OFF Default: OFF This parameter is used by software developers only.
Auto Restart After Abend Delay Time = number	Specify the amount of time (in minutes) before the server is brought down after an abend, if the Auto Restart After Abend parameter is in effect. Supported values: 2 to 15 minutes. Default: 2 minutes. Regardless of what time is set, the server sends a message every 2 minutes to warn users that the server will be brought down.
Auto Restart After Abend = value	Cause the system to respond automatically to an abend. Supported values: 0 = The system does not automatically respond to the abend. 1 = After an abend, the system determines the source of the abend. Based on findings, the system either keeps the computer running or shuts down the computer and attempts to restart it. 2 = After an abend, the system always shuts down the computer and attempts to restart it. Default: 1 For value 1 or 2 to take effect, the Developer Option parameter (located in the Miscellaneous category of parameters) must also be set to ON. If the server is to be shut down, the system sends a message every 2 minutes to warn all connections. To configure the amount of time the system waits before shutting down the server, use the Auto Restart After Abend Delay Time parameter. After an abend, the screen displays information about the abend. This information is sent to the ABEND.LOG file on the C: drive. Once the server is shut down and restarted, the ABEND.LOG file is transferred to SYS:SYSTEM. Important: Because the server can abend and be restarted automatically, the system administrator should periodically check the ABEND.LOG file or the General Information screen of MONITOR to find out if there have been any abends.

Novell Directory Services Parameters

Novell^® Directory Services (NDS) parameters allow you to do the following:

Control the NDS trace file.
Set time intervals for maintenance processes that reclaim disk space, remove external references, and check the consistency of backlinks.
Set NDS synchronization intervals and restrictions.
Specify the number of NCP retries before timeout.
Mark the status of other servers in the namebase as UP or DOWN.
Specify bindery services contexts.

See Table 19 for descriptions of NDS parameters.

Table 19. Novell Directory Services Parameters

Parameter	Use to
NDS Trace to Screen = ON/OFF	Enable the NDS trace screen; this displays information about NDS events on the monitor. Supported values: ON, OFF. Default: OFF.
NDS Trace to File = ON/OFF	Send messages about NDS events to the NDS trace file on the SYS: volume. The default file is SYSTEM\DSTRACE.DBG. Supported values: ON, OFF. Default: OFF. The file path and name can be changed with the NDS Trace Filename parameter. The file is circular; it grows to a maximum length of approximately 500 KB and then starts to overwrite itself at the beginning of the file. If this parameter is set to ON, the trace information is also scrolled on the screen.
NDS Trace Filename = path\name	Set the path and name of the NDS trace file on SYS: volume. Maximum length: 254.Default: SYSTEM\DSTRACE.DBG.
NDS Client NCP Retries = number	Specify the number of NCP retries before the NDS client times out a connection. Supported values: 1 to 20. Default: 3. Lower settings are useful for smaller networks or those in which cables are disconnected frequently. Higher settings are useful for larger networks with heavy traffic. A setting of 4, 5, or 6 should be sufficient for large networks.
NDS External Reference Life Span = number in hours	Specify the number of hours unused external references are allowed to exist before being removed. Supported values: 1 to 384 hours. Default: 192. External references are local IDs assigned to users when they access other servers. When users no longer have access, the external references should be removed.
NDS Inactivity Synchronization Interval = number in minutes	Specify the maximum elapsed time between exhaustive synchronization checks. As soon as you change this value, the system executes the synchronization check. Synchronization checks then recur at the specified interval. Supported values: 2 to 1440 minutes. Default: 30. If the system has replicas across a WAN link, this value should be set as high as 240 minutes (4 hours) to reduce WAN traffic.
NDS Synchronization Restrictions = OFF/ON,version number list	Specify which versions of Novell Directory Services the server can synchronize with. Supported values: OFF, ON, list of version numbers.Maximum length of version number list: 131 characters. Default: OFF. To determine what version is currently loaded on a server, type MODULES at the server prompt. The Novell Directory Services version number is displayed under the heading DS.NLM. If this parameter is set to OFF, the server synchronizes with all versions available. If this parameter is set to ON, the server synchronizes only with those versions specified as parameters to the ON value. Example: ON,420,421
NDS Servers Status = value	Mark the status of all server objects in the local namebase as UP or DOWN. Supported values: UP, DOWN Use this parameter to reset the status of all the servers if the status of one server isn't accurately recognized by the system. For example, if a server is up but the system recognizes it as down, set this parameter to mark all servers as up. Subsequently, the system would reassess the status of all servers and change the status to down for those servers that were truly down.
NDS Janitor Interval = number in minutes	Set the interval in minutes at which the janitor process is executed. The janitor process is executed as soon as you change this value and then recurs at the specified interval. Supported values: 1 to 10080 minutes. Default: 60. The janitor process cleans up unused records, reclaims disk space, and purges objects flagged for deletion.
NDS Backlink Interval = number in minutes	Set the interval in minutes at which backlink consistency checking is performed. Backlink consistency checking is executed as soon as you change this value. It then recurs at the specified interval. Supported values: 2 to 10080 minutes. Default: 780. A backlink indicates that an object in a replica has an ID on a server where the replica doesn't exist. This process creates needed backlinks and deletes unnecessary ones.
NDS Trace File Length to Zero = OFF	Delete the contents of the trace file. This parameter does not delete the file itself. As soon as the file is cleared, the parameter resets to OFF. Supported values: ON, OFF. Default: OFF. To use this parameter, you must also set the NDS trace to file parameter to ON, because the trace file must be open for the system to delete its contents.
Check Equivalent to Me = value	Enforce checking of the Equivalent To Me attribute on authentication. Supported values: ON, OFF. Default: OFF Set this parameter to ON for enhanced security. If this parameter is set to ON, DSREPAIR must be used to synchronize the Equivalence attribute and the Equivalent To Me attribute. Setting this parameter to ON might adversely affect communication performance.
Bindery Context = context;context	Specify one or more containers to be used by Novell Directory Services when it provides bindery services. Maximum: 2047 characters. Up to 16 contexts. Multiple contexts are separated by semicolons. To set multiple contexts, you must have a replica of the container you specify in the context on the same partition. Example: SET BINDERY CONTEXT = OU=SALES_LA.OU=SALES. O=NOVELL_US;OU=ACCOUNTING.O=NOVELL This parameter can be set in the STARTUP.NCF file.

SFT III Parameters

A NetWare 4.11 SFT III^TM system provides additional SET parameters to help you test and customize your mirrored server environment.

Some SET parameters affect only one engine (the MSEngine or the IOEngine). A few parameters can be set in both engines (see SFT III Parameters Settable in Both Engines).

You must execute SET parameters in the correct engine. To toggle to the appropriate console display (IOEngine or MSEngine), use the <Alt>+<Esc> keys before typing a SET command.

The NetWare 4.11 SET parameters listed in previous sections can also be used with a NetWare SFT III system.

NOTE: Changing one SFT III SET parameter may affect other parameters. As a general rule, don't change more than one parameter at a time.

MSEngine Parameters Only Settable at Startup

The following MSEngine SET parameters are settable only at startup:

Minimum Packet Receive Buffers

Cache Buffer Size

Maximum Subdirectory Tree Depth

Auto TTS Backout Flag

Concurrent Remirror Requests

To change the default for these parameters, put the SET parameter in the MSSTART.NCF file.

NOTE: If you change the Minimum Packet Receive Buffers parameter in the MSSTART.NCF file, you must also put the same SET parameter in the IOSTART.NCF file.

Changes to the MSSTART.NCF file do not take effect until after you bring down both servers and reactivate them.

IOEngine Parameters Only Settable at Startup

The following IOEngine SET parameters are settable only at startup:

Minimum Packet Receive Buffers

Auto Register Memory Above 16 Megabytes

To change the default for these parameters, include the SET parameter in the IOSTART.NCF file and restart that server.

SFT III Parameters Settable in Both Engines

The following parameters can be set in either the IOEngine or the MSEngine, or both engines. In most cases, the parameter setting in the IOEngine and the MSEngine should match.

Maximum Packet Receive Buffers

Minimum Packet Receive Buffers

Allow Invalid Pointers

Read Fault Notification

Read Fault Emulation

Write Fault Notification

Write Fault Emulation

Sound Bell for Alerts

Replace Console Prompt With Server Name

Alert Message Nodes

Worker Thread Execute in a Row Count

Halt System on Invalid Parameters

Upgrade Low Priority Threads

Display Relinquish Control Alerts

Display Incomplete IPX Packet Alerts

Display Old API Names

Related SFT III Wait Time Parameters

Six SFT III SET parameters are closely related:

SFT3 Error Wait Time (default: 3 seconds)

MSL Error Wait Time (default: 0.8 second)

Secondary Take Over Wait Time (default: 1 second)

IPX Internet Down Wait Time (default: 4 seconds)

MSL Deadlock Wait Time (default: 5 seconds)

Check LAN Extra Wait Time (default: 0 seconds + 5 seconds)

Because their wait time settings affect server switchover, you should understand the interrelationships of these parameters before you change any of their default settings.

The SFT3 Error Wait Time automatically adjusts the time of the other five wait time parameters. This parameter should be adjusted only for systems experiencing multiple timeouts.
Of the related wait time values, the MSL Error Wait Time should be the shortest. It should be shorter by 1 second than the Secondary Take Over Wait Time.
Both the MSL Error Wait Time and the Secondary Take Over Wait Time should be shorter than the IPX Internet Down Wait Time.
For hardware failures, you need to find out if the Mirrored Server Link^TM (MSL) is down (so the secondary server can shut down) before you start checking the LAN hardware. Therefore, the MSL Error Wait Time also should be shorter than the Check LAN Extra Wait Time.
For software failures, you need to find out if the LAN is down before you find out if the MSL is down. Otherwise, both servers could fail at the same time. Therefore, the IPX Internet Down Wait Time should be shorter than the MSL Deadlock Wait Time.

Parameter Descriptions

SFT III SET parameters are described in the following tables:

MSEngine Communication Parameters, Table 20

MSEngine Miscellaneous Parameters (SFT III), Table 21

IOEngine Communication Parameters, Table 22

IOEngine Memory Parameters, Table 23

IOEngine Mirrored Server Parameters (SFT III), Table 24

IOEngine Mirrored Servers Error Recovery Options Parameters (SFT III), Table 25

IOEngine Mirrored Servers Test Options Parameters (SFT III), Table 26

IOEngine Error Handling Parameters (SFT III), Table 27

Table 20. MSEngine Communication Parameters (SFT III)

Parameter	Use to
Clear Extra ECB Space = number	Specify whether to fill the leftover space in a receive event control block (ECB) with zeroes to prevent abends caused by undersized packets. Supported values: 0 to 2. Default: 1. 0 = Don't fill the leftover space in the ECB with zeroes. 1 = Fill up to 64 extra bytes in the ECB with zeroes. 2 = Fill the rest of the ECB with zeroes. To improve server performance, set this parameter to 0. To prevent recurring MSEngine outputs different errors, set it to 2.

Parameter

Use to

Clear Extra ECB Space = number

Specify whether to fill the leftover space in a receive event control block (ECB) with zeroes to prevent abends caused by undersized packets.

Supported values: 0 to 2.
Default: 1.

0 = Don't fill the leftover space in the ECB with zeroes.
1 = Fill up to 64 extra bytes in the ECB with zeroes.
2 = Fill the rest of the ECB with zeroes.

To improve server performance, set this parameter to 0. To prevent recurring MSEngine outputs different errors, set it to 2.

Table 21. MSEngine Miscellaneous Parameters (SFT III)

Parameter	Use to
Notify All Users Of Mirrored Server Synchronization = value	Specify whether to broadcast a message to all logged-in users when the mirrored servers begin synchronizing. If the SFT III server:notifying users of synchronizationserver has more than 64 MB of RAM, or if server synchronization takes more than 5 seconds, set this parameter to ON. Supported values: ON, OFF Default: OFF.
Server Failure Notification Name = name	Specify the user or group name to notify with a broadcast message in case of a server or disk SFT III server:failure, notifying about;Failure:notifying SFT III users aboutfailure or disk-out-of-sync condition. To send the broadcast to all logged-in users, use group EVERYONE. Note: If you use an invalid user or group name, the broadcast message will fail. Supported values: any valid user or group name. Default: no group or user name.
MSEngine Use Primary Server For DOS I/O for MSEngine, setting;MSEngine:DOS I/O, setting;Floppy drive input to MSEngine, settingDOS I/O = value	Specify which server to use for DOS input to the MSEngine. To copy data from the secondary server's DOS partition or floppy drive, set this parameter to OFF. Supported values: ON, OFF. Default: ON.

Parameter

Use to

Notify All Users Of Mirrored Server Synchronization = value

Specify whether to broadcast a message to all logged-in users when the mirrored servers begin synchronizing. If the SFT III server:notifying users of synchronizationserver has more than 64 MB of RAM, or if server synchronization takes more than 5 seconds, set this parameter to ON.

Supported values: ON, OFF
Default: OFF.

Server Failure Notification Name = name

Specify the user or group name to notify with a broadcast message in case of a server or disk SFT III server:failure, notifying about;Failure:notifying SFT III users aboutfailure or disk-out-of-sync condition. To send the broadcast to all logged-in users, use group EVERYONE.

Note: If you use an invalid user or group name, the broadcast message will fail.

Supported values: any valid user or group name.
Default: no group or user name.

MSEngine Use Primary Server For DOS I/O for MSEngine, setting;MSEngine:DOS I/O, setting;Floppy drive input to MSEngine, settingDOS I/O = value

Specify which server to use for DOS input to the MSEngine. To copy data from the secondary server's DOS partition or floppy drive, set this parameter to OFF.

Supported values: ON, OFF.
Default: ON.

Table 22. IOEngine Communication Parameters (SFT III)

Parameter	Use to
Check LAN Option = number	Check the functionality of the LAN boards in the server and prevent loss of service to clients by providing early warning of LAN board problems. Supported values: 0 to 2. 0 = Don't check the server LAN boards. 1 = If a LAN board problem is detected, notify the server console but don't restart the primary server. 2 = If the secondary server's LAN boards are more functional, restart the primary server. Default: 2. Note: The secondary server uses the same value for this parameter as the primary server.
Check LAN Extra Wait Time = time	Specify the additional time the server waits (5 seconds plus the value of this parameter) before taking the action specified in the Check LAN Option parameter. If traffic is heavy on your network, or if MAUs need more time to reset, increase this setting. Supported values: 0 seconds to 59.3 seconds. Default: 0.
Use Diagnostic Responder to Validate LAN Functionality = value	Specify whether to broadcast an IPX diagnostic request to verify that LAN boards are functional. If the SFT server is running standalone, or if the system isn't detecting bad boards, set this parameter to ON. Supported values: ON, OFF. If you have a router that replicates broadcast, don't set this parameter to ON or a flood of network traffic will result. If your SFT III server is the only server on the network, set this parameter to ON. Default: OFF.

Parameter

Use to

Check LAN Option = number

Check the functionality of the LAN boards in the server and prevent loss of service to clients by providing early warning of LAN board problems.

Supported values: 0 to 2.
0 = Don't check the server LAN boards.
1 = If a LAN board problem is detected, notify the server console but don't restart the primary server.
2 = If the secondary server's LAN boards are more functional, restart the primary server.

Default: 2.

Note: The secondary server uses the same value for this parameter as the primary server.

Check LAN Extra Wait Time = time

Specify the additional time the server waits (5 seconds plus the value of this parameter) before taking the action specified in the Check LAN Option parameter. If traffic is heavy on your network, or if MAUs need more time to reset, increase this setting.

Supported values: 0 seconds to 59.3 seconds.
Default: 0.

Use Diagnostic Responder to Validate LAN Functionality = value

Specify whether to broadcast an IPX diagnostic request to verify that LAN boards are functional. If the SFT server is running standalone, or if the system isn't detecting bad boards, set this parameter to ON.

Supported values: ON, OFF.

If you have a router that replicates broadcast, don't set this parameter to ON or a flood of network traffic will result.

If your SFT III server is the only server on the network, set this parameter to ON.

Default: OFF.

Table 23. IOEngine Memory Parameters (SFT III)

Parameter	Use to
Borrow Short Term Memory Ahead Amount = number	Specify the amount of memory the system keeps available for processes that temporarily need extra memory. If you get an insufficient short-term memory error while running a module, set this parameter to a higher value and reload the module. Supported values: 0 to 100000 bytes. Default: 32768 bytes.

Parameter

Use to

Borrow Short Term Memory Ahead Amount = number

Specify the amount of memory the system keeps available for processes that temporarily need extra memory.

If you get an insufficient short-term memory error while running a module, set this parameter to a higher value and reload the module.

Supported values: 0 to 100000 bytes.
Default: 32768 bytes.

Table 24. IOEngine Mirrored Server Parameters (SFT III)

Parameter	Use to
SFT3 Error Wait Time = time	Adjust all SFT III wait time parameters. Supported values: 0.5 second to 10 seconds. Default: 3 seconds. Change this parameter only if the systems are experiencing multiple timeouts. Note: Multiple timeouts might indicate a problem in the system.
Secondary Take Over Wait Time= time	Specify the number of seconds that the secondary server waits for an I'm alive packet from the primary server before taking over as the new primary server. (For more information, see I'm Alive packet in Concepts.) Supported values: 0.5 second to 20 seconds. Default: 1 second. Set this time to be longer than the MSL Error Wait Time. (For more about related SET parameters, see Related SFT III Wait Time Parameters) If your network is connected to a busy internetwork and packets take longer to travel across it, increase the value of this parameter. Important: If the message This server should not have become the primary server because the primary server is still alive appears, increase the Secondary Take Over Wait Time by 0.5 second or more. However, setting this parameter too high may cause workstations to time out while the servers are determining if a switchover is needed.
Display Mirrored Server Too Many Hops Away Message= value	Specify whether to display a warning message if the hops between the mirrored servers exceed the Maximum Pseudo Hop Count parameter. Supported values: ON, OFF. Default: ON.
Maximum Pseudo Hop Count= number	Specify the maximum number of hops that the primary server will advertise as its pseudo hop count. (For more information, see Pseudo hop count in Concepts.) Supported values: 1 to 8. Default: 4. If your SFT III servers are installed on different network segments, with several hops between them, you may need to specify a higher Maximum Pseudo Hop Count. Important: Increasing the pseudo hop count reduces the number of hops available to stations on the internetwork. The total hop count (the pseudo hop count plus the actual number of hops from the router to the MSEngine) between a station and server cannot exceed 16. If the actual number of hops between mirrored servers is greater than the value specified by this parameter, the primary server advertises only the Maximum Pseudo Hop Count.
Enable Pseudo Hop Count= value	Specify whether the primary server advertises an artificially high hop count when it is mirrored to a secondary server on a different network segment. (For more information, see Pseudo hop count in Concepts.) Supported values: ON, OFF. Default: ON.
New End Address For Unclaimed Memory Block= number	Define the end of the MSEngine's memory range. The IOEngine claims any memory blocks numbered after the New End Address. If your servers have unequal amounts of RAM, use this parameter to align the memory of the larger-RAM server with the memory of the smaller-RAM server. (See Responding to Secondary Server Is Missing RAM Messages in Appendix C of Supervising the Network.) Note: Reducing the MSEngine's memory too much (by setting a low New End Address number) might prevent volumes from mounting. Supported values: 2097152 to 1073741824 bytes. Default: highest memory installed in the server.
New Start Address For Unclaimed Memory Block= number	Define the start of the MSEngine's memory range. The IOEngine claims any memory blocks that fall before the New Start Address. Supported values: 2097152 to 1073741824 bytes. Default: 5242880 bytes. If the IOEngine is frequently borrowing memory from the MSEngine, set the New Start Address to a higher number to give the IOEngine more memory.
MSL Error Wait Time= time	Specify the number of seconds that the MSL driver waits for an acknowledgment of a sent packet before signaling that the other server or the MSL has failed. Supported values: 0.2 second to 4.4 seconds. Default: 0.8 second. If your servers are very busy (CPU utilization over 60%), use this parameter to give them more time to communicate. The value of this parameter should be less than the Secondary Take Over Wait Time parameter. Note: Changing the default on this parameter makes it take longer to determine that the other server has failed.
Comprehensive MSEngine Synchronization Check= value	Specify whether to do a comprehensive verification that both MSEngine outputs are the same. Supported values: ON, OFF. Default: OFF. Note: The OFF setting provides a faster, simpler check of MSEngine outputs. Though it reduces synchronization time, the OFF setting may increase the risk of undetected synchronization errors.
IPX Internet Down Wait Time= time	Specify how many seconds the server waits before concluding that the IPX internetwork is not delivering packets. Supported values: 0.5 second to 59.3 seconds. Default: 4 seconds. If you have a busy network or hardware reliability problems, use this parameter to allow more time for the server to get IPX packets. The value of this parameter should be more than the Secondary Take Over Wait Time, but less than the MSL Deadlock Wait Time.
Display IPX Route to Other Server= value	Specify whether to display the IPX route to the other server. This parameter is useful for troubleshooting internetwork problems. Supported values: ON, OFF. Default: OFF. The IPX route can show how efficient the network routing is by displaying the node numbers, the addresses, and the number of hops to the other server.
MSL Deadlock Wait Time= time	Specify how many seconds the server waits before concluding that the MSL driver is deadlocked (receive packets are being held off indefinitely). Supported values: 1 second to 59.3 seconds. Default: 5 seconds. If you have very busy servers, use this parameter to allow more time for the two servers to communicate. This setting times 4 is the time-out value that determines when the server exercises the MSL Send Blocked Recovery Option. Note: If you increase the IPX Internet Down Wait Time, you must also increase the MSL Deadlock Wait Time. Otherwise, if the MSL is deadlocked, the IPX connection may time out before the deadlock is detected. It is best if the MSL Deadlock Wait Time is at least one second longer than the IPX Internet Down Wait Time.
Extra MSL Checking= value	Specify whether to do extra checking of MSL messages to ensure data integrity. Supported values: ON, OFF. Default: ON. Note: Setting this parameter to OFF may improve performance, but it increases the risk of undetected MSL errors.
IOEngine Error Log Use DOS= value	Specify whether to log system alerts to the default DOS drive if volume SYS: is not mounted. Supported values: ON, OFF. Default: ON. When the servers are resynchronized, the DOS error log is appended to the IO$LOG.ERR file on volume SYS:.
Always Down Server When Power Fails= value	Specify whether the MSEngine is shut down when a power failure is detected. Supported parameters: ON, OFF. Default: ON. Set this parameter to OFF to allow for continued service when both SFT III servers are on separate UPS devices. If the servers are fully synchronized and mirrored, and this parameter is set to OFF, the UPS halts only the IOEngine (rather than shutting down the MSEngine) when power fails. If only one of your SFT III servers has a UPS installed, leave this parameter set to ON.
Turbo Memory Sync=value	Change how the memory is synchronized on the server. Supported values: 0 = Disable. 1 = Enable and clear the memory. 2 = Enable, but don't clear the memory. Default: 2. The default gives you the best performance. Use the other methods only when instructed in troubleshooting.

WARNING: Don't change the settings for the parameters in Table 25 unless you are running SFT III in a testing environment.

Table 25. IOEngine Mirrored Servers Error Recovery Options Parameters (SFTIII)

Parameter	Use to
Secondary Server MSL Send Blocked Recovery Option= option	Specify the recovery strategy for the secondary server if it detects that the MSL driver is not sending data to the other server at the correct rate. Supported options: 0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server. Default: 2.
Primary Server MSL Send Blocked Recovery Option= option	Specify the recovery strategy for the primary server if it detects that the MSL driver is not sending data to the other server at the correct rate. Supported options: 0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server. Default: 2.
MSEngine Abend And Processor Exception Recovery Option= option	Specify the recovery strategy for the server that detects MSEngine software abends and MSEngine hardware exceptions. Supported options:0 = Halt the server. 1 = Restart the server. Default: 1.
Always Halt Secondary If Sync Error= value	Specify whether to halt the secondary server every time an error is detected during mirrored server synchronization. Supported values: ON, OFF. Default: OFF.
IOEngine Abend And Processor Exception Recovery Option= option	Specify the recovery strategy for the server that detects IOEngine software abends and IOEngine hardware exceptions. Supported options: 0 = Halt the server. 1 = Restart the server. Default: 1.
Machine Check Recovery Option= option	Specify the recovery strategy for the server that detects hardware errors (other than memory parity errors). Supported options:0 = Halt the server. 1 = Restart the server. Default: 1.
Memory Parity Error Recovery Option= option	Specify the recovery strategy for the server that detects memory parity errors. Supported options: 0 = Halt the server. 1 = Restart the server. Default: 1.
Secondary Server MSL Hardware Failure Recovery Option= option	Specify the recovery strategy for the secondary server detecting an MSL hardware failure. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server using the same MSL. 3 = Restart the secondary server using the alternate MSL. Default: 2. The secondary server performs the set option unless the primary server has failed. If the primary server has failed, the secondary server becomes the new primary server.
Primary Server MSL Hardware Failure Recovery Option= option	Specify the recovery strategy for the primary server detecting an MSL hardware failure. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server using the same MSL. 3 = Restart the secondary server using the alternate MSL. Default: 2.
MSEngine Outputs Different Recovery Option= option	Specify the recovery strategy for the secondary server detecting that its MSEngine outputs are different from the primary server's MSEngine outputs. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server Default: 0.
Secondary Server MSL Consistency Error Recovery Option= option	Specify the recovery strategy for the secondary server detecting communications consistency errors, such as checksum errors, invalid sequence number, or invalid packet type. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server using the same MSL. 3 = Restart the secondary server using the alternate MSL. Default: 2. The secondary server performs the set option unless the primary server has failed. If the primary server has failed, the secondary server becomes the new primary server.
Primary Server MSL Consistency Error Recovery Option = option	Specify the recovery strategy for the primary server detecting communications consistency errors, such as checksum errors, invalid sequence number, or invalid packet type. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server using the same MSL. 3 = Restart the secondary server using the alternate MSL. Default: 2.
Secondary Server MSL Deadlock Recovery Option = option	Specify the recovery strategy for the secondary server detecting an MSL communications delivery deadlock. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server Default: 2.
Primary Server MSL Deadlock Recovery Option = option	Specify the recovery strategy for the primary server detecting an MSL communications delivery deadlock. Supported options:0 = Halt the secondary server. 1 = Halt the primary and secondary servers. 2 = Restart the secondary server Default: 2.

WARNING: Don't change the settings for the parameters in Table 26 unless you are running SFT III in a testing environment.

Table 26. IOEngine Mirrored Servers Test Options Parameters (SFTIII)

Parameter	Use to
Test Mode = option	Test server switchover and recovery with four failure scenarios. Supported options: 0 = Don't initiate Test Mode. 1 = Enable a simple halt/restart server test. 2 = Generate MSL errors. 3 = Generate system errors. 4 = Generate errors of types 1, 2, and 3. Default: 0. Note: When you change the Test Mode setting back to 0, all settings for Mirrored Servers Error Recovery Options return to their defaults Suggestion: Because Test Mode options apply only to the primary server, you can set different test options in each server's IOSTART.NCF file. For best performance, however, set the same test options in each server's IOSTART.NCF file.
Stop On Server Test Unexpected Error = value	Specify whether to stop both servers if an unexpected error (not generated by the Test Mode) occurs. Supported values: ON, OFF. Default: ON.
Restart Minimum Delay Amount = time	Specify how many seconds the server waits before executing a restart in Test Mode. Supported times: 0 seconds to 23 hours 43 minutes 40.1 seconds. Default: 10 seconds. This setting is added to the random number generated by the Restart Maximum Random Delay Amount parameter to determine the actual delay amount. If you notice several communications deadlocks or initialization failures while running your servers in Test Mode, use this parameter to allow more time for the server to finish switchover before restarting.
Server Test Minimum Delay Amount = time	Specify how many seconds the server waits before initiating the Test Mode option. Supported times: 0 seconds to 23 hours 43 minutes 40.1 seconds. Default: 3 minutes. This setting is added to the random number generated by the Server Test Maximum Random Delay Amount parameter to determine the actual delay amount. Use this parameter to reduce the number of workstation pauses caused by frequent server resynchronization while running in Server Test Mode.
Restart Maximum Random Delay Amount = time	Specify the maximum random number that the server generates to add to the Restart Minimum Delay Amount. The resulting sum is the number of seconds the server waits before executing a restart in Test Mode. Supported times: 0 seconds to 59 minutes 19.2 seconds. Default: 0 seconds.
Server Test Maximum Random Delay Amount = time	Specify the maximum random number that the server generates to add to the Server Test Minimum Delay Amount. The resulting sum is the number of seconds the server waits before initiating the Test Mode option. Supported times: 0 seconds to 59 minutes 19.2 seconds. Default: 19.8 seconds.

Table 27. IOEngine Error Handling Parameters (SFT III)

Parameter	Use to
Status Dump File State = number	Specify the action to take if the MSSTATUS.DMP file size exceeds the size limit. Supported values:0 = Take no action if the file grows too large. 1 = Delete the log file if it grows too large. 2 = Rename the log file if it grows too large. Default: 1.
IOEngine Error Log File State = number	Specify the action to take if the IO$LOG.ERR file size exceeds the size limit. Supported values:0 = Take no action if the file grows too large. 1 = Delete the log file if it grows too large. 2 = Rename the log file if it grows too large. Default: 1.
Status Dump File Overflow Size = number	Specify the size limit for the MSSTATUS.DMP file. Supported values: 65536 to 4294967295 bytes. Default: 4194304 bytes.
IOEngine Error Log File Overflow Size = number	Specify the size limit for the IO$LOG.ERR file. Supported values: 65536 to 4294967295 bytes. Default: 4194304 bytes.

Additional Information

Topic	See
Using SERVMAN to change set parameters	SERVMAN
Controlling file compression	Using SET to Control File Compression in Chapter7 of Supervising the Network.
Improving server performance	Improving Server Performance in Chapter 7 of Supervising the Network.
Editing .NCF files	Creating or Editing a Server Batch (.NCF) File in Chapter 7 of Supervising the Network.
Time synchronization and the TIMESYNC.CFG file	Maintaining Network Time Synchronization in Chapter 4 of Supervising the Network.

SET

Purpose

Syntax

Displaying and Changing Current Settings

Memory Parameters

File Caching Parameters

Directory Caching Parameters

Allocation of Directory Cache Buffers

How Directory Caching and File Caching Work Together

File System Parameters

Lock Parameters

Transaction Tracking Parameters

Disk Parameters

Time Synchronization Parameters

NCP Parameters

Miscellaneous Parameters

Error Handling Parameters

Novell Directory Services Parameters

SFT III Parameters

IOEngine Parameters Only Settable at Startup

SFT III Parameters Settable in Both Engines

Additional Information