HP OpenVMS Systems

Content starts here

HP Advanced Server V7.3B for OpenVMS

Release Notes


September 2006

This document includes information about the Advanced Server V7.3B for OpenVMS distribution kit, software features and usage guidelines, the latest problem fixes, fixes from preceding product versions, known problems, and restrictions. These Release Notes supplement the product documentation. Always read the Release Notes before you start the product installation

Revision/Update Information: This document supersedes the Advanced Server V7.3A for OpenVMS Release Notes*.

Operating System: OpenVMS Alpha Version 7.3-2, 8.2 and 8.3
(For more information on the supported versions, please refer to the cover letter.)

Software Version: HP Advanced Server V7.3B for OpenVMS



Hewlett-Packard Company
Palo Alto, California


© Copyright 2006 Hewlett-Packard Development Company, L.P.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.

UNIX is a registered trademark of The Open Group.

The HP Advanced Server for OpenVMS documentation set is available on CD-ROM.

This document was prepared using VAX DOCUMENT, Version V3.3-1b.

Contents Index


Preface

The HP Advanced Server for OpenVMS Release Notes include information about the distribution kit, software features and usage guidelines, the latest problem fixes, and restrictions.

These Release Notes supplement the product documentation. Always read the documentation as well as the product Release Notes.

Intended Audience

These Release Notes are intended for the Advanced Server for OpenVMS system administrator. It assumes you have:

  • A basic understanding of a PC LAN network
  • A basic understanding of managing the HP OpenVMS operating system
  • Access to the Advanced Server for OpenVMS documentation

Document Structure

This manual contains the following chapters:

  • Chapter 1 contains information about the Advanced Server for OpenVMS software kit.
  • Chapter 2 describes the main features of the Advanced Server for OpenVMS software.
  • Chapter 3 provides guidelines for using the Advanced Server for OpenVMS software.
  • Chapter 4 describes the problems corrected in Advanced Server V7.3 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 5 describes the problems corrected in Advanced Server V7.3-ECO1 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 6 describes the problems corrected in Advanced Server V7.3-ECO2 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 7 describes the problems corrected in Advanced Server V7.3A for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 8 describes the problems corrected in Advanced Server V7.3A-ECO1 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 9 describes the problems corrected in Advanced Server V7.3A-ECO2 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 10 describes the problems corrected in Advanced Server V7.3A-ECO3 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 11 describes the problems corrected in Advanced Server V7.3A-ECO4 for OpenVMS. These changes also apply to Advanced Server V7.3B for OpenVMS.
  • Chapter 12 describes the problems corrected in Advanced server V7.3B for OpenVMS.
  • Chapter 13 describes restrictions in the Advanced Server for OpenVMS software.

Related Documents

The Release Notes supplement the following manuals:

Document Description
HP Advanced Server for OpenVMS Server Installation and Configuration Guide Explains how to install and configure Advanced Server software.
HP Advanced Server for OpenVMS Concepts and Planning Guide Provides an overview of and introduction to the Advanced Server software and associated networking concepts for system administrators and operators.
HP Advanced Server for OpenVMS Server Administrator's Guide Explains how to manage and customize the Advanced Server software.
HP Advanced Server for OpenVMS Commands Reference Manual Provides command syntax descriptions for all ADMINISTER commands and NET command equivalents.
HP Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses Describes the License Server software and how to manage Advanced Server licenses.

The following table lists related OpenVMS documents.

OpenVMS Document Description
x New Features and Documentation Overview Manual Describes the new features of the OpenVMS software and an overview of the documentation that supports it
x Upgrade and Installation Manual Describes how to install the OpenVMS Alpha system software
OpenVMS System Manager's Manual A task-oriented guide (in two volumes) to managing an OpenVMS system; describes how to set up the required system services
OpenVMS Guide to System Security Describes OpenVMS security features, including procedures for enabling external authentication
OpenVMS System Management Utilities Reference Manual A reference guide (in two volumes) to the utilities and tools used in managing an OpenVMS system
OpenVMS License Management Utility Manual Explains how to load and manage license Product Authorization Keys (PAKs)
HP OpenVMS System Manager's Manual Describes Extended File Specifications on OpenVMS, including how to set up and enable the ODS-5 file system
COM, Registry, and Events for OpenVMS Developer's Guide Contains COM for OpenVMS, OpenVMS Registry, and OpenVMS Events information
HP C Run-Time Library Utilities Reference Manual Describes utilities that help you manage localization and time zone data for international software applications

