HP OpenVMS Systems Documentation

DECnet-Plus for OpenVMS
Applications Installation and Advanced Configuration

Contents

Index

Chapter 11
Installing the OSI Applications

This chapter describes how to install the optional OSI applications. These applications are:

FTAM
Virtual Terminal (VT)
OSAK

It also includes how to list the files installed on your system during the OSI applications installation. See Section 11.11 for the list of commands.

You install these optional components using the POLYCENTER Software Installation utility. For information about how to run the this utility, refer to DECnet-Plus for OpenVMS Installation and Basic Configuration, Appendix A.

11.1 Prerequisite Steps

Install the OSI applications only after you have installed DECnet-Plus for OpenVMS, rebooted, and configured the DECnet-Plus for OpenVMS base components.

11.2 Register the OSI Applications Software License

If you are installing prerequisite or optional software along with OSI applications, review the PAK status and install the PAKs for any prerequisite or optional software before you install the OSI applications.

The DVNETEND PAK is required to install DECnet-Plus. This PAK also allows you to install and run the base FTAM, VT, and OSAK applications.

To use the FTAM and VT gateways, you need the extended function license. The PAK names are:

For Alpha: DVNETEXT
For VAX: DVNETRTG

11.3 Starting the Installation of the OSI Applications

You install the OSI applications using the POLYCENTER Software Installation DCL interface.

For a description of all the features you can request when starting an installation (such as purging files and using a product configuration file), refer to DCL help for the product install command.

To install the OSI applications, choose from the following commands.

For OSAK only:

$ product install osak /source=DKA400:[kits]

For FTAM and VT:

$ product install ftam,vt /source=DKA400:[kits]

For FTAM only:

$ product install ftam /source=DKA400:[kits]

For VT only:

$ product install vt /source=DKA400:[kits]

If you do not use the /SOURCE qualifier, the default is to read the installation kit from PCSI$SOURCE:.

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

Details on determining the directory location of the OSI applications kit are provided in Section 9.4.

11.4 Installing the OSI Applications

To install the OSI applications, log into the SYSTEM account and perform the following steps:

If you have previously installed the OSI applications on your system, be sure to shut down any FTAM, VT, or OSAK processes currently running by executing the appropriate shutdown procedures(s).
You must shut down FTAM and VT first, before shutting down OSAK.
- $ @sys$startup:osif$stop
- $ @sys$startup:vt_stop
- $ @sys$startup:osak$stop
De-install the OSI applications.
If you have previously installed the OSI applications on your system, then de-install the applications, using the product remove command:
$ product remove application [Return]
application is FTAM, VT, or OSAK.
Note that you must de-install FTAM and VT before de-installing OSAK.
Mount the software CD-ROM.

Note
Refer to the OpenVMS Layered Products Compact Disc User's Guide for instructions on mounting and removing a compact disc.
Decide which products to install. You must install OSAK before installing FTAM or VT. You can install FTAM and VT either together or separately.
See Section 11.3 for the FTAM, VT, and OSAK installation commands.
To install FTAM and VT together, type:
$ product install ftam,vt/source=device:[directory] [Return]
device:[directory] is the location of the files on the distribution media.

Note
The following code examples are from an Alpha installation. A VAX installation varies slightly in the PAK name and in disk space requirements.
The POLYCENTER Software Installation utility displays the selected products and requests confirmation. Press Return to continue, or enter NO to exit.
The following products have been selected: DEC AXPVMS FTAM V3.2 DEC AXPVMS VT V2.1 Do you want to continue? [YES] [Return]

The POLYCENTER Software Installation utility displays the pre-installation messages for FTAM including the copyright notice, license notice, and OSAK notice, and asks if you want to continue.

*** DEC AXPVMS FTAM V3.2: DECnet-Plus for OpenVMS OSI File Transfer,
Access, and Management (FTAM)

    Copyright (c) Digital Equipment Corporation 1995. All rights reserved.

    This product uses the PAKS: DVNETEND and the Gateway requires DVNETEXT.

    The DECnet-Plus OSAK software must be installed and started before
 continuing this installation.
    Do you want to continue? [YES] [Return]

The POLYCENTER Software Installation utility displays the pre-installation messages for VT including the copyright notice, license notice, OSAK notice, and gateway notice, and asks if you want to continue.

