HP OpenVMS Systems

HP Advanced Server for OpenVMS
Server Installation and Configuration Guide

By default, the language of the Advanced Server is "English (USA)". You can configure any one of over 40 languages for the Advanced Server. For an up-to-date list of the languages officially supported by the Advanced Server, refer to the Software Product Description (SPD).

3.8.1 Considerations Regarding the Server Language

Consider the following when configuring the server language:

• The same language should be used by all servers in a domain. All Advanced Servers in the same cluster automatically share the same language (they share the same registry database where the language is stored).
• Although you can change the server's language at any time (after stopping the Advanced Server), HP recommends that once a choice is made, you do not alter that choice.
  Certain objects might exist whose names include characters that are not included in the new language that you select. For example, after you select a new language, PWRK$CONFIG might convert (depending on the language) all text strings in the Security Account Manager (SAM), access control list (ACL), and share databases from the old character set (for the previous language) to the new set (for the new language).
  If one or more of these databases are converted, PWRK$CONFIG displays the following message:

  Setting character set information in databases as needed...

  
  In addition, a message will be displayed for each database affected, such as:

  Setting share database character set information ...

  
  If any of these databases contain text strings that cannot be converted (that is, object names that contain characters not included in the newly configured Advanced Server language character set), the PWRK$CONFIG procedure reverts to the set of databases that existed prior to conversion attempt. Error messages will indicate the names that could not be converted, and the language is reset to the original language. You must rename (or remove) the objects that cannot be converted, and rerun PWRK$CONFIG to change the language.
  Note that for some languages, PWRK$CONFIG does not need to convert the text strings in the databases mentioned above --- it changes the client code page value only. (A client code page is an ordered set of 256 characters that extends the limits of ASCII (American Standard Code for Information Interchange) character sets to support the variety of characters used in languages internationally. Each language-specific code page overlays the same set of 8-bit values. For example, a specific 8-bit value in a code page used for the English language can be used for another character used for the Cyrillic language.)

During the PWRK$CONFIG.COM configuration procedure, you can configure an Advanced Server language other than the default by selecting option 9. The procedure lists the configurable languages. At the prompt, enter the number of the language you want to use.

In the following example, the Hebrew language is configured (character set ISO8859-8).

  Your Advanced Server for OpenVMS is presently configured to
  run as follows:

   1.  Run the License Server:          NO
   2.  Enable Timesource service:       NO
   3.  Enable Alerter service:          YES
   3a. Alert user names:                Administrator
   4.  Enable Netlogon service:         YES
   5.  Advanced Server domain:          LANDOFOZ
   6.  Advanced Server role:            MEMBER
   7.  Advanced Server computer name:   LIONHEART
   7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIAS
   8.  Server announce comment:    Advanced Server V7.3B for OpenVMS
   9.  Advanced Server language:        English (USA)
   10. Enable NT style printing:        NO
Enter item number, or RETURN to use these values [DONE]: 9 [Return]

******************** W A R N I N G ************************
Although you can change the server's language at any time
(after stopping the Advanced Server), HP recommends
that once a choice is made, you do not alter that choice.
Certain objects might exist whose names include characters
that are not included in the new language that you select.
Error messages will indicate the names that could not be
converted, and the language will be reset to the original
language. If you want to change the language, you must
first rename (or remove) the objects that cannot be
converted, and rerun PWRK$CONFIG to change the language.
***********************************************************"
Do you want to continue with item number 9 (Y/[N]) Y [Return]
 1) Afrikaans           16) French               31) Portuguese
 2) Albanian            17) French (Ca. MS-DOS)  32) Portuguese (MS-DOS)
 3) Basque              18) German               33) Romanian
 4) Belarussian         19) Greek                34) Russian
 5) Bulgarian           20) Greek (IBM)          35) Serbian (Cyrillic)
 6) Catalan             21) Hebrew               36) Serbian (Latin)
 7) Croatian            22) Hungarian            37) Slovak
 8) Czech               23) IBM Cyrillic         38) Slovenian
 9) Danish              24) Icelandic            39) Spanish
