[an error occurred while processing this directive]

HP OpenVMS Systems

Content starts here

HP Advanced Server for OpenVMS
Server Installation and Configuration Guide


Previous Contents Index

7.3.1 Server Configuration Parameters in the OpenVMS Registry

When you are prompted whether to delete the Advanced Server data files:

  • If you respond YES, in addition to deleting the data files (the Advanced Server directory structure and associated files created during installation), the procedure deletes all known Advanced Server keys and values from the OpenVMS Registry.
  • If you respond NO, the procedure creates the following file:
    PWRK$LANMAN:SYS$REGISTRY.LIS
    This file contains a list of all Advanced Server parameters that were in the OpenVMS Registry before removing the Advanced Server. Once the Advanced Server product is removed, PWRK$REGUTL is no longer available for managing Registry parameters. To remove the Advanced Server parameters left in the OpenVMS Registry, use the OpenVMS Registry Control Program (REG$CP.EXE). See the PWRK$LANMAN:SYS$REGISTRY.LIS file to determine which keys and values are to be removed.

7.4 Sample Advanced Server Removal Procedure

This is a sample of the removal procedure for Advanced Server software.


The following product has been selected:
    CPQ AXPVMS ADVANCEDSERVER V7.3B         Layered Product

Do you want to continue? [YES] YES [Return]

The following product will be removed from destination:
    CPQ AXPVMS ADVANCEDSERVER V7.3B         DISK$ALPHAV82:[VMS$COMMON.]

Portion done: 0%...10%...20%

Information about the use of the Advanced Server may have
accumulated in data files.
Delete those files? [NO] YES [Return]

Some portions of Advanced Server may be useful even after
Advanced Server is removed.
Save clean up tools? [YES] NO [Return]

If PCSI provided the image SYS$COMMON:[SYSEXE]NETBIOS.EXE
and does not know of another product also using that image,
then PCSI will remove that image.  It is possible another
program uses that image but PCSI does not know about it.
This procedure can save the image so you can restore it
in case it is needed. Several related files are also saved.
Save a copy of NETBIOS.EXE? [YES] [Return]

The OpenVMS Registry server is already started on this node.

Removing Advanced Server registry parameter and keys
Removing PWRK$DEFAULT and PWRK$GUEST OpenVMS accounts...

Saving Advanced Server for OpenVMS NETBIOS component...
Deleting Advanced Server data files...
Deassigning Advanced Server for OpenVMS logical names...

...30%...40%...50%...60%...70%...80%...90%...100%

The following product has been removed:
    CPQ AXPVMS ADVANCEDSERVER V7.3B         Layered Product


Appendix A
Installation and Upgrade Checklist

Table A-1 summarizes the tasks that you need to perform to install and configure the Advanced Server. You can photocopy this table and use it as a checklist as you read about and complete the tasks in this book.

Table A-1 Installation and Upgrade Checklist
[] 1. Prepare for the installation by completing all preinstallation tasks on the checklist in Section 1.8, Preinstallation Tasks, including the following:
  1. Check the part listing.
  2. Make sure that you have the required hardware.
  3. Log in to the SYSTEM account (or an equivalent account).
  4. Make sure your system has the required software.
  5. Check that OpenVMS registry services are available on the Advanced Server system.
  6. Read the release notes.
  7. Make sure that the system parameters GBLPAGES, GBLSECTIONS, PROCSECTCNT, and SCSNODE are set properly.
  8. Back up the system disks.
  9. Make sure that you have enough disk space to install the software.
  10. Make sure that the queue manager is running.
  11. Check the time zone configuration.
  12. Verify that DECnet (or DECnet-Plus) and TCP/IP, if needed, are running.
  13. Check for existing HP OpenVMS server images and files on the system.
  14. Check OpenVMS Cluster configuration, if installing on a Cluster.
