Using NS3000/iX Network Services (36920-90008)

Chapter 3 61

Remote File Access

RFA/RDBA Automatic logon

A REMOTE HELLO is no longer necessary before using RFA. This is

useful if your system does not support the Virtual Terminal service.

Overview

RFA requires a remote session when accessing or creating remote ﬁles

to provide the ﬁle system security of the remote user. This session is

referred to as an “environment.” An environment is identiﬁed by either

a DSLINE environment ID that refers to a VT session, or by a logon string

that automatically creates a remote session. RFA will use an existing

session established by VT before a session is automatically logged on. If

a session already exists, and a logon string is speciﬁed, the logon string

will be ignored. The user is responsible for supplying RFA with an

environment to operate within.

How to Use the Automatic Logon Feature

RFA automatically creates its session by using the logon sequence

speciﬁed in the LOGON option of the DSLINE command. At the MPE/iX

prompt, type:

DSLINE nodename; LOGON=user.acct,group

If a remote session does not exist, and a DSLINE LOGON string has been

speciﬁed, then this logon string will be used to automatically log on a

remote session for an RFA FOPEN. Whenever RFA logs on a remote

session, it will also log it off after all ﬁles in that session have been

closed.

Remote Hello After RFA Automatic Logon

One may still establish a remote VT session using a common DSLINE

environment after RFA has automatically logged on its own remote

session under the same DSLINE environment. VT commands will not be

executed under a session created automatically by RFA. A session

created automatically by RFA will be recognized by VT. All RFA will be

performed under RFA’s session and all VT will be performed

independently under the VT session. Since these two sessions are

independent, they may be established under different user/account

names.

RFA/RDBA Autologon Example

Suppose you were to issue the command DSLINE NODE1;LOGON=

user1.acct1, and then open a remote ﬁle on NODE1. The FOPEN logs on a

remote session on NODE1 under user1.acct1.