10) Dutch               25) Icelandic (MS-DOS)   40) Swedish
11) English (USA)       26) Indonesian           41) Turkish
12) English (USA)+Euro  27) Italian              42) Ukrainian
13) English (Other)     28) Nordic L. (MS-DOS)   43) Western Europe+
14) Faeroese            29) Norwegian                Euro
15) Finnish             30) Polish

  The Advanced Server language specifies the internal character set
  encoding for strings, character casing rules, and the client
  code page.

Enter Advanced Server language by number for this cluster [English(USA)]: 21 [Return]

  Your Advanced Server for OpenVMS is presently configured to
  run as follows:

   1.  Run the License Server:          NO
   2.  Enable Timesource service:       NO
   3.  Enable Alerter service:          YES
   3a. Alert user names:                Administrator
   4.  Enable Netlogon service:         YES
   5.  Advanced Server domain:          LANDOFOZ
   6.  Advanced Server role:            MEMBER
   7.  Advanced Server computer name:   LIONHEART
   7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIAS
   8.  Server announce comment:    Advanced Server V7.3B for OpenVMS
   9.  Advanced Server language:        Hebrew
   10. Enable NT style printing:        NO
Enter item number, or RETURN to use these values [DONE]: [Return]

By default, printers shared by the server are managed locally using the ADMINISTER user interface. You can configure the server to support management of the printers from Windows NT. This allows you to take advantage of the Windows NT style of printer management, using the Windows NT print services dialog boxes, such as the Add Printer wizard for adding printers.

Administrators can then store the latest drivers for the printers on the Advanced Server. When new drivers are distributed, administrators have to update a single location only. When client users set up printers to use from their workstations, they are able to download the appropriate printer driver automatically.

Before configuring your sever to support Windows NT printer management, be sure to familiarize yourself with the considerations noted in Section 3.9.1, Considerations Regarding Windows NT Printer Management.

3.9.1 Considerations Regarding Windows NT Printer Management

Consider the following before choosing to configure the Windows NT style of printer management. When you enable Windows NT printer management:

• Only limited functionality is available for managing printers with the ADMINISTER interface. (Similarly, when the default printer management style is enabled (using the ADMINISTER interface), limited functionality is available for managing the printers from Windows NT.)
• Printers or print queues that were already defined on the server are upgraded automatically so that clients can continue to share these printers and their queues. However, management of these upgraded printers from Windows NT is limited. To gain full Windows NT management functionality for these printers, use Windows NT print services to delete the printers and then to add the printers back onto the Advanced Server.

  Note When running PWRK$CONFIG to reconfigure the Advanced Server, printers that have been upgraded previously are not upgraded again.

• Once you configure the Windows NT printer management style, if you decide to reconfigure your server to the default local printer management style, all printers will be unusable. You will have to perform several, time-consuming tasks to make printers functional again.
• Be sure to refer to the HP Advanced Server V7.3B for OpenVMS Release Notes for more information on restrictions regarding Windows NT printer management.

During the PWRK$CONFIG.COM configuration procedure, you can configure Windows NT style printer management by selecting option 10. The procedure displays a warning and asks you if you are sure you want to make the change, as shown in the following example:

  Your Advanced Server for OpenVMS is presently configured to
  run as follows:

   1.  Run the License Server:          NO
   2.  Enable Timesource service:       NO
   3.  Enable Alerter service:          YES
   3a. Alert user names:                Administrator
   4.  Enable Netlogon service:         YES
   5.  Advanced Server domain:          LANDOFOZ
   6.  Advanced Server role:            MEMBER
   7.  Advanced Server computer name:   LIONHEART
   7a. Advanced Server OpenVMS Cluster alias:   LIONHEART_ALIAS
   8.  Server announce comment:    Advanced Server V7.3B for OpenVMS
   9.  Advanced Server language:        English (USA)
   10. Enable NT style printing:        NO
Enter item number, or RETURN to use these values [DONE]: 10 [Return]