[] 2. Start the installation procedure and respond to installation prompts. You may choose to install the following:
  • The complete Advanced Server
  • The standalone License Server (if you chose not to install the Advanced Server)
  • The standalone external authentication software (if you chose not to install the Advanced Server)
  • Both the standalone License Server and external authentication software (if you chose not to install the Advanced Server)
[] 3. Start the configuration procedure and respond to configuration prompts.
[] 4. Run the Installation Verification Procedure (if you did not do so when you installed the Advanced Server).
[] 5. Start the server (if you did not do so when you configured the Advanced Server).
[] 6. Install Windows NT server administration tools (optional).


Appendix B
Sample Advanced Server Installation and Configuration

This appendix shows sample installation and configuration procedures for the Advanced Server when it is being installed for the first time on the system.

B.1 Sample Advanced Server Installation Procedure

The following example shows a sample installation dialog for the Advanced Server. The installation dialog differs slightly according to circumstances.


$ PRODUCT INSTALL ADVANCEDSERVER/SOURCE=DKA100:[000000]

The following product has been selected:
    CPQ AXPVMS ADVANCEDSERVER V7.3B         Layered Product


Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.

CPQ AXPVMS ADVANCEDSERVER V7.3B: Advanced Server for OpenVMS

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

    Advanced Server is sold by Hewlett-Packard Development Company

    Advanced Server requires PAK PWLMXXXCA07.03 for each client.

    This installation procedure requires that all the following
    conditions are satisfied:
        1.  This procedure is running on an Alpha processor.
        2.  The system is running OpenVMS 7.3-2 or later.
        3.  All required privileges are currently enabled.
        4.  No PATHWORKS or Advanced Server images are running
            on this node or anywhere in the cluster.
        5.  No files from a PATHWORKS (NetWare) kit are present
            on this system disk.
        6.  No files from any Pathworks or Advanced Server kit
            are in SYS$SPECIFIC on this system disk.

        This procedure checks if the conditions are satisfied.
        If they are satisfied, the procedure continues. If not,
        the procedure stops.

Do you want to continue? [YES] [Return]

        Select one of the numbered options:
        1  Install the complete Advanced Server         [default]
        2  Install only the License Server
        3  Install only the external authentication images
        4  Install both the License Server and the
           external authentication images
Option: [1] [Return]
A PCFS driver from a previous kit is currently loaded in memory on
this node.
A PCI driver from a previous kit is currently loaded in memory on
this node.
You must reboot this node before starting the product on this node.
Select an option:
    1. Delay reboot as long as possible on all nodes. [default]
    2. Prevent PWRK$CONFIG configuration on any node using this system
       disk until after reboot.
    3. Prevent PWRK$CONFIG configuration on all nodes until after reboot.
    4. Prevent startup on any node using this system disk until
       after reboot.
    5. Prevent startup on all nodes until after reboot.
Option: [1] [Return]
   User Accounts and User Identification Codes (UICs)
   --------------------------------------------------
    The Advanced Server V7.3B for OpenVMS installation creates two
    OpenVMS accounts:  a default account, PWRK$DEFAULT, and a guest
    account, PWRK$GUEST.  The default UIC group number for both
    these new accounts depends on the following:
    o If you are installing the server for the first time, the
      default is the first unused UIC group number, starting
      with 360.
    o If a PCFS$ACCOUNT already exists, the default is
      the UIC group number associated with PCFS$ACCOUNT.
    o If a PWRK$DEFAULT or PWRK$GUEST account already exists,
      the default is the UIC group number associated with
      PWRK$DEFAULT or PWRK$GUEST, in preference to PCFS$ACCOUNT.
      However, the default UIC group number will not be used to
      change the UIC of any existing accounts.

For more information about UIC group numbers, see the
OpenVMS System Manager's Manual.
Enter default UIC group number for PWRK$DEFAULT and PWRK$GUEST
Group: [360] [Return]
Creating OpenVMS accounts for PWRK$DEFAULT and PWRK$GUEST

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
 CPQ AXPVMS ADVANCEDSERVER V7.3B      DISK$ALPHAV82:[VMS$COMMON.]