*** DEC AXPVMS VT V2.1: DECnet-Plus for OpenVMS Virtual Terminal

    Copyright (c) Digital Equipment Corporation 1994. All rights reserved.

    VT requires the PAK DVNETEND, and the VT Gateways require DVNETEXT also.

    OSAK must be installed and started before continuing this installation.

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

    VT Gateways startup requires LAT and DEC TCP/IP Services started first.
    Do you want to continue? [YES] [Return]

The POLYCENTER Software Installation utility enters the execution phase, in which it installs the products, executes the startup command files, and runs the VT installation verification procedure (IVP). Note that the FTAM IVP is not run during this installation, and must be run separately.

%PCSIUI-I-DONEASK, execution phase starting
The following products will be installed:
DEC AXPVMS FTAM V3.2
DEC AXPVMS VT V2.1
%PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM
-PCSI-I-VOLSPC, 31060 required; 484479 available; 453419 net
Portion Done: 0%...10%...20%...30%...40%...70%...80%...90%...100%
The following products have been installed:
DEC AXPVMS FTAM V3.2
DEC AXPVMS VT V2.1
%PCSI-I-EXETSTSTART, start of test procedure
%PCSI-I-EXETSTOK, end of test procedure; completed with no errors

The POLYCENTER Software Installation utility displays the post-installation messages for FTAM and lists required system resources, configuration and IVP tasks you must complete, release notes location, and completion message.

*** DEC AXPVMS FTAM V3.2: DECnet-Plus for OpenVMS OSI File Transfer,
Access, and Management (FTAM)

    Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
        @SYS$STARTUP:OSIF$STARTUP.COM
    Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
        @SYS$STARTUP:OSIF$STOP.COM

    The following messages are informational and indicate the amount of
each resource used by FTAM.

    This product requires the following SYSGEN parameters:
        GBLSECTIONS add 24

    This product requires the following SYSGEN parameters:
        GBLPAGES add 5068

    After installing DECnet-Plus FTAM you must do
"$ @SYS$STARTUP:OSIF$CONFIGURE.COM" to setup necessary accounts.

    The DECnet-Plus FTAM IVP may be run at any time by doing
"$ @SYS$TEST:OSIF$IVP.COM"


    Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES

    DECnet-Plus for OpenVMS FTAM Installation Completed

The POLYCENTER Software Installation utility displays the VT post-installation messages and lists release notes location, and completion message.

*** DEC AXPVMS VT V2.1: DECnet-Plus for OpenVMS Virtual Terminal

    Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
        @SYS$STARTUP:VT_START.COM
    Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
        @SYS$MANAGER:VT_STOP.COM

    Previous VT_SYSTART.COM changes are in SYS$STARTUP:VT_SYSTART.COM_OLD

    Release notes are available in SYS$HELP:DECNET*.RELEASE_NOTES

    DECnet-Plus for OpenVMS Virtual Terminal Installation Completed

11.5 Starting Up and Shutting Down OSI Applications

The installation procedure for each OSI application executes the startup procedure automatically.

To enable automatic restart of the applications once you have installed them on your system, edit the system startup file (sys$manager:systartup_vms.com) and add the following command lines to the file, beginning with the OSAK command:

$ @sys$startup:osak$start.com ! OSAK startup command file
$ @sys$startup:osif$startup.com ! FTAM startup command file
$ @sys$startup:vt_start.com ! VT startup command file

See Section 11.4, Step 1, for instructions on shutting down the OSI applications.

11.6 The OSAK Installation Verification Procedure

The OSAK installation verification procedure (IVP) is run automatically during the installation. However, you can run it at any time by entering the following command:

$ @sys$test:osak_ivp

If the IVP runs successfully, you see the following:

Starting OSAK Installation Verification Procedure ...
OSAK Installation Verification Procedure completed successfully

If the IVP finishes with errors, you see a message similar to this:

OSAK Installation Verification Procedure completed with errors

In both cases, the OSAK software produces a log file called OSAK$IVP.LOG in the default directory, SYS$TEST. If the IVP fails during installation, you can check the log file to help you identify the source of the problem. You can also forward the log file to DIGITAL to assist you when discussing the problem.

When you have finished running the IVP and you are sure that the OSAK software is properly installed, back up the system disk. Save the distribution kit for future installations.

11.7 Running the OSIF$CONFIGURE.COM Procedure

