| United States-English |
|
|
|
![]() |
Advanced Server/9000: Advanced Server/9000 Installation Guide > Chapter 4 Migrating from LAN Manager/XChanges from LAN Manager/X to Advanced Server/9000 |
|
This section describes LAN Manager Version 1.x functionality that is implemented differently or not supported in Advanced Server/9000.
In Advanced Server/9000, there are some minor syntax changes that apply to all net commands:
Changes to the net commands from LAN Manager/X to Advanced Server/9000 are shown in the following table.
The new net commands for Advanced Server/9000 are shown in table 2. For more information about net commands in Advanced Server/9000, see the Advanced Server/9000 Administrator's Guide.
The Advanced Server/9000 server supports shared file access with other servers running on the same HP-UX system when file interlocking is enabled. File interlocking will propagate client file range locks to HP-UX file system range locks. If other servers also respect HP-UX file range locks then files can be safely accessed by multiple servers. Advanced Server/9000 does not support the extended interlocking options that LAN Manager 1.x provides to support PacerShare servers. LAN Manager 1.x has the following lanmanx.ini entry: [ server ] interlock=yes|no|readonly|exclusive (default is no) Advanced Server/9000 replaces LAN Manager 1.x's lanmanx.ini entry with the UseUnixLocks registry value in the AdvancedServer\FileServiceParameters key name. The UseUnixLocks registry value specifies whether record locks created by clients are reflected in the UNIX file system. The default is 0 (locks are not reflected in UNIX file system). Refer to the appendix on Advanced Server Registry in the Advanced Server/9000 Administrator's Guide for more details on use of the registry. LAN Manager 1.x has interlock=exclusive and interlock=readonly modes to support the PacerShare product. Advanced Server/9000 does not have equivalent locking functionality. Note also that the net file command on the server does not list locks taken out on files due to OPEN calls. The command only shows locks taken out on files due to explicit LOCK calls by clients. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||