HP OpenVMS Systems Documentation

* Do you want to generate NCL configuration scripts?   [YES] :
%NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by NET$CONFIGURE
%NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$APPLICATION_STARTUP.NCL; was not replaced
%NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$EVENT_STARTUP.NCL; was not replaced
%NET$CONFIGURE-I-NOTREPLACED, SYS$SYSROOT:[SYSMGR]NET$MOP_CLIENT_STARTUP.NCL; was not replaced
* Do you want to start the network?                    [YES] :
Copyright (c) Digital Equipment Corporation 1993, 1995. All rights reserved.
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING-ALL

sys$manager:net$dns_clerk_startup.ncl changed to use the new default namespace.

Your default namespace nickname is BB_NS.

Your default namespace NSCTS is 08-00-2B-17-F4-BC-F5-B2-38-FB-C4-7B-96-00.
%NET$CONFIGURE-I-FLUSHCACHE, flushing selected cache entries

Node 0
at 1995-01-23-15:32:52.583-05:00Iinf

%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to bb_ns:.area39.arv011

Node 0 Session Control
at 1995-01-23-15:32:52.906-05:00Iinf


Node 0 Session Control
at 1995-01-23-15:32:52.918-05:00Iinf


Node 0 Session Control
at 1995-01-23-15:32:52.926-05:00Iinf


Node 0 Session Control
at 1995-01-23-15:32:54.427-05:00Iinf


Node 0 Session Control
at 1995-01-23-15:32:54.545-05:00Iinf

Characteristics

    Maintain Backward Soft Links      = True

                     SHOW
                DIRECTORY  BB_NS:.area39
                       AT  23-JAN-1995:15:32:55
                  DNS$CTS = 1993-02-06-16:50:34.908990700/08-00-2b-17-f4-bc

Directory Service: DECdns

Node name:         BB_NS:.AREA39.ARV011
Phase IV synonym:  ARV011

Address tower protocol and selector values:
  Session:   DNA_SessionControlV3 (SC3)
             00 13
  Transport: DNA_OSItransportV1 (TP4)
             DE C0
  Routing:   DNA_OSInetwork (CLNS)
             47:0027:00-27:AA-00-04-00-0B-9C:21 (39.11)

  Session:   DNA_SessionControlV3 (SC3)
             00 13
  Transport: DNA_NSP (NSP)
             (no selector value)
  Routing:   DNA_OSInetwork (CLNS)
             47:0027:00-27:AA-00-04-00-0B-9C:20 (39.11)

  Session:   DNA_SessionControlV3 (SC3)
             00 13
  Transport: DNA_OSItransportV1 (TP4)
             DE C0
  Routing:   DNA_OSInetwork (CLNS)
             47:0027:00-5E:08-00-2B-E4-54-1C:21

  Session:   DNA_SessionControlV3 (SC3)
             00 13
  Transport: DNA_NSP (NSP)
             (no selector value)
  Routing:   DNA_OSInetwork (CLNS)
             47:0027:00-5E:08-00-2B-E4-54-1C:20

Synonym softlink name:
    BB_NS:.DNA_NodeSynonym.ARV011

Reverse address mapping (backtranslation) softlink names:
    BB_NS:.DNA_BackTranslation.%X470027.%X0027.%XAA0004000B9C
    BB_NS:.DNA_BackTranslation.%X470027.%X005E.%X08002BE4541C


Number of nodes reported on:  1

%NET$CONFIGURE-I-NODEISREG, node is already registered in the DECdns directory
service

Node 0
at 1995-01-23-15:32:56.524-05:00Iinf

%NET$CONFIGURE-I-NODERENAMED, node successfully renamed to bb_ns:.area39.arv011

Node 0 Session Control Tower Maintenance BB_NS:.AREA39.ARV011
at 1995-01-23-15:32:56.699-05:00Iinf

%NET$CONFIGURE-I-TOWERSUPDATED, updated address towers for node

Node 0 Session Control Backtranslation Softlink *
at 1995-01-23-15:32:56.823-05:00Iinf


Node 0 Session Control Backtranslation Softlink *
at 1995-01-23-15:32:56.823-05:00Iinf