For additional information about HP OpenVMS products and services, access the following OpenVMS World Wide Web address:


http://www.hp.com/go/openvms

Reader's Comments

HP welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet openvmsdoc@hp.com
Mail Hewlett-Packard Company
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How To Order Additional Documentation

For information about how to order additional documentation, visit the following World Wide Web address:


http://www.hp.com/go/openvms/doc/order


Chapter 1
Distribution Kit

The Advanced Server V7.3B for OpenVMS software kit supports OpenVMS Alpha systems. The kit name is:
CPQ-AXPVMS-ADVANCEDSERVER-V0703-B-1.PCSI


Chapter 2
Features of Advanced Server for OpenVMS

Advanced Server for OpenVMS (often referred to as the Advanced Server) implements networking functions that are compatible with a Windows NT Server. The Advanced Server for OpenVMS offers easy access to OpenVMS file and printer resources from Windows desktops, using native Microsoft products and utilities such as Windows Explorer. The Advanced Server for OpenVMS combines the networking strengths and rich application set of Windows NT with the proven availability, reliability, scalability, and security of OpenVMS. It incorporates much of the code and functionality of Advanced Server for UNIX (Tru64 UNIX), as well as of PATHWORKS for OpenVMS (Advanced Server). Some of the main features provided by the Advanced Server for OpenVMS include:

  • LAN Manager V3.0 technology (same as Windows NT V4.0)
  • Support of OpenVMS Alpha Version 7.3-2 and Version 8.2, including the following and much more:
    • OpenVMS Registry
    • External authentication and the distributed common object module (COM for OpenVMS), as implemented beginning with OpenVMS Version 7.2.
    • Extended File Specifications and ODS-5 (On-Disk Structure 5) disk volumes
  • Trusted domains
  • Wide Area Domain, Windows Internet Name Service (WINS) integration over TCP/IP
  • Full browser functionality
  • Windows NT management APIs
  • The following Windows 2000 support:
    • Interoperability with Windows 2000 clients
    • Interoperability with Windows 2000 domain controllers in a Windows 2000 mixed-mode domain when the Advanced Server for OpenVMS performs as a backup domain controller or member server
    • Interoperability with Windows 2000 domain controllers in a pure (native) Windows 2000 domain when the Advanced Server for OpenVMS performs as a member server
  • Support for Windows XP Professional clients
  • The comprehensive ADMINISTER command-line interface
  • External authentication (allowing OpenVMS users to log in at the OpenVMS prompt using their domain user name and password) and password synchronization between OpenVMS and Advanced Server systems
  • User account lockout
  • Support for DECnet and DECnet-Plus, TCP/IP, and NetBEUI

This chapter includes the following information:

Topic Section Number
New Features Provided by Advanced Server V7.3B for OpenVMS 2.1
New Features Provided by Advanced Server V7.3A-ECO4 for OpenVMS 2.2
New Features Provided by Advanced Server V7.3A-ECO3 for OpenVMS 2.3
New Features Provided by Advanced Server V7.3A-ECO2 for OpenVMS 2.4
New Features Provided by Advanced Server V7.3A for OpenVMS 2.5
Overview of Advanced Server for OpenVMS Features 2.6
Differences Between Advanced Server V7.3B for OpenVMS and PATHWORKS V6.1 for OpenVMS (Advanced Server) 2.7

2.1 New Features Provided by Advanced Server V7.3B for OpenVMS

2.1.1 Option to Disable Client License Check

