|
HP OpenVMS Systems |
|
HP Advanced Server V7.3B for OpenVMSRelease 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
Software Version: HP Advanced Server V7.3B for OpenVMS
© 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.
PrefaceThe 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 AudienceThese Release Notes are intended for the Advanced Server for OpenVMS system administrator. It assumes you have:
Document StructureThis manual contains the following chapters:
Related DocumentsThe Release Notes supplement the following manuals:
The following table lists related OpenVMS documents.
For additional information about HP OpenVMS products and services, access the following OpenVMS World Wide Web address:
Reader's CommentsHP welcomes your comments on this manual. Please send comments to either of the following addresses:
How To Order Additional DocumentationFor information about how to order additional documentation, visit the following World Wide Web address:
Chapter 1
|
$ DEFINE/SYSTEM PWRK$LR_DISABLE_CLIENT_PING 0 |
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.
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. |
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:
pwrk$lmsrv process abnormally terminated.
See PWRK$LMLOGS:PWRK$LMSRV_<nodename>.LOG;* for further information"
|
PWRK$LMSRV PROCESS TERMINATED ABNORMALLY!
|
$ ADMIN SHOW EVENTS/FULL
|
An Advanced Server for OpenVMS process with pid <pid> unexpectedly terminated |
================= 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 |
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 |
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 |
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 |