%NET$CONFIGURE-I-BCKTRNUPDATED, updated backtranslation softlink for node
%NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

        Configuration Options:

        [0]     Exit this procedure

        [1]     Perform an entire configuration
        [2]     Change node name/namespace name
        [3]     Configure Devices on this machine
        [4]     Configure Transports
        [5]     Configure Timezone Differential Factor
        [6]     Configure Event Dispatcher
        [7]     Configure Application database
        [8]     Configure MOP Client database
        [9]     Configure Cluster Alias
        [10]    Replace MOP Client configuration
        [11]    Configure satellite nodes
        [12]    Configure cluster script locations

* Which configuration option to perform?                 [0] :

Part IV describes the steps necessary to plan, install, and configure the OSI applications for OpenVMS Alpha and VAX systems. It includes the following chapters:

• Chapter 9 --- Planning for the Installation
• Chapter 10 --- Preparing to Install the OSI Applications
• Chapter 11 --- Installing the OSI Applications
• Chapter 12 --- Configuring the OSI Applications

FTAM

FTAM is an Open Systems Interconnection (OSI) product that implements the OSI File Transfer, Access, and Management standard ISO 8571 developed by the International Organization for Standards (ISO). Using FTAM, you can copy, append, delete, rename, and inspect the file attributes of local files, remote files, or both.

Virtual Terminal

DECnet-Plus Virtual Terminal is DIGITAL's implementation of the OSI Virtual Terminal standard. Virtual Terminal (VT) enables applications and systems supporting different types of terminals to interoperate with each other. Using VT, you can use your terminal to access any other system running VT, regardless of the type of system. You can also use the VT gateways for access to and from non-OSI systems.

OSAK

Open System Application Kernel (OSAK) is DIGITAL's implementation of the OSI upper layers. It provides OSI Session, Presentation and Application services. These services are used by OSI applications such as FTAM, VT, X.400, and X.500. In addition, by using the OSAK programming interfaces which provide access to OSI Session, Presentation and Application layers, users can develop applications that layer on DIGITAL's implementation of the OSI stack.

9.2 Required Hardware

The OSI applications installation procedure requires the following hardware:

• A CD reader (if installing an Alpha version)
• A CD reader, magnetic tape drive, or TK50 tape drive (if installing a VAX version)
• A terminal
  You can use either a hard copy or video terminal to communicate with the operating system and respond to prompts from the installation procedure.

You must use the POLYCENTER Software Installation utility to install the OSI applications installation kit. This utility is provided as part of the operating system software.

To install FTAM and VT, you must first install DECnet-Plus, and then install OSAK.

To run the VT/Telnet gateways, you must have the DIGITAL TCP/IP Services for OpenVMS installed on your system.

9.4 Kit Location

To obtain the directory location of the OSI applications kit on the CD, refer to the OpenVMS Layered Products Compact Disc User's Guide that accompanies the CD distribution kit, or before starting installation, complete the following steps:

1. To determine whether the CD drive is already mounted, enter the following command:

   $ show device device-name [Return]

2. If it is not mounted, enter the appropriate MOUNT command to mount the CD.
3. To obtain the save-set name, use a DIRECTORY command specifying the device name from the previous command. For example:

   $ directory DKA400:[kits]*.pcsi [Return]

If you are installing from a TK50 or magnetic tape drive, refer to the appropriate user guide for further instructions.

9.5 Time Required to Install

The time required to install the OSI applications depends on the media type, the CPU type, and your system configuration. In general, the procedure should require less than 15 minutes.

This chapter details the tasks you need to complete or consider before attempting to install the OSI applications.

10.1 Inspecting the Distribution Kit

The software bill of materials (BOM) included with your distribution kit shows the components of the kit. Compare the items you received against the BOM. Report any damaged or missing components to DIGITAL before continuing with the installation.

10.2 Logging In to a Privileged Account

To install the OSI applications, you must be logged in to an account that has the following privileges:

For FTAM and VT:

• SETPRV

For OSAK:

• CMKRNL
• SETPRV

Determine your account privileges as follows:

1. Determine the default privileges of the installing account. Log in and enter the DCL command:

   $ show process/privileges [Return]

   
   If the account lacks the SETPRV privilege, proceed to Step 2.
