Consumos (energía,

This is the name of the FTAM responder command file that is to be executed by the OSAKserver upon receiving an inbound FTAM connection request. A responder command file is mandatory. The installation verification procedure (IVP) creates a responder command file for FTAM called

sys$system:osif$responder.com, which you can use in its original form or copy to another file name and adapt to your needs. For example, to research interoperability issues, you might want to modify your osif$responder.comfile to enable tracing only under testing conditions.

10.9.3 OpenVMS User Name

This is the user name of the OpenVMS account in which inbound connections reside. The responder has owner privileges whenever it runs in a user’s account. By default, owner privileges allow complete access to files, which allows the responder to read, write, and delete files. You can restrict these privileges for a given file or directory by using the DCLset protectioncommand.

10.9.4 OpenVMS Login Password

This is the login password associated with the specified user name. If the user’s account is password protected, accessing the FTAM responder requires that both the password and the user name reside in the address database. If the user’s account lacks password protection, omit this parameter from the address database.

10.9.5 OpenVMS Account

This is the OpenVMS account name corresponding to the user name. You can specify an account name for billing purposes. Note that OpenVMS ignores the account name. For information about accounts on OpenVMS systems, refer to the DECnet-Plus management documentation.

10.9.6 Transport Class

The OSI standards define five different protocol classes for the Transport layer. These protocol classes are labeled 0, 1, 2, 3, and 4. OSI Transport implements three transport classes (0, 2, and 4). All three classes are available for negotiation at connection time. The class selected is negotiated based on the classes

supported by the peer user. In negotiation, the highest class supported by both entities is selected.

10.9.7 Transport Options

The transport options that are available to FTAM include checksums, expedited, extended format, and flow control. You can specify any combination of these options. For more information, refer to your DECnet-Plus management documentation.

10.9.8 The FTAM Default Address

Remote file access for FTAM is equivalent to remote file access on a DECnet node. The OpenVMS OSI default account serves the same functions as the DECnet default account. The default name of the OpenVMS OSI default account isosit$default.

On OpenVMS operating systems for Version 5.7 and later, you need a password to access theosit$default account.

10.9 Managing Inbound Addresses

The FTAM IVP creates a default address, rms.ftam.osif., which uses the account osit$default. If this account name is nonexistent on your system, then the default address will not work. The default address has the following information in the address database.

Item Default Value

Address rms.ftam.osif.

Service acse

File sys$system:osif$responder.com

User osit$default1

Password There is no default password

1 _{osit$defaultis the original user name of the OpenVMS OSI default account but the OSI} Transport installer may use a different account. In that case, attempts to use the IVP’s default local application address fail unless it is deleted and recreated with a valid user name and password.

10.9.9 Example of Inbound Address Entry

You can specify inbound FTAM addresses in the OSAK application database with the following commands:

$ ncl create osak application """RMS""/""FTAM""/""OSIF""/NS+,CLNS" $ ncl create osak application """RMS""/""FTAM""/""OSIF""/NS+,CLNS" -

invocation [ap = -1, ae = -1]

$ ncl set osak application """RMS""/""FTAM""/""OSIF""/NS+,CLNS" - invocation [ap = -1, ae = -1] startup information -

"user=OSIT$DEFAULT,file=SYS$SYSTEM:OSIF$RESPONDER.COM"

$ ncl set osak applic """RMS""/""FTAM""/""OSIF""/NS+,CLNS" startup policy To create an address with a NULL PSAP, use the following command: $ ncl create osak application """""/""FTAM""/""OSIF""/NS+,CLNS"

10.9.10 The DAP–FTAM Gateway Default Account

When the DAP–FTAM Gateway (also referred to as the gateway) is installed, the installation procedure creates the gateway account. The name of the default gateway account isosigtwyand the name of the default directory is[OSIF$GTWY].

Account Parameters

When the gateway account is created, several critical flags and UAF (User Authorization File) fields are set by the installation procedure. For the DAP–FTAM Gateway to function effectively, these should not be modified. The specified flags are:

• nocaptive • restricted • defcli • nodisuser • lockpwd • dismail • disctly

10.9 Managing Inbound Addresses

The following table contains the critical values for the UAF fields. Critical UAF Values for the Gateway Account

Field Value

fillm 25

biolm 20

bytlm 20000

wsextent 3072

The FAL Session Control Application

The Network Control Language (NCL) database contains a number of session control applications. One of the objects in the NCL database is the file access listener (FAL), which is the target for requests made by remote nodes. A

command file (sys$system:fal.exe) is associated with the FAL. This file contains the program or procedure used to start the FAL object.

When FTAM is installed, a file (sys$system:osif$gtwy.com) is created which replaces sys$system:fal.exe in the NCL database. The old file name (sys$system:fal.exe) is then assigned to a symbol that is stored in

sys$system:osif$gtwy.com. In the Gateway account’slogin.com, another symbol is assigned to point to sys$system:osif$gtwy.com.

When a request is directed to the Gateway account, the symbol is redefined to execute the DAP–FTAM Gateway image. However, if the incoming request was directed to any other account, the symbol does not get changed and the old file (sys$system:fal.exe) is executed.