HP OpenVMS Systems
HP Advanced Server V7.3B for OpenVMS
$ REGUTL SHOW VALUE * ALIASNAME
This section covers important licensing guidelines that either have not
been documented before or need special consideration.
3.19.1 License Enforcement
Advanced Server for OpenVMS requires that clients accessing server resources be appropriately licensed. To conform to this requirement, one of the following must be true:
In both cases, the minimum license required to access Advanced Server for OpenVMS services is the Client Access license PWLMXXXCA07.03, or an equivalent client virtual license. This license can be used as either a client-based license or a server-based license.
To access Advanced Server for OpenVMS resources, clients currently using client-based
licenses to access PATHWORKS file servers must upgrade their
licenses. Clients requesting PWLMXXXCA06.00 licenses need to be
upgraded to request PWLMXXXCA07.03 licenses. For more information about
licensing and upgrading licenses, see Section 3.19.2, Loading or Upgrading to PWLMXXXCA07.03 Licenses, and refer to the
HP Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.
3.19.2 Loading or Upgrading to PWLMXXXCA07.03 Licenses
Note that if you are loading or upgrading to PWLMXXXCA07.03 client
access licenses, the License Server will assign any PWLMXXXCA07.02
licenses first, if they are loaded and available. Remember that a
PWLMXXXCA07.03 license is required to access the Advanced Server V7.3B for OpenVMS. HP
recommends that you remove the PWLMXXXCA07.02 licenses from the system
and/or modify the clients to explicitly request PWLMXXXCA07.03
licenses. For more information, refer to the HP Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses.
3.19.3 Client License Support
HP supports PATHWORKS 32 client license software on Windows 95, Windows
98, Windows NT 4.0, Windows 2000, and Windows XP Professional clients.
For your convenience, unsupported PATHWORKS licensing software for
other clients remain available on the Advanced Server kit (in specific,
PATHWORKS licensing software for DOS and Windows 3.1, and PATHWORKS
licensing software for Protected Mode Windows for Workgroups LAN
3.19.4 Client License Software for Windows 2000 and Windows XP Clients
Windows 2000 clients can obtain client license software either from the
PATHWORKS 32 distribution kit, the PWLICENSE share, or from HP customer
support. Windows XP Professional clients can obtain client license
software either from the PWLICENSE share or HP customer support. To
enable clients to access the PWLICENSE share and install the client
licensing software, make sure that server-based licensing is enabled.
3.20 PWRK$MONITOR and CMT Tools Replaced by PWRK$PWMON Utility
Though the images for the PWRK$MONITOR utility and the client-based Configurator, Monitor, and Tuner (CMT) tools are still included in the Advanced Server for OpenVMS kit, as of Version 7.3 of the Advanced Server for OpenVMS, these utilities can no longer be used with the Advanced Server for OpenVMS.
The PWRK$PWMON utility gathers and displays the data collected by the
server. Unlike PWRK$MONITOR, PWRK$PWMON is not invoked automatically at
startup. It is invoked from the command line. The PWRK$PWMON utility is
provided for use by HP customer support.
3.21 PWRK$LMDMN Process and Startup File Replaced
Advanced Server products prior to V7.3 use the PWRK$LMDMN process to validate logons and replicate the domain security accounts database. Beginning with Advanced Server V7.3 for OpenVMS, the PWRK$LMSRV process provides this functionality instead. As noted in Section 22.214.171.124, Domain Database Replication and Network Logon Performance Improvement, this serves to streamline the operation of the Advanced Server, especially during replication.
The PWRK$LMDMN process and its associated startup command file
(PWRK$LMDMN_STARTUP.COM) are no longer part of the software kit and are
not installed with the software.
3.22 RMS Protections
RMS sets protection on files and directories based on user identification codes (UICs). As described in the HP Advanced Server for OpenVMS Server Administrator's Guide, the user's UIC determines which categories a user belongs to (System, Owner, Group, World). RMS assigns file protections for each of these categories. The default protections for files and directories are listed in Table 3-2.
The RMS protections associated with a share definition are used to set RMS protections on new files or directories created within that share. When an object (file or directory) in that share is replaced with an object of the same name from another share, the original object's protections are inherited by the object replacing it.
The default values for the directory protections and file protections are listed in Table 3-2, Default Values for RMS File and Directory Protections:
|Protections||RMS Protection Codes|
|Directory||S: RWED, O: RWED, G: RWED, W: RE|
|File||S: RWD, O: RWD, G: RWD, W:R|
The administrator can change the RMS protection on a specific share by using the ADMINISTER MODIFY SHARE command with the /HOST_ATTRIBUTES qualifier to set the file and directory protections. For example:
$ ADMINISTER MODIFY SHARE share-name - _$ /HOST_ATTRIBUTES=(DIRECTORY_PROTECTION=(O:WRE,G:WR,W:R), - _$ FILE_PROTECTION=(O:WRED, G:WR, W: R))
Note that granting write access to a category will automatically grant it delete access as well.
Because share data (such as host attributes) is cached when the first client accesses the share, the changes made to share protections are not reflected until either all users are disconnected from the share or the Advanced Server is restarted.
The Advanced Server for OpenVMS supports four different RMS file formats for shares:
Support of the stream_LF file format is introduced with Advanced Server V7.3A for OpenVMS to accommodate applications that require or recommend such a format.
Define the RMS file format for a share by using the MODIFY SHARE or ADD SHARE/DIRECTORY command. Use the /HOST_ATTRIBUTES=rms-format qualifier to specify one of the following as the format (rms-format):
Note that with the addition of the STREAM_LF keyword for the /HOST_ATTRIBUTES qualifier, you must now specify the STREAM keyword in full to distinguish it from the STREAM_LF qualifier. You can abbreviate the STREAM_LF keyword to "STREAM_" at a minimum. Abbreviations are not recommended for use in batch jobs and command procedures.
To control user access to print shares, you can assign users to the
groups that have the appropriate access permissions, or you can assign
permissions directly to shares. For more information, refer to the
HP Advanced Server for OpenVMS Server Administrator's Guide.
3.25 Windows NT Printer Management of Large Numbers of Printers
Depending on the processor upon which your Advanced Server runs, the number of printers served might affect performance of Windows NT printer management actions. HP recommends enabling Windows NT printer management only on servers with fewer than 100 printers. HP has found that with 100 or more printers, actions that require enumerating could take a long time. (Note that for some actions, printer enumeration is not obvious.) Windows NT fails to display an hourglass, causing the printer action to appear hung. For information on restrictions relating to Window NT management of server printers, see Section 13.7.8, Windows NT Printer Management Restrictions.
If you do choose to ignore HP's recommended limit for the number of printers for Windows NT printer management, and your server has approximately 1000 or more printers defined, set the OpenVMS SYSGEN CTRLPAGES parameter to a generous size. Otherwise, the OpenVMS Registry will be unable to open the keys associated with the printers, preventing printer management functions from being performed and possibly causing the server to fail. This recommendation for the CTRLPAGES parameter is unrelated to the performance issue mentioned in the previous paragraph.
The default for the CTRLPAGES parameter is 256. For example, for a thousand printers, set the value to at least 275. Increment the size by one for every ten additional printers over 1000.
Clients might not be able to access certain files on a shared ODS-2 disk that were originally created on an Advanced Server V7.2 for OpenVMS server. These are files that have long names that include multiple periods. When the periods are encoded, the file names exceed 40 characters in length. (On ODS-2 volumes, the limit for the file name is 39 characters and the limit for the extension is 39 characters.) Advanced Server V7.2 for OpenVMS servers use a method to encode file names that differs from the method that both Advanced Server for OpenVMS (V7.3 and higher) servers and PATHWORKS V6 Advanced Servers use. Therefore, files originally created on disk by an Advanced Server V7.2 for OpenVMS product might not be accessible by clients who connect to an Advanced Server V7.3 for OpenVMS product. Use the PWRENAME utility to rename such files so that they can be accessed by clients. PWRENAME is defined in the command definition file SYS$STARTUP:PWRK$DEFINE_COMMANDS.COM.
To invoke the command, enter the following line:
$ PWRENAME filespec
where filespec is the name of a specific file or the name of a device or directory. If you specify the name of a file, the utility operates on that specific file only. If you specify a device, the utility operates on all files on the device. If you specify a directory, the utility operates on all files in the specified diretory.
Use any of the following qualifiers:
|/LOG= logfile_name||Specifies a file to log the output. By default, output is sent to SYS$OUTPUT.|
|/[NO]RENAME||With the RENAME qualifier, the utility renames each file whose name exceeds the 40 character limit. This is the default. With the NORENAME specifier, the utility outputs the list of files that exceed the 40-character limit, but does not rename them.|
|/[NO]VERBOSE||With the VERBOSE qualifier, the utility outputs the names of all files examined. This is the default. Use the /NOVERBOSE qualifier to prevent such output.|
Beginning with Advanced Server V7.3A for OpenVMS, the Macintosh file attribute information (used by the now retired PATHWORKS for Macintosh server) is no longer stored in the ACL of a file's header. This reduces the size of the Advanced Server ACE in the file header by 117 bytes (from 163 bytes to 46 bytes) and reduces the number of files with secondary file headers (extension file headers).
The ACE of a file created by an Advanced Server for OpenVMS prior to Version 7.3A, or by a PATHWORKS for OpenVMS (Advanced Server), would appear as follows (using the indicated OpenVMS DCL command):
$ SHOW SECURITY filename (UNKNOWN=%X80,SIZE=%D163,FLAGS=%X0C00,ACCESS=%X06900000,DATA= %X00000008,%X00000000,%X0000041E,%X3EAC4100,%X511B0000,%XC63F8E74, %X1CF4009E,%X2703722A,%X27036E4D,%X05756E4D,%X00000000,%X00000000, %X00000000,%X00000000,%X00000000,%X00000000,%X00000000,%X00000000, %X010A0000,%X10E51200,%X00800200,%X00000000,%X00000000,%X00000000, %X00000000,%X00000000,%X00000000,%X00000000,%X00000000,%XEE710000, %XB022F5BF,%X0000FF39,%X00008000,%X00000000,%X00000000,%X00000000, %X00000000,%X00000000,%X00000000)
The ACE of a file created on Version 7.3A (or later) of the Advanced Server for OpenVMS now appears as follows:
$ SHOW SECURITY filename (UNKNOWN=%X80,SIZE=%D46,FLAGS=%X0C00,ACCESS=%X06900000,DATA= %X00000008,%X00000000,%X0000041E,%X30064120,%X2A490003,%X8857ACB1, %X2AC600A0,%X2C3586F0,%X2C355E40,%X00005E40)
ACEs of files created on earlier versions of the Advanced Server for OpenVMS will be converted automatically to the latter format whenever the file is opened with write access; that is, whenever a client modifies or writes the file. Therefore, no further action is required to convert the ACE format.
This new ACE format is not compatible with any Advanced Server for OpenVMS prior to Version 7.3A. Customers needing to preserve the old ACE format on existing files can do so by adding the following line to the [ODS2] section in the PWRK$COMMON:PWRK.INI file:
If you ever need to downgrade the Advanced Server from V7.3A or later to a previous version, you can make file ACEs compatible again by doing either of the following:
HP recommends that before you upgrade to Version 7.3A (or later) of the Advanced Server for OpenVMS, you first back up all disks that have files that might be converted. If you later decide to go back to an earlier version of the Advanced Server for OpenVMS, you can restore the files from the backups.