HP Advanced Server V7.3B for OpenVMS and HP PATHWORKS V6.1 for OpenVMS (Advanced Server)

HP PATHWORKS V6.1 for OpenVMS (Advanced Server)

• Server-based license management. PATHWORKS Advanced Server also allows client

access based on the availability of Client Access licenses in the local LMF database being

used in server-based mode. If a client requesting access to the server fails to produce

a valid client-based license, the PATHWORKS License Registrar software checks for the

availability of a valid Client Access license being used in server-based mode. If one is

available, the client is allowed access.

Client Access licenses can be put into server-based mode in one of two ways:

– If the PATHWORKS License Server was not conﬁgured for the system where

PATHWORKS Advanced Server is executing, then all Client Access licenses loaded

into the local LMF database on that system will be used in server-based mode.

– If the PATHWORKS License Server was conﬁgured for the system where

PATHWORKS Advanced Server is executing, then all Client Access licenses

loaded into the local LMF database will, by default, be used in client-based mode.

To allow some or all of these licenses to be used in server-based mode, use the

PATHWORKS License Manager to allocate a portion of those licenses to the special,

predeﬁned Server-Based group. Licenses available in the Server-Based group will

then be available for use in server-based mode.

Note: PATHWORKS Advanced Server allows you to simultaneously use Client Access licenses

in both client-based and server-based mode. However, because clients using Client Access

licenses in client-based mode are already licensed to use the server software, they never

consume additional Client Access licenses allocated for use in server-based mode.

Accommodation of Retired Features

The following features of PATHWORKS V5.0 for OpenVMS (LAN Manager) are not provided in

PATHWORKS V6.1 for OpenVMS (Advanced Server):

• Standalone server role. PATHWORKS Advanced Server can be conﬁgured as a PDC,

BDC, or member server.

• FAT volumes. To continue to provide FAT volume access to clients, you must maintain the

PATHWORKS for OpenVMS (LAN Manager) server on a separate system. Files held within

shares on a FAT volume must be migrated to PATHWORKS for OpenVMS (LAN Manager)

shares before you upgrade to PATHWORKS Advanced Server.

• Backward-compatibility mode. This mode is used to ease the migration from

PATHWORKS V4.x to PATHWORKS V5.0 for OpenVMS (LAN Manager) . Make

sure all clients making use of this connection format are upgraded before the installation of

PATHWORKS Advanced Server.

• Remote Boot service. If clients depend on remote booting, you must maintain the

PATHWORKS for OpenVMS (LAN Manager) server on a separate system. Transfer this

function to another server that supports Remote Boot service before the upgrade.

• Share-level security. PATHWORKS Advanced Server manages access to all resources

through user-level security.