Following the FTAM POLYCENTER Software Installation utility installation, you should execute the osif$configure.com procedure located in SYS$STARTUP. This procedure first verifies the existence of the OSIT$DEFAULT and OSIGTWY accounts, then asks whether you want to run the installation verification procedure (IVP).

If the procedure finds that either of the OSIT$DEFAULT and OSIGTWY accounts are not present, the procedure creates the account(s) and prompts for user input. The IVP question is asked whether or not it was necessary to create accounts.

Following is an example of running the script on a system where the accounts already exist:

$ @sys$startup:osif$configure.com
  This setup procedure will verify the existence of the OSIT$DEFAULT
  and OSIGTWY accounts.  If these accounts are not present, you will
  be asked some questions about UIC and default device, as well as
  being required to choose passwords from a computer generated list.

  Do you wish to continue with this procedure [Yes] :



  The OSIT$DEFAULT and OSIGTWY accounts are present.  The OSIT$DEFAULT
  account is useful as an account to specify when running the DECnet-Plus
  FTAM IVP.  The OSIGTWY account is the mechanism by which users may access
  the DAP/FTAM Gateway.  For more information about this Gateway, see the
  FTAM Use and Management Guide.


  DECnet-Plus FTAM setup complete.


  Would you like to run the IVP [Yes] : No

11.8 The FTAM Installation Verification Procedure

You can verify the FTAM installation by running the FTAM installation verification procedure (IVP). The IVP is an internal test of the FTAM initiator and responder using the underlying OSI layers of the local system through the Network layer. This testing verifies that your installation can set up and accept an application association and its underlying presentation and session connections. The IVP tests the FTAM DCL commands on the local system and also exercises the DAP-FTAM Gateway.

The POLYCENTER Software Installation utility does not automatically run the IVP. You must do this manually.

The DCL commands tested by the IVP are:

COPY/APPLICATION_PROTOCOL=FTAM
DIRECTORY/APPLICATION_PROTOCOL=FTAM
DELETE/APPLICATION_PROTOCOL=FTAM
RENAME/APPLICATION_PROTOCOL=FTAM

11.8.1 Preparing for the FTAM IVP

Before you run the IVP:

Ensure that the OSI transport is running and enabled. It will be running if you answered YES to the "Configure Transport?" question during the net$configure procedure.
If you are running the IVP for the first time, be sure to run the OSIF$CONFIGURE.COM beforehand. Instructions on running this procedure are in Section 11.7. The last question in the procedure asks if you want to run the IVP. To do so, type YES and press [Return].

11.8.2 Running the FTAM IVP

You can issue the IVP commands from any directory on the system. The IVP prompts you for an account and the corresponding password. The OSIT$DEFAULT account is a reasonable choice since it will be configured correctly. However, you may specify any valid account and password.

$ @sys$test:osif$ivp.com

  DECnet-Plus FTAM Installation Verification Procedure

  It is 20-APR-1995 at 10:50.

  The DECnet-Plus FTAM IVP assigns the LOCAL_FTAM alias to be:

          :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:

  The DECnet-Plus FTAM IVP copies a small data file, SYS$TEST:OSIF$IVP.TMP,
  to LOCAL_FTAM::OSIFILE.TMP. The IVP requests a directory listing
  of the new file, before copying it back to SYS$LOGIN:OSIF$IVP.CPY.
  Next, the IVP requests a difference of the original file,
  SYS$TEST:OSIF$IVP.TMP, and the second new file, SYS$LOGIN:OSIF$IVP.CPY.
  The LOCAL_FTAM::OSIFILE.TMP file, that was originally copied is then
  renamed to LOCAL_FTAM::OSIFILE.RNM. The IVP then deletes the two
  new files.

  To perform these actions, a valid username and password with
  the following privileges must be supplied by the user:

          NETMBX, TMPMBX, SYSNAM, SYSLCK, PRMMBX

Please enter the USERNAME for use by the IVP: osit$default

Please enter the PASSWORD for use by the IVP:

  $ COPY /APPLICATION_PROTOCOL=FTAM /LOG SYS$TEST:OSIF$IVP.TMP
    LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP

%COPY-S-COPIED, SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1 copied to
:::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT password"::
SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1 (403 records)

  $ DIRECTORY /APPLICATION_PROTOCOL=FTAM -
    LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP

Directory :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:::
   "OSIT$DEFAULT password"

SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1