******************** W A R N I N G ************************
Before enabling this feature, make sure you are familiar with
the Windows NT printer management restrictions documented in the
Release Notes. Note that once you configure the Windows NT printer
management style, if you reconfigure your server to the default
local printer management style, all printers will be unusable. You
will have to perform several time-consuming tasks to make printers
functional again.
***********************************************************"
Are you sure you want to enable
Windows NT printer management? [Y/[N]] Y [Return]

10. Enable NT style printing: Y [Return]

This section describes how to:

• Troubleshoot Registry Server startup problems
• Ensure sufficient resources will be available to support clients
• How to recover if problems occur when reconfiguring the Advanced Server

For proper operation of the PWRK$CONFIG.COM configuration procedure and the file server, registry services must be available on the system running the Advanced Server.

In an OpenVMS Cluster environment, the OpenVMS Registry can be configured so that the Registry Server does not run on the server node but rather on another node in the cluster. However, HP recommends that the OpenVMS Registry be configured to run the Registry Server on every Advanced Server node. This ensures that registry services are available to the file server. For instructions on starting the Registry Server and enabling registry services, see Section 1.8.5, Step 5: Start the OpenVMS Registry Server.

• If registry services are not available, the PWRK$CONFIG.COM procedure attempts to start the OpenVMS Registry Server. If the attempt is successful, the procedure displays the following message:

  Checking to see if the OpenVMS Registry Services are available ... %RUN-S-PROC_ID, identification of created process is 0000023B

• If the SYS$REGISTRY logical is not defined, the OpenVMS Registry will not start. In this case, the PWRK$CONFIG.COM displays the following messages and terminates:

  Checking to see if OpenVMS Registry Services are available... SYS$REGISTRY must be defined to start the VMS Registry %PWRK-F-NOREGISTRY, OpenVMS Registry services not configured for this system %PWRK-F-CONFIGERR, severe error encountered during configuration OpenVMS Registry Services are not available on this system. Some file server parameters are stored in the OpenVMS Registry. For the file server or file server utilities to be able to access these parameters, OpenVMS Registry Services must be available on this system. Since the file server requires access to the OpenVMS Registry, it is recommended that OpenVMS Registry Services be started as part of system start-up, before the file server is started. For instructions on how to start OpenVMS Registry Services please refer to the file server release notes. This configuration is incomplete and cannot continue. You must execute @SYS$UPDATE:PWRK$CONFIG again. Please configure and start the OpenVMS Registry Services before doing so.

  
  You must enable registry services and start the Registry Server, then run the PWRK$CONFIG.COM procedure again. For more information about enabling and starting the Registry Server, refer to the OpenVMS System Manager's Manual or the COM, Registry, and Events for OpenVMS Developer's Guide (included in the OpenVMS Documentation CD-ROM).

The Advanced Server requests the resources that it needs using the OpenVMS AUTOGEN utility. If AUTOGEN underestimates the resources required for use by processes other than the Advanced Server, and these resources have already been consumed when the Advanced Server is started, there may be insufficient resources left for the Advanced Server to support the desired number of clients.

To ensure sufficient resource allocation to support clients, make sure that all software that will run concurrently with the Advanced Server is installed and started before you run the the Advanced Server configuration procedure (PWRK$CONFIG.COM). If TCP/IP is selected as a transport, make sure that the TCP/IP product is loaded before you run the PWRK$CONFIG procedure.

After you successfully configure the Advanced Server, it may not start, reporting that there are insufficient resources to support any clients. In this case, examine the following file to determine the system resource that needs to be increased (nodename is the name of the server node):

PWRK$LOGS:PWRK$CONFIG_ERROR_nodename.LOG

To increase the resource, make the appropriate modifications to the MODPARAMS.DAT file and then run AUTOGEN.

3.10.3 If Problems Occur When Reconfiguring the Advanced Server

If you reconfigure a previously configured server, the PWRK$CONFIG command procedure creates subdirectories in the PWRK$LMDOMAINS: and PWRK$LMDATAFILES: directories, and stores the original accounts database files there.

The names of the subdirectories are based on the date and time, such as 16JUN200014314818.DIR, indicating that the directory was created on 16-JUN-2000 at approximately 2:32 p.m.