By default, when a client establishes a session to the Advanced Server for the purpose of mapping a drive or printer, the server establishes a separate session to the client to determine if the client has any client-based licenses installed. This license check can incur a significant delay if the client or network employs a firewall which blocks incoming traffic on TCP port 139.

The delay can cause the attempt to map a drive to timeout and fail. If your clients do not use client-based licenses (instead rely only on server-based licenses present on this system), you can prevent the server from querying clients for licenses by responding Yes to the following prompt:

Do you have PATHWORKS client license components installed on any client in your network. If not, do you wish to disable client-based license checks (enter ? for more information)? [Y]

You can enable client license check by defining the logical:


$ DEFINE/SYSTEM PWRK$LR_DISABLE_CLIENT_PING 0

2.1.2 Option to Install PC Files and Shares

By default, Advanced Server V7.3A ECO4 for OpenVMS or earlier always created the PWUTIL, PWLIC, and PWLICENSE shares. These 3 shares include files which can be used by Windows clients for various purposes.

The PWUTIL share contains Windows utilities, such as User Manager for Domains and Server Manager, which can be used to manage Advanced Server from a Windows client. The PWLIC and PWLICENSE shares include a copy of the Windows software necessary to implement client-based licensing. This software is not required if you choose server-based licensing only. The client-based licensing software is also available on the PATHWORKS32 for Windows kit.

These utilities and the client-based licensing software are not required by all the users accessing Advanced Server. Hence, Advanced Server V7.3B for OpenVMS provides the option to install or remove these files and their associated shares.

During the initial configuration of Advanced Server after installation, the administrator is prompted whether to install these files. Administrators can either choose to install these files now or install them at a later time using a command procedure included in the Advanced Server kit. If the files already exist, the administrator is prompted whether to delete them or not.

In any case, the two command procedures - PWRK$PWUTIL.COM and PWRK$PWLIC.COM - are copied to SYS$COMMON;[SYSUPD] during installation. At any point of time, if the administrator wants to add or delete the PWUTIL share and files, execute the following command:


$ @SYS$UPDATE:PWRK$PWUTIL.COM

If the administrator wants to add or delete the PWLIC and PWLICENSE shares and files (both shares use the same directory path), execute the following command:


$ @SYS$UPDATE:PWRK$PWLIC.COM

In both the cases, if Advanced Server is running when you execute this command procedure, it will prompt you for a username and password. If Advanced Server is not running, no username and password is required.

When prompted for a username and password, if Advanced Server is configured as a PDC or BDC, supply the credentials of a privileged domain user in order to successfully add or delete the files and shares.

If Advanced Server is configured as a Member Server, supply the credentials of the local Member server administrator account or any privileged member server local account.

Note

On Advanced Server configured as member server, when you run the command procedure, if you supply the credentials of a domain user, addition or deletion of shares will fail.

2.1.3 Automatic Restart of PWRK$LMSRV Process After Abnormal Termination

Prior to V7.3B of Advanced Server for OpenVMS, if the PWRK$LMSRV process crashed, it would also terminate the PWRK$LMMCP process which resulted in a complete Advanced Server failure. In this case, Advanced Server had to be restarted by an administrator.

With Advanced Server V7.3B for OpenVMS, a new feature has been introduced to automatically restart the PWRK$LMSRV process when it terminates abnormally. The automatic restart of PWRK$LMSRV is done without restarting the PWRK$LMMCP process. This makes the restart very fast as it only involves starting a new PWRK$LMSRV process and is done without administrator intervention.

Advanced Server provides a logical name, PWRK$TEMP_AUTO_SERVER_RESTART , to enable and disable this feature. Note that as long as this logical is not defined, automatic restart of PWRK$LMSRV process is enabled.

In order to disable automatic restart of the PWRK$LMSRV process when it terminates abnormally, the logical name needs to be defined as follows:


$ DEFINE/SYSTEM PWRK$TEMP_AUTO_SERVER_RESTART NO