Portion done: 0%...10%...20%...30%...40%...70%...90%

To automatically start Advanced Server V7.3B for OpenVMS at
system startup, you should add the following line to the
SYS$MANAGER:SYSTARTUP_VMS.COM file.
$ @SYS$STARTUP:PWRK$STARTUP

Note: Add this line after the lines that start all the network
transports, such as TCP/IP.

To automatically stop Advanced Server V7.3B for OpenVMS at system shutdown,
you should add the following line to the SYS$MANAGER:SYSHUTDWN.COM file.

$ @SYS$STARTUP:PWRK$SHUTDOWN

Note: Add this line before the lines that stop any of the network transports,
such as TCP/IP.

Before starting Advanced Server V7.3B for OpenVMS on this node,
be sure to configure the product (@SYS$UPDATE:PWRK$CONFIG) on each node in the
cluster where the product will run....100%

The following product has been installed:
CPQ AXPVMS ADVANCEDSERVER V7.3B       Layered Product

%PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS ADVANCEDSERVER
V7.3B ...

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

Starting Installation Verification Procedure
for Advanced Server V7.3B for OpenVMS

%PWRK-I-NORMAL, IVP completed successfully
%PCSI-I-IVPSUCCESS, test procedure completed successfully

B.2 Sample Advanced Server Configuration Procedure

The following example shows a sample configuration dialog for the Advanced Server.