Total of 1 file.

  $ COPY /APPLICATION_PROTOCOL=FTAM /LOG -
    LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP -
    SYS$LOGIN:OSIF$IVP.CPY

%COPY-S-COPIED, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT
password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1 copied
 to DKA100:[SMITH]OSIF$IVP.CPY;8 (403 records)

  $ DIFFERENCE SYS$TEST:OSIF$IVP.TMP SYS$LOGIN:OSIF$IVP.CPY
Number of difference sections found: 0
Number of difference records found: 0

DIFFERENCES /IGNORE=()/MERGED=1-
   SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1-
   DKA100:[SMITH]OSIF$IVP.CPY;8

  $ DELETE/LOG SYS$LOGIN:OSIF$IVP.CPY;

  $ RENAME /APPLICATION_PROTOCOL=FTAM /LOG -
    LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.TMP -
    OSIFILE.RNM
%RENAME-I-RENAMED, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:
   "OSIT$DEFAULT password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.TMP;1
   renamed to OSIFILE.RNM

  $ DELETE /APPLICATION_PROTOCOL=FTAM /LOG -
    LOCAL_FTAM"OSIT$DEFAULT password"::OSIFILE.RNM
%DELETE-I-FILDEL, :::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:
"OSIT$DEFAULT password"::SYS$COMMON:[OSIT$DEFAULT]OSIFILE.RNM;1
deleted (0 blocks)


Would you like to test the DAP Gateway (this requires the OSIGTWY password)? Y


  Checking SYS$SYSTEM:ISOAPPLICATIONS.DAT for OSINOD...


Please enter the PASSWORD for the OSIGTWY account:


  $ COPY /APPLICATION_PROTOCOL=FTAM /LOG SYS$TEST:OSIF$IVP.TMP
    LOCAL_FTAM"OSIT$DEFAULT password"::GTWYFILE.TMP

%COPY-S-COPIED, SYS$COMMON:[SYSTEST]OSIF$IVP.TMP;1 copied to
:::RMS.FTAM.OSIF.%x21,template=osit$loop_clns:"OSIT$DEFAULT password"::
SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1 (403 records)

  $ DIR 0"OSIGTWY password"::OSINOD"OSIT$DEFAULT password"::
      SYS$LOGIN:GTWYFILE.TMP

Directory 0"OSIGTWY password"::

OSINOD"OSIT$DEFAULT OSIT$DEFAULT"::SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1
                          24  20-APR-1995 10:53:47.00  (RWED,RWED,RWED,RWED)

Total of 1 file, 24 blocks.

  $ DELETE /LOG 0"OSIT$DEFAULT password"::GTWYFILE.TMP;
%DELETE-I-FILDEL, 0"OSIT$DEFAULT
password"::SYS$COMMON:[OSIT$DEFAULT]GTWYFILE.TMP;1 deleted (24 blocks)

  DECnet-Plus FTAM Installation Verification Procedure
  completed successfully at 10:53.

11.9 The VT Installation Verification Procedure

The VT installation verification procedure (IVP) is run automatically during the installation. However, you can run it at any time by entering the following command:

$ @sys$test:vt_ivp

If the IVP ran successfully, you see the following:

VT_IVP: Test successful

%IVP-S-END, IVP ended

If the IVP finishes with errors, you see a message similar to this:

VT_IVP: <Failure message>

%IVP-S-END, IVP ended

In both cases, the VT software produces a log file called VT_IVP.LOG in the SYS$SCRATCH directory. You can check the log file to help you identify the source of the problem. You can also forward the log file to DIGITAL to assist you when discussing the problem.

11.10 De-installing OSI Applications

To de-install the OSI applications, you must be logged into an account with the same privileges required to install the OSI applications. See Section 10.2 for this list of privileges.

You may optionally shut down the OSI applications before de-installing them. See Section 11.4 for instructions.

Note that you must de-install FTAM and VT before you de-install OSAK.

To de-install any of the OSI applications, enter the command:

$ product remove application

application is FTAM, VT, or OSAK.

Invoking this command shuts down the application if it is running and removes the product files. An example of the de-installation response sequence for each application is provided in Section 11.13.

Note

You do not have to remove a product before re-installing the same version, or installing a different version. If the product is already installed on the system, the POLYCENTER Software Installation utility removes it automatically before beginning the installation.

11.11 Files Installed on Your System

The OSI applications installation procedure installs a number of files on your system. To list the files, enter the following command:

$ product show object /product=application