2. Do either of the following:
   • Ask your system manager to use the Authorize utility to modify the default privileges of the account to include the SETPRV privilege
   • Run the Authorize utility and make the changes yourself, if your account has the SYSPRV privilege:

     $ set default sys$system [Return] $ run authorize [Return] UAF> modify account-name/privileges=(SETPRV) [Return] UAF> exit [Return]

3. To activate the change in privileges, log out and then log in again.

The release notes for the OSI applications are provided as part of the DECnet-Plus release notes. You should review these release notes prior to installation because they describe new features and differences among multiple versions, as well as changes to the installation procedure.

To access the release notes, issue the command:

$ product extract release_notes -
    decnet_osi/source=DKA400:[kits]/file=filename [Return]

Note that in this example, the directory on the CD in which the installation kit is located is referred to as DKA400:[kits]. You should substitute this directory name with the actual directory location of your DECnet-Plus kit.

The product selected is displayed and you are prompted whether to continue with the extraction.

To extract the release notes, type YES and press Return. The release notes are written to the specified file, which you can display or print.

To cancel the extraction, type NO and press Return.

To install and run the OSI applications, you must have sufficient free global memory. Table 10-1 shows the global memory requirements:

You must first find out your available system resources, and then use the AUTOGEN utility if you need to increase the global pages, global pagelets, or global sections system parameters. Do this as follows:

1. Use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT):

   $ write sys$output f$getsyi("contig_gblpages") [Return] 15848 $ write sys$output f$getsyi("free_gblsects") [Return] 24

2. Compare the values displayed with those required for the OSI applications.
   • If the values displayed by the system are greater than the values required for the OSI applications, you do not need to change the system parameter settings.
   • If one of the values is less than the value required for OSI applications, you must increase the system parameter setting using the AUTOGEN utility. Proceed to the next section.

Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually.

For more information about using the AUTOGEN utility, refer to your OpenVMS system management documentation.

10.5 Process Quotas

The POLYCENTER Software Installation utility requires that the installation account has as a minimum the quotas shown in Table 10-2.

The number of available global sections on the system limits the number of simultaneous connect requests that the OSAK software can support. OSAK buffers store each connect request in a global section until the intended application has either accepted or rejected it, or does not accept an inbound connection within a given period, in which case the OSAK software rejects the connection on behalf of the application. The process running the OSAK software, OSAK$SERVER_V3, is started automatically by the installation procedure. Therefore, the installing account requires the process quotas shown in Table 10-2, as does the SYSTEM account if you start OSAK$SERVER_V3 in SYSTARTUP_VMS.COM.

Table 10-3 summarizes the required process account quotas for the OSAK$SERVER_V3 process.

OSAK$SERVER_V3 Process Account Calculation Example

The following calculations determine the correct process account quota values for 20 global sections:

• For ASTLM: 20 global sections multiplied by 2 units + 10 = 50
• For TQELM: 20 global sections multiplied by 2 units + 10 = 50

Table 10-4 summarizes the minimum process account quotas required for processes that use the OSAK software.

Users of the OSI applications also need a minimum TMPMBX and NETMBX privileges.

Use the OpenVMS Authorize utility to verify and change process quotas and user privileges for the installation and user accounts in the user authorization file (SYSUAF.DAT). (Some sites may restrict the use of the OpenVMS Authorize utility to certain accounts or users.)

After you have changed the quotas for the installation account, log out of the installation account and log in again for the new quotas to take effect.

For more information on modifying account quotas, refer to the description of the Authorize utility in the OpenVMS system management documentation subkit.

10.6 Determining Disk Space

Table 10-5 shows the approximate minimum disk space required to install the individual OSI applications.

To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt:

$ show device sys$sysdevice [Return]

If necessary, create enough free disk space to accommodate the installation of the OSI applications.

Chapter 7 describes options the POLYCENTER Software Installation utility provides, if there is insufficient disk space to complete the OSI applications installation.

10.7 Notifying Users

You may want to notify the users on the system that you are installing the OSI applications. Log in to an account that has OPER privileges.

The command is:

$ reply/all/bell "Now installing the OSI applications" [Return]