$ @SYS$UPDATE:PWRK$CONFIG
Advanced Server V7.3B for OpenVMS Configuration Procedure

    The Advanced Server stores and accesses the following
    types of data files:

    o Configuration parameter files
    o License Server data files
    o Log files
    o Printer spool files
    o Virtual memory section files

    You can specify any existing OpenVMS disk device that has at
    least 150000 free blocks of disk space to store these data files.

    Note: The server frequently accesses the data files stored on
    the disk.  If these files are stored on the system disk, it can
    degrade the performance of both the OpenVMS system and the
    server.  Therefore, HP recommends that you specify a disk
    other than the system disk.

    Enter disk device name where the Advanced Server data files
    will be stored [SYS$SYSDEVICE:]: [return]

    Creating Advanced Server directory tree on SYS$SYSDEVICE:...
    Checking to see if OpenVMS Registry Services are available...
    The OpenVMS Registry server is already started on this node.
    Populating OpenVMS Registry with required Advanced Server & NT
    parameters. Please wait. This may take one to two minutes...
    Required OpenVMS Registry file keys and values have been created.
    Creating Advanced Server directory tree...

    Processing optional client files...

    Do you want to install Windows client utilities, such as
    User Manager for Domains and Server Manager, which can be
    used to manage Advanced Server from a Windows client [N]? [return]

    If necessary, the Windows client utilities and PWUTIL share may be
    installed at any time by executing the command procedure:

    $ @SYS$UPDATE:PWRK$PWUTIL.COM

    The Advanced Server includes a copy of the Windows client
    software necessary to implement client-based licensing.
    If you have or plan to implement server-based licensing only,
    this software is not required on the Windows clients.


    Do you want this server to share the client-based license software  [N]? [return]

    If necessary, the client-based license software can be shared
    from this server at any time by executing the command procedure:
    $ @SYS$UPDATE:PWRK$PWLIC.COM

    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] [return]

    Creating the Monitor user authorization file PWRK$COMMON:PWMONUAF.DAT ...

    Changing the server configuration parameters will allow you to modify
    this server's client capacity and select the transports to be used.

    GRUNT is currently configured to
       + support 50 PC clients
       + use the following transport(s): TCP/IP

   If you want this server to be the primary domain controller, you should
   configure it to use all the transports used by the backup domain
   controllers and member servers in the domain.

   If you want this server to be a backup domain controller or member server,
   you should configure it to have at least one transport in common with the
   domain's primary domain controller, otherwise this configuration will fail.

   If you do not change the configuration parameters now, you may do so
   later by typing ADMIN/CONFIG.

   Do you want to change the server configuration parameters now? [YES]: [return]

   ******** Advanced Server Configuration for node GRUNT ********
   * Options  Help                                              *
   *                                                            *
   * *Server's Client Capacity********************************* *
   * *                                                        * *
   * * ( ) Maximize Client Capacity Using AUTOGEN/Reboot      * *
   * * ( ) Maximize Client Capacity Without AUTOGEN or Reboot * *
   * * (*) User Supplied Client Capacity                      * *
   * *                                                        * *
   * *  Client Capacity: 50                                   * *
   * ********************************************************** *
   *                                                            *
   *   Percent of Physical Memory Used: 80                      *
   *   Data Cache Size (Kbytes): 8192                           *
   *                                                            *
   *   Maximum Concurrent Signons: 10                           *
   *   OpenVMS Process Priority: 9                              *
   *                                                            *
   *  **********  ********  ***************  *****************  *
   *  * Verify *  * Quit *  * Advanced... *  * Transports... *  *
   *  **********  ********  ***************  *****************  *
   *                                                            *
   * Test for supportable configuration *************************

  The OpenVMS Registry server is already started on this node.

  Reading current configuration parameters ...

  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:                   LANGROUP
   6.  Advanced Server role:                     PRIMARY
   7.  Advanced Server computer name:            GRUNT
   7a. Advanced Server OpenVMS cluster alias:    GRUNT-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]: 5 [return]

  An Advanced Server domain is a collection of computers that share
  a common security database and policy.  Each domain has a unique
  name.  A network can have many domains.

  The Advanced Server domain name can be up to 15 characters
  long.  The domain name must be different than the computer name.

  Enter Advanced Server domain name for this system [LANGROUP]: GRUNTDOM

  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:                GRUNTDOM
   6.  Advanced Server role:                  PRIMARY
   7.  Advanced Server computer name:         GRUNT
   7a. Advanced Server OpenVMS cluster alias: GRUNT-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]: [return]

  Saving parameters to the OpenVMS Registry...
  Creating SAM datafiles...
  Creating sharefile PWRK$LMROOT:[LANMAN.DATAFILES]SHAREDB ...
  New sharefile has been created.
  ADMIN$ added
  IPC$ added

  The Advanced Server Administrator account is used to
  administer the server.  The Administrator account
  is mapped by default to the OpenVMS SYSTEM account.

  The Administrator account password can be up to 14 characters
  long and the case of the characters used will be preserved.

  Enter Administrator account password:
  Re-enter to verify password:

  Changing password for Administrator account...

  Setting character set information in databases as needed ...

  Setting share database character set information ...
  Setting ACL database character set information ...
  Checking system resources...

  The current system configuration for GRUNT will support 50 PC clients.
  The Advanced Server is configured to use DECnet, NetBEUI, TCP/IP.

  To automatically start the Advanced Server V7.3B for OpenVMS
  at system startup, you should add the following line to the

  SYS$MANAGER:SYSTARTUP_VMS.COM file.

  $ @SYS$STARTUP:PWRK$STARTUP

  Note: Add this line below the lines that start all network transports
  (such as TCP/IP).

 Do you want to start the Advanced Server V7.3B on node GRUNT now [YES]: [return]
 The file server will use DECnet, NetBEUI, TCP/IP.
 Advanced Server mail notification will use DECnet.
 Process NETBIOS created with identification 00000248
 Process PWRK$NBDAEMON created with identification 0000024A
 Process PWRK$KNBDAEMON created with identification 0000024C
 Process PWRK$LICENSE_R created with identification 0000024E
 Checking to see if the OpenVMS Registry Services are available...
 The Advanced Server is configured to support 20 PC clients.
 Process PWRK$MASTER created with identification 00000251
 The master process will now start all other Advanced
 Server processes.
 $


Previous Next Contents Index