In the NETLOGON section, you specify parameters related to network logon. The NetLogon service is started automatically at server startup.

Table A-2 NETLOGON Keywords

Keyword	Description	Setting	Default Setting
maxclisess =n	Specifies the number of links for internal communication that this server can initiate. This represents the maximum number of domains that this domain can trust, plus one (number of trusted domains plus 1).	Minimum: 5 Maximum: 128	32
maxsrvsess =n	Specifies the number of links used for internal communication that this server can accept. This number must include the number of domains that trust this domain, the number of backup domain controllers in this domain, and the number of Windows NT workstations in this domain (trusting domains + BDCs + Windows NT workstations).	Minimum: 5 Maximum: unlimited	200
pulse =n	Specifies the number of seconds that the primary domain controller waits before sending update notices to each backup domain controller and member server.	60-3600 seconds	300 seconds 5 minutes
randomize =n	Specifies the number of seconds that a backup domain controller randomizes a request to get updates after receiving an update notice from the primary domain controller. This keyword decreases the odds of servers in the same domain requesting an update from the primary domain controller at the same time.	5-120 seconds	30 seconds
scripts =path	Specifies the location of logon scripts.		If you do not specify this keyword, the login scripts are assumed to be stored at:
	PWRK$LMROOT:[LANMAN.REPL.IMPORT.SCRIPTS]
update=YES/NO	Controls synchronization of the user accounts database with the master database on the primary domain controller when the server starts. This keyword applies only to a backup domain controller and is ignored by the primary domain controller.	YES or NO	NO (do not synchronize on startup)

A.3.5 NODE_servername Section

Table A-3 NODE_ servername Keywords

Keyword	Description	Setting	Default Setting
autoshare= device=sharename
	Specifies a synonym for the autoshare name created by default for an OpenVMS disk device. The value for this keyword is a list of OpenVMS device names (or volume labels) and share name synonym to which each device maps.	All OpenVMS disk devices are automatically shared, and share names are based on the volume label of each disk device. (See Section A.4, Defining Autoshares).	NULL
noautoshare =(device[,...])
	Specifies a disk device or list of devices that should not be automatically shared when the server starts. Autosharing DFS devices is not recommended.	Up to 512 characters, including commas	dad, _dfs
listenname= servername
	Specifies the name of the server on the network; up to 15 characters. Using this keyword, you enable users to connect to a server using a different server name. Caution: Do not change the listenname by editing the LANMAN.INI file directly. To change the listenname, use the PWRK$CONFIG.COM configuration procedure.	Up to 15 characters	The server node name
srvservices =list	Specifies the services that start automatically when the server is started. Because services are started in the order they appear in the srvservices entry, you must ensure that "NetLogon" appears before any services that require the NetLogon service. The Browser service is not controlled by this keyword. It is started automatically when the Server service starts.	alerter, netlogon, browser	alerter, netlogon

A.3.6 SERVER Section

Table A-4 Server Keywords

