![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
The POLYCENTER Software Installation utility does not automatically run the IVP. You must do this manually.
The DCL commands tested by the IVP are:
Before you run the 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.
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.
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.
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
application is FTAM, VT, or OSAK.
This section provides sample OSI applications installations.
$ prod install osak/source=sys$sysdevice:[kits]
The following product has been selected:
DEC AXPVMS OSAK T3.0
Do you want to continue? [YES] [Return]
*** DEC AXPVMS OSAK T3.0: DEC OSAK V3.0 for OpenVMS AXP
Copyright © Digital Equipment Corporation 1994. All rights reserved.
Digital Equipment Corporation
Do you want all the default values for this product? [YES] [Return]
OSAKserver and OSAK network management will be stopped.
Do you want to continue? [YES] [Return]
Do you want to view the values? [NO] [Return]
%PCSIUI-I-DONEASK, execution phase starting
The following product will be installed:
DEC AXPVMS OSAK T3.0
%PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM
-PCSI-I-VOLSPC, 6785 required; 350277 available; 343492 net
Portion Done: 0%...10%...20%...30%...60%...70%...80%...90%...100%
The following product has been installed:
DEC AXPVMS OSAK T3.0
%PCSI-I-EXETSTSTART, start of test procedure
%PCSI-I-EXETSTOK, end of test procedure; completed with no errors
*** DEC AXPVMS OSAK T3.0: DEC OSAK V3.0 for OpenVMS AXP
OSAKserver and OSAK network management processes have been started.
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @sys$startup:osak$start
$ prod install vt/source=sys$sysdevice:[kits]
The following product has been selected:
DEC AXPVMS VT V2.1
Do you want to continue? [YES] [Return]
*** DEC AXPVMS VT V2.1: DECnet-Plus for OpenVMS Virtual Terminal
Copyright (c) Digital Equipment Corporation 1995. 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]
%PCSIUI-I-DONEASK, execution phase starting
The following product will be installed:
DEC AXPVMS VT V2.1
%PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM
-PCSI-I-VOLSPC, 3506 required; 343419 available; 339913 net
Portion Done: 0%...10%...20%...50%...60%...80%...90%...100%
The following product has been installed:
DEC AXPVMS VT V2.1
%PCSI-I-EXETSTSTART, start of test procedure
%PCSI-I-EXETSTOK, end of test procedure; completed with no errors
*** 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
$ product install ftam/source=sys$sysdevice:[kits] [Return]
The following product has been selected:
DEC AXPVMS FTAM V3.2
Do you want to continue? [YES] [Return]
*** 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]
%PCSIUI-I-DONEASK, execution phase starting
The following product will be installed:
DEC AXPVMS FTAM V3.2
%PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM
-PCSI-I-VOLSPC, 27584 required; 423237 available; 395653 net
Portion Done: 0%...10%...20%...30%...40%...50%...80%...90%...100%
The following product has been installed:
DEC AXPVMS FTAM V3.2
*** 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
This section provides sample OSI applications de-installations.
$ product remove vt The following product has been selected: DEC AXPVMS VT V2.1 Do you want to continue? [YES] [Return] The following product will be removed: DEC AXPVMS VT V2.1 %PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM -PCSI-I-VOLSPC, -3436 required; 310692 available; 314128 net Portion Done: 0% %PCSI-I-PRCOUTPUT, output from subprocess follows... %%% VT_RESPONDER is running in process 0000050D %%% Process will be stopped %%% VT_LAT_GTWY is running in process 00000518 %%% Process will be stopped %%% LAT_VT_GTWY is running in process 00000519 %%% Process will be stopped %%% VT_TELNET_GTWY is running in process 0000029E %%% Process will be stopped %%% TELNET_VT_GTWY is running in process 0000029F %%% Process will be stopped Portion Done: 20% Portion Done: 50%...60%...70%...80%...90%...100% The following product has been removed: DEC AXPVMS VT V2.1
$ product remove ftam The following product has been selected: DEC AXPVMS FTAM V3.2 Do you want to continue? [YES] [Return] The following product will be removed: DEC AXPVMS FTAM V3.2 %PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM -PCSI-I-VOLSPC, -27578 required; 314199 available; 341777 net Portion Done: 0%...20%...40%...50%...60%...70%...80%...90%...100% The following product has been removed: DEC AXPVMS FTAM V3.2
$ product remove osak The following product has been selected: DEC AXPVMS OSAK T3.0 Do you want to continue? [YES] [Return] PCSI-E-CONREMUNR, optionally remove product DEC AXPVMS DECNET_OSI T6.3-K3_B that is no longer required by another product Do you want to take this action? [NO] [Return] Do you want to continue? [YES] [Return] The following product will be removed: DEC AXPVMS OSAK T3.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$OVMSSYSTEM -PCSI-I-VOLSPC, -6735 required; 344094 available; 350829 net Portion Done: 0%...20% %PCSI-I-PRCOUTPUT, output from subprocess follows... %%% OSAK$SERVER_V3 is running in process 0000054A %%% Process will be stopped %%% OSAK$NETMAN is running in process 0000054B %%% Process will be stopped Portion Done: 40%...50%...60%...70%...80%...90%...100% The following product has been removed: DEC AXPVMS OSAK T3.0
This chapter describes how to configure FTAM and Virtual Terminal (VT) on an OpenVMS system.
The FTAM and VT applications require you to manage the OSI application entity database. This database stores addressing information for aliases that represent FTAM and VT applications and listeners.
On OpenVMS, the location of this file is:
sys$system:isoapplications.dat
The entries in the isoapplications database define aliases and contain information about local listeners, remote responders, and source addresses for local initiators. The aliases are used by local FTAM and VT initiators and listeners, and by users who specify these aliases in FTAM and VT commands.
There are three types of formats you can use in this isoapplications database. They are:
The isoapplications database can contain any combination of these formats.
For detailed information on the Address, Distinguished Name and Pattern formats, refer to Chapter 9 in DECnet-Plus FTAM and Virtual Terminal Use and Management.
This section provides basic configuration task checklist items and examples for setting up the initiating and responding systems or entities.
Refer to DECnet-Plus FTAM and Virtual Terminal Use and Management for detailed information about managing initiating and responding systems.
If you are already familiar with configuring FTAM and VT, then you can continue the configuration procedure starting at Section 12.4.
On OpenVMS, the FTAM and VT installation and startup procedures provide default FTAM and VT responders. When the vt_start.com and osif$startup.com command procedures are run, these responders are started automatically.
A responding entity needs to be defined in the isoapplications database before you can access it. To get the information you need for an alias, you must contact the person responsible for configuring and managing the remote OSI system running FTAM or VT. The remote FTAM or VT implementation may be from Digital or from another vendor.
Set up the isoapplications database for a specific remote FTAM or VT application as follows:
Once the setup is complete, you can invoke initiator requests using the alias.
Use the task list from Section 12.3.2 to configure your system to perform an FTAM file copy.
In this example, you copy remote file system_a_filename on System-A, to file system_b_filename on System-B.
System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are OpenVMS systems.
Use the OSI provider and the following account information on System-A:
username: system_a_user [Return] password: system_a_pwd [Return]
Use the default FTAM responder on System-A. There is no setup required on System-A.
Using information collected in Section 12.3.2, perform the following steps on initiating entity System-B from a privileged account:
system_a_alias :FTAM:::RMS.FTAM.OSIF. \
%X410004AA000400001321, \
provider=osi,template=default:
After the setup is complete, you can start the FTAM copy command:
$ copy/application=ftam - [Return] system_a_alias"system_a_user system_a_pwd"::system_a_filename - [Return] system_b_filename [Return]
Use the task list from Section 12.3.2 to configure your system to perform a Virtual Terminal login.
In this example, you perform a VT set host/vtp from System-B to System-A.
System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are OpenVMS systems.
Use the RFC 1006 provider and the following account information from System-A:
username: system_a_user [Return] password: system_a_pwd [Return]
Use the default VT responder on responding entity System-A. There is no setup required on System-A.
Using the information from Section 12.3.2, perform the following steps on initiating entity System-B from a privileged account:
system_a_alias :VT:::%x0001.%x0001.%x0002. \
16.20.8.42.102, \
provider=rfc1006:
After the setup is complete, you can start the VT set host/vtp command:
$ set host/vtp system_a_alias [Return] Username: SYSTEM_A_USER [Return] Password: system_a_pwd [Return]
As stated in Section 12.3.1, default FTAM and VT responders are provided on OpenVMS. The installation also supplies an initial isoapplications file with local aliases used by the FTAM and VT responders, gateways, and initiators.
Table 12-1 shows default addresses (PSEL, SSEL, TSEL) for the FTAM and VT responders and gateways:
| Gateway/Responder | Default Address |
|---|---|
| FTAM Responder | RMS.FTAM.OSIF |
| VT Responder | %x0001.%x0001.%x0002 |
| VT/LAT Gateway | %x0001.%x0001.%x0003 |
| VT/TELNET Gateway | %x0001.%x0001.%x0004 |
Each of these responders and gateways can accept connections through all of the transports that FTAM and VT support: OSI transport, RFC 1006, and X.25/CONS.
You can set up your own responder for FTAM in addition to or instead of the default one. You cannot set up your own responder for VT; however, you can change the aliases and change the local addresses (PSEL, SSEL, TSEL) that the VT responder and gateways use. For these operations, refer to DECnet-Plus FTAM and Virtual Terminal Use and Management, Chapter 10 and Chapter 11.
The primary job of configuring FTAM and VT on OpenVMS is to add entries to the isoapplications database for the remote FTAM and VT applications on your network. On OpenVMS, you add entries to isoapplications by using a text editor.
Refer to Chapter 9 in DECnet-Plus FTAM and Virtual Terminal Use and Management for a complete description of managing the isoapplications database.
As mentioned in Section 12.2, every entry in isoapplications has one of three formats:
If you have the DEC X.500 Directory Service product installed, you have the option of adding entries of the Distinguished Name format and the Pattern format. You have the option of adding entries of the Address format regardless of whether X.500 is installed.
If you are not using X.500, complete an Address Format Worksheet in Table 12-3 for each remote application. If you are using X.500, complete the checklist in Table 12-2.
To complete the Address Format Worksheet forms, see Section 12.3.2 for collecting relevant information.
| Question | Yes | No |
|---|---|---|
|
Do you want to register the local listeners in the X.500
Directory?
If yes, you need an X.500 Distinguished Name to identify each of the local listeners. Specify a Distinguished Name for each local listener.
|
[] | [] |
|
isoapplications
isoapplications
?
If yes, then continue on with this checklist to add entries of the Distinguished Name, Pattern, and Address formats. |
[] | [] |
|
Do you want to add entries of the Distinguished Name
format?
If yes, complete the following information for each remote application:
|
[] | [] |
|
Do you want to add entries of the Pattern format?
If yes, you need to determine what your pattern(s) should look like. You may be able to get this information from your network administrator, or you may be able to use the DEC X.500 Administration Utility (DXIM) to examine the structure of the X.500 Directory Information Tree for your organization to determine what your Pattern format entries should be. Complete the following information for each pattern entry. The Distinguished Name should be incomplete (contain at least one *).
|
[] | [] |
|
Do you want to add entries of the Address format?
If yes, complete a form in Table 12-3 for each remote application. |
[] | [] |
PROFILE_012.HTML OSSG Documentation 2-DEC-1996 12:33:41.92
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.