To re-enable the automatic restart of the PWRK$LMSRV process, the logical needs to be either deassigned or defined as follows:


$ DEFINE/SYSTEM PWRK$TEMP_AUTO_SERVER_RESTART YES

It is not required to restart Advanced Server in order for the new value to become operative.

By default, the Advanced Server also sets a limit on the automatic restart of the PWRK$LMSRV process such that if 3 abnormal terminations occur within a 24 hour period, the process will not be restarted automatically; instead an administrator will need to manually restart Advanced Server. A new registry parameter - AutoServerRestartTime - is provided which specifies the number of days within which the 3 abnormal terminations of the PWRK$LMSRV process can occur and result in the automatic restart of the PWRK$LMSRV process.

For example, if the administrator wants to allow only 2 PWRK$LMSRV process crashes to be automatically restarted in a 15-day time period and does not want to automatically restart the PWRK$LMSRV process for the third occurrence, the registry parameter should be defined as follows:


$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM
$ REGUTL SET PARAMETER VMSSERVER AUTOSERVERRESTARTTIME 15/CREATE

Once this registry parameter is created, the /create qualifier need not be used to modify the parameter again. Also, restart Advanced Server after changing this registry parameter in order for the new value to become operative.

When a PWRK$LMSRV process crashes, messages similar to the following are posted in various log files as follows:

  • In SYS$MANAGER:OPERATOR.LOG, the message logged is similar to:


        pwrk$lmsrv process abnormally terminated.
        See PWRK$LMLOGS:PWRK$LMSRV_<nodename>.LOG;* for  further information"
    
  • In PWRK$LMLOGS;PWRK$LMMCP_<nodename>.LOG , the message logged is:


        PWRK$LMSRV PROCESS TERMINATED ABNORMALLY!
    
  • An event logged in the Advanced Server System event log can be viewed by executing the following command:


        $ ADMIN SHOW EVENTS/FULL
    

    The event message logged is similar to:


    An Advanced Server for OpenVMS process with pid <pid> unexpectedly
    terminated
    

    where <pid> indicates the process identification number of the terminated pwrk$lmsrv process.
  • In the Advanced Server common event log which can be viewed using the command $ ADMIN/ANALYZE. The message logged is similar to:


       ================= EVENT #8 ==================
    
       Event Time   :   20-JUN-2006 11:01:52.49       Node: <Nodename>
       Process Id   :   0000021F
       Event        :   Unexpected System Error Encountered
       Event Source :   LAN Manager Utility
       Event Class  :   Error
    
       Status       :   %SYSTEM-F-ABORT, abort
       Text         :   PWRK$LMSRV process terminated
    
    

2.1.4 Server Message Block (SMB) Signing

Advanced Server V7.3B for OpenVMS supports SMB signing. By default, SMB signing is enabled for outgoing connections and is disabled for incoming connections.

For definition and explanation of SMB signing, refer to the following Microsoft Knowledge Brief:


http://support.microsoft.com/kb/887429/en-us#top

To enable SMB signing for incoming connections, execute the following commands:


$ @SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM
$ REGUTL SET PARAMETER SERVER ENABLESECURITYSIGNATURE 1/CREATE

To require SMB signing for incoming connections, execute the following commands:


$ SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM
$ REGUTL SET PARAMETER SERVER REQUIRESECURITYSIGNATURE 1/CREATE

Note

After modifying either of the above registry parameters, restart the Advanced Server for the new values to become operative.

To enable SMB signing for outgoing connections, execute the following commands:


$ SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM
$ REGUTL SET PARAMETER RDR ENABLESECURITYSIGNATURE 1/CREATE

To require SMB signing for outgoing connections, execute the following commands:


$ SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM
$ REGUTL SET PARAMETER RDR REQUIRESECURITYSIGNATURE 1/CREATE

Note

After modifying either of the rdr registry parameters, the Advanced Server need not be restarted for the new values to become operative.

In all these cases, once the registry parameters are created, the /create qualifier need not be used to modify the parameter again.


Next Contents Index