Keyword	Description	Setting	Default Setting
accessalert =n	Specifies the number of resource access violations that can occur before the server sends an alert to the alertnames list.	0 to unlimited	5
alertnames =list	Specifies a list of the Advanced Server user accounts to receive administrative alerts. To receive alerts, a client workstation must be running the Messenger service. The Messenger service is not supported on OpenVMS servers.		None
autodisconnect =n	Specifies the interval, in minutes, that the server waits before dropping the virtual circuit to an inactive client.	0 to unlimited	0 (no automatic disconnect)
erroralert =n	Specifies the number of errors that can occur before the server sends an alert to the alertnames list.	0 to unlimited	5
logonalert =n	Specifies the number of logon violations that can occur before the server sends an alert to the alertnames list.	0 to unlimited	5
maxapplog= n	Specifies the maximum size, in kilobytes, of the Application event log file.	0 to unlimited	100 Kbytes
maxauditlog= n	Specifies the maximum size, in kilobytes, of the Security event log file.	0 to unlimited	100 Kbytes
maxclients= n	Specifies the maximum number of clients.	1 to unlimited	50
maxerrlog= n	Specifies the maximum size, in kilobytes, of the System event log file.	0 to unlimited	100 Kbytes
srvannounce =n	Specifies the number of seconds at which the server announces its presence to the network. This keyword has effect only if srvhidden=NO.	1 to unlimited	180 seconds
srvcomment =text	Specifies the descriptive comment that the server sends when it announces its presence to the network.	Up to 48 characters, including spaces	PATHWORKS V6.0B for OpenVMS (Advanced Server)
srvhidden=YES/NO	Specifies whether the server is hidden on the network. If the server is not hidden, it announces its presence at the interval set by srvannounce and can be viewed using the ADMINISTER SHOW COMPUTERS command.	YES or NO	NO (visible)
srvservices =list	Specifies the services that start automatically when the server is started. Because services are started in the order they appear in the srvservices entry, you must ensure that NetLogon appears before any services that require it. The Browser service is not controlled by this keyword. It is started when the Server service is started.	alerter netlogon, browser	alerter, netlogon
userpath =path	Specifies the OpenVMS system directory on the server to be used as a default parent directory for home directories for new user accounts.	Up to 255 characters	If you do not specify this keyword, the path is assumed to be:
	PWRK$LMROOT:[LANMAN.ACCOUNTS.USERDIRS

A.3.7 VMSSERVER Section

Table A-5 VMSSERVER Keywords

Keyword	Description	Setting	Default Setting
autoshare= devn=sharename
	Specifies a synonym for the autoshare name for an OpenVMS disk device. The value for this keyword is a list of OpenVMS device names (or volume labels) and the share name for each device. (See Section A.4.)	All OpenVMS disk devices are automatically shared, and share names are based on the volume label of each disk device
hostmapusevmsnames=YES/NO
	Checks to see if the PATHWORKS Advanced Server user's name matches an OpenVMS user account name. Explicit host mapping is checked and used first. If host mapping has not been specified, the software searches for a matching OpenVMS user name. (See Section 3.3.12.)	YES or NO	YES
hostmapdomains =(domainname,...)
	This parameter is used to perform external authentication on a network user name located in a domain other than the one where the server is located. Checks to see if the user's domain name matches one of the domains listed, where the PATHWORKS Advanced Server user name matches an OpenVMS user account name. Affects hostmapusevmsnames translations.	List of domains used for OpenVMS host mapping	NULL. The server's domain name is assumed.
hostmapdefault =text	Used when no other host mapping definitions apply.	ADMINISTRATOR, PWRK$DEFAULT, GUEST, or REJECT	PWRK$DEFAULT
noautoshare=( device[,...device])
	Specifies a disk device or list of devices that should not be automatically shared when the server starts. DFS disk devices are not automatically shared. Autosharing DFS devices is not recommended.	Up to 512 characters	dad, _dfs
pwrkalias= text	Specifies the PATHWORKS cluster alias. Caution: Do not change pwrkalias by editing the LANMAN.INI file directly. To change the PATHWORKS cluster alias, use the PWRK$CONFIG.COM configuration procedure.	Cluster alias name	OpenVMS cluster alias

A.3.8 WORKSTATION Section

Table A-6 WORKSTATION Keywords

Keyword	Meaning	Setting	Default Setting
domain =domainname	Specifies the name of the domain that includes this server. Caution: Do not change the domain name by editing the LANMAN.INI file directly. To change the domain name, use the PWRK$CONFIG.COM configuration procedure. Changing the domain name reinitializes the server security database.	Up to 15 characters	LANGROUP

A.4 Defining Autoshares

The PATHWORKS Advanced Server lets you map autoshare names through entries in the LANMAN.INI file. This feature is useful if:

• You have a disk device whose volume label exceeds the 11-character limit.
• You want to map a server device to a single letter to accommodate the DOS disk device-naming convention.
• You do not want to autoshare some devices.

You can use the AUTOSHARE and NOAUTOSHARE keywords in the VMSSERVER section of the server's LANMAN.INI file to specify a list of autoshare names for the server to create, in addition to the autoshares that the server creates automatically, and to specify the names of devices that you do not want to autoshare. You must restart the server to activate these changes.

If you are running PATHWORKS Advanced Server in an OpenVMS cluster environment, you can specify the AUTOSHARE and NOAUTOSHARE keywords in the node-specific section of the LANMAN.INI file called NODE_servername. The devices you specify in the node- specific section remain local to that server node; they are not served to other OpenVMS cluster members. Keywords specified in the VMSSERVER section override identical keywords in the NODE_servername section. See Section A.4.3 for more information.

The AUTOSHARE and NOAUTOSHARE keywords function as follows:

• If a volume label is specified with the NOAUTOSHARE keyword, that device is not shared, but it is still available by its logical name.
• If a volume label is specified with the AUTOSHARE keyword, that device is shared and mapped to the specified autoshare name.
• If a volume is not specified, PATHWORKS Advanced Server creates an autoshare by default, so long as the volume label does not exceed the 11- character name limit.

The AUTOSHARE keyword in the LANMAN.INI file specifies an alias for the autoshare name created by default for an OpenVMS disk device. PATHWORKS Advanced Server creates an autoshare for each mounted OpenVMS disk device when the server starts. To create a more meaningful share name or to map the device name to a DOS format, use the AUTOSHARE keyword in the LANMAN.INI file.

The format is as follows:

AUTOSHARE=(devname_1=sharename_1,...,devname _n=sharename_n)

The share name cannot exceed 11 characters. Do not append a dollar sign ($) to the device name; the PATHWORKS Advanced Server does this automatically.

For example, Table 4-4, Sample Autoshare Names, shows physical device names and volume labels for disk devices mounted on node DOT and the autoshare names that PATHWORKS Advanced Server creates by default.

The following example shows an AUTOSHARE keyword in the VMSSERVER section of the LANMAN.INI file:

AUTOSHARE = DOT$DUA1=USERS_1,DOT$DUA2=M,DOT$DUA3=WORK5

If you connect to an autoshare, you access the root directory of the disk device. For example, if you connect to the share USERS_1$, you access DOT$DUA1:[000000]. The AUTOSHARE keyword directs PATHWORKS Advanced Server to create an autoshare named M$. When a user displays a list of available devices (for example, to create a shared directory), the device M: is listed.

As shown in Table 4-4, Sample Autoshare Names, PATHWORKS Advanced Server did not create an autoshare for the device DOT$DUA3:, because the volume label WORK_DISK055 exceeds the 11-character limit. But PATHWORKS Advanced Server allows you to include the device name (DOT$DUA3) in the autoshare list in the LANMAN.INI file and creates the autoshare WORK5$ for DOT$DUA3:.

A.4.2 The NOAUTOSHARE keyword

The NOAUTOSHARE keyword in the LANMAN.INI file specifies the OpenVMS device names that should not be automatically shared.

If the server configuration includes many disk devices, you may want to specify which devices are not shared automatically. By sharing some devices and not sharing others, you can separate OpenVMS disk resources from PATHWORKS Advanced Server resources and reduce unnecessary resource consumption by the server. Entries in the NOAUTOSHARE keyword list match OpenVMS device names that contain the search string. For example, the following line in the VMSSERVER section of the LANMAN.INI file specifies search strings DFS, DAD*, and PWRK$DKB300.

NOAUTOSHARE = DFS,DAD*,PWRK$DKB300

With this set of search strings, any OpenVMS device name containing the string DFS, any string containing DAD followed by any characters such as DAD1 and DAD2, and the explicit device PWRK$DKB300 are not shared. The total search string after the equal sign (=) cannot exceed 128 characters.

OpenVMS disk devices mounted cluster wide are offered to users as shared devices (autoshares) by all server nodes in an OpenVMS cluster system. Devices mounted on a specific server (not cluster wide) are accessible to users connected to that server only.

The LANMAN.INI file contains two sections that govern autoshares: the VMSSERVER section and the NODE_servername section. In an OpenVMS cluster system, you can make a device available cluster wide by using the AUTOSHARE keyword in the VMSSERVER section. You can restrict device availability to a particular server by using the AUTOSHARE keyword in the NODE_servername section.

The following fragment of a LANMAN.INI file illustrates how you can share disk devices in an OpenVMS cluster:

[VMSSERVER] AUTOSHARE = PCS524$DKA100=J,PCS524$DKA200=K [NODE_DOT] AUTOSHARE = DUA1001=H,DUA1002=G,DUA1006=I [NODE_TINMAN] AUTOSHARE = DUA1001=H,DUA1002=G

In this example:

• PCS524$DKA100 and PCS524$DKA200 are available as shared devices on autoshares J: and K: on all OpenVMS cluster server nodes.
• DUA1001 and DUA1002 are available as shared devices on autoshares H: and G: on server nodes DOT and TINMAN, respectively.
• DUA1006 is available as a shared device on autoshare I: on node DOT only.