![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
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.
The OSI applications installation procedure requires the following hardware:
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.
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:
$ show device device-name [Return]
$ 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.
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.
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.
To install the OSI applications, you must be logged in to an account that has the following privileges:
For FTAM and VT:
For OSAK:
Determine your account privileges as follows:
$ show process/privileges [Return]
$ set default sys$system [Return] $ run authorize [Return] UAF> modify account-name/privileges=(SETPRV) [Return] UAF> exit [Return]
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.
Note
After DECnet-Plus is installed, the release notes file is located in:
- SYS$HELP:DECNET_PLUS-V#_#.RELEASE_NOTES
#_# is the version number of the DECnet-Plus version you are installing.
To install and run the OSI applications, you must have sufficient free global memory. Table 10-1 shows the global memory requirements:
| Software | Alpha | VAX |
|---|---|---|
| FTAM | 5068 global pagelets | 4402 global pages |
| 24 global sections | 19 global sections | |
| VT | 1136 global pagelets | 422 global pages |
| 8 global sections | 14 global sections | |
| OSAK | 3296 global pagelets | 1344 global pages |
| 6 global sections | 13 global sections |
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:
$ write sys$output f$getsyi("contig_gblpages") [Return]
15848
$ write sys$output f$getsyi("free_gblsects") [Return]
24
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.
The POLYCENTER Software Installation utility requires that the installation account has as a minimum the quotas shown in Table 10-2.
| Quota | Value |
|---|---|
| ASTLM | 24 |
| BIOLM | 18 |
| BYTLM | 32768 |
| DIOLM | 18 |
| ENQLM | 200 |
| FILLM | 100 |
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.
| Quota | Value |
|---|---|
| ASTLM | 2 units for each global section + 10 |
| ENQLM | 1 unit for each OSI process |
| TQELM | 2 units for each global section + 10 |
OSAK$SERVER_V3 Process Account Calculation Example
The following calculations determine the correct process account quota values for 20 global sections:
Table 10-4 summarizes the minimum process account quotas required for processes that use the OSAK software.
| Quota | Value |
|---|---|
| ASTLM | 10 |
| ENQLM | 2 |
| TQELM | 10 |
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.
Table 10-5 shows the approximate minimum disk space required to install the individual OSI applications.
| Software | Alpha | VAX |
|---|---|---|
| FTAM | 28,000 blocks | 12,000 blocks |
| VT | 4,000 blocks | 2,000 blocks |
| OSAK | 6,900 blocks | 6,000 blocks |
| TOTAL | 38,900 blocks | 20,000 blocks |
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.
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]
This chapter describes how to install the optional OSI applications. These applications are:
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.
Install the OSI applications only after you have installed DECnet-Plus for OpenVMS, rebooted, and configured the DECnet-Plus for OpenVMS base components.
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:
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.
To install the OSI applications, log into the SYSTEM account and perform the following steps:
$ product remove application [Return]
Note
Refer to the OpenVMS Layered Products Compact Disc User's Guide for instructions on mounting and removing a compact disc.
$ product install ftam,vt/source=device:[directory] [Return]
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 following products have been selected: DEC AXPVMS FTAM V3.2 DEC AXPVMS VT V2.1 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]
*** 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]
%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
*** 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
*** 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
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.
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.
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
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.
PROFILE_011.HTML OSSG Documentation 2-DEC-1996 12:33:40.22
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.