If an error occurs during configuration, the server configuration will be returned to its original state. After you are confident you have a successful reconfiguration, you can manually delete these subdirectories and their contents.

3.11 The Advanced Server Network Adapter

The PWRK$CONFIG configuration might need to use the network to communicate with the PDC. If the system has more than one network adapter (also referred to as a network interface card), the default adapter chosen by PWRK$CONFIG might not be the correct interface. Or, on some newer systems, the Advanced Server might not recognize the only network adapter present. In cases such as these, you can define system logical names to direct the Advanced Server to use a specific interface. If no such logical is defined, PWRK$CONFIG selects the first adapter (alphabetically) defined on your system from a list of known adapters.

If the server has access to more than one network adapter, and you do not want to use the adapter selected, or if the system has a network adapter that is not found or recognized by the Advanced Server, you can manually specify the network adapter to use with the transport you specified.

3.11.1 Manually Defining the Network Adapter

To manually define the network adapter to be used for a specific protocol, follow these steps:

1. Use the DCL DEFINE/SYSTEM command to define a system logical name that specifies the network adapter, as shown in the following examples. Table 3-5, OpenVMS Network Adapter Logicals, lists the OpenVMS logical name that you can use for each transport. You must add the appropriate logicals to SYS$MANAGER:SYLOGICALS.COM to have them available after rebooting.
2. Restart the server:

   $ @SYS$STARTUP:PWRK$STARTUP

The following examples show how to define the appropriate network adapter for the DECnet, TCP/IP, and NetBEUI transports, respectively:

• To specify adapter EWA0: for the DECnet transport, enter the following command:

  $ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:

• To specify adapter ESA0: for the TCP/IP transport, enter the following command:

  $ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE ESA0:

  Note If TCP/IP is running on multiple network adapters, and you select one of those adapters for use by the Advanced Server, make sure that the adapter you select for the TCP/IP transport corresponds to the first IP address for the host in the TCP/IP local hosts database (as seen by executing the TCPIP SHOW HOST command). Otherwise, the Advanced Server might use an IP address of a different network interface than that associated with logical PWRK$KNBDAEMON_DEVICE. However, you can now ensure that the Advanced Server uses the IP address of the same interface as defined by logical PWRK$KNBDAEMON_DEVICE by defining the IP address of that interface with the logical PWRK$KNBDAEMON_IPADDR. You no longer need to make sure the selected adapter corresponds to the first IP address in the local hosts database.

• To specify adapter ESA1: for the NetBEUI transport, enter the following command:

  $ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE ESA1:

Note that you can specify the same adapter for each protocol, as in the following example:

$ DEFINE/SYSTEM NETBIOS$DEVICE EWA0:
$ DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE EWA0:
$ DEFINE/SYSTEM PWRK$NETBEUI_DEVICE EWA0:

The NETBIOS, PWRK$KNBDAEMON (for TCP/IP), and PWRK$NBDAEMON (for NetBEUI) processes require that their associated network adapter is known and available to the server software. It is possible that new network adapters are released that are not known to the current version of the Advanced Server software. If the Advanced Server does not find or recognize the selected network adapter, each of the failing processes (NETBIOS, which is always present, and PWRK$KNBDAEMON and PWRK$NBDAEMON, if present) writes an error message to its log file. Table 3-6, Undefined Adapter Messages, shows each process, the log file that records the error message from the process, and examples of the text of the error message. In the examples in Table 3-6, the server node name is MYNODE. All three error messages have the same meaning: that no such device was found by the server.

Tue Mar 24 13:13:50 2000 get_phys_addr: Failed to get Ethernet

device characteristics

Tue Mar 24 13:13:50 2000 Failed to open datalink

%NB-W-ERRSIGNAL, exceptional conditional detected at 24-Mar-2000
13:13:50.00

-SYSTEM-W-NOSUCHDEV, no such device available

If you find any of the messages listed in Table 3-6, define the network adapter for the appropriate processes, using the procedure outlined in Section 3.11.1, Manually Defining the Network Adapter. For example, if the server reported an unknown device, enter the DEFINE/SYSTEM commands to define the appropriate adapter for each protocol on the server.