 |
» |
|
|
|
Creates a session on a remote node. Syntax | |
[:envID ] [ {envID }]
DSLINE [:[envID=]nodename][ logon [;DSLINE={[envID=}nodename}]
[envnum ] [ {#Lenvnum }] |
Use | |
Available In Session? Yes |
Parameters | |
- envID
An environment ID—that is, a character
string representing a specific session on a remote node. For NS
names, the environment name itself may optionally be qualified:
envname[.domain[.organization]].
Each portion of the string may have a maximum of 16 alphanumeric
characters (including underscores and hyphens), of which the first
must be alphabetic. The default domain
and organization names are those specified
for your local node when it was configured as part of its NS 3000/iX
network. For ARPA domain names, the environment ID has the syntax
label[.label[...]. The labels must
follow the syntax for ARPANET host names. Refer to ARPA Domain Name
Syntax in Chapter 1 “Introduction to NS 3000/iX” for
more details. If the envID is not equated with
a node name, it must refer to a previously defined environment.
If it is equated to a node name, it then represents a session on
that node. If the nodename is used by
itself, it then becomes its own environment ID, representing a particular
session on that node. If envID, nodename,
and envnum are all omitted in the beginning
of the command line (before HELLO),
the environment information must be given in the ;DSLINE=
option at the end of the command line or the default environment
will be assumed. The default environment for a REMOTE
command is the one most recently referenced in a DSLINE
or REMOTE command.
- nodename
When you are using NS names, the nodename
is the name assigned to the remote node when it is configured into
the NS 3000/iX network. This name may optionally be qualified
in the format node[.domain[.organization]].
The default domain and organization
are those of the local node. Each portion of this string may have
a maximum of 16 alphanumeric characters (including underscores and
hyphens), of which the first must be alphabetic. When you are using
ARPA domain names, the nodename has the syntax label[.label[...].
The labels must follow the syntax for ARPANET host names. Refer
to ARPA Domain Name Syntax in Chapter 1 “Introduction to NS 3000/iX” for more details. An environment ID may be equated with this node name, or the
node name (if used alone) may become its own environment ID. In
either case, the environment ID then represents a specific remote
session on this node. Default: the environment specified by the
last DSLINE or REMOTE command.
- envnum
The number of the environment assigned when the
environment was defined. This is the environment number listed in
the message that appears after a DSLINE command.
Note that when envnum is specified immediately
after REMOTE, envnum
is specified without the #L prefix.
- logon
A valid logon sequence for the remote node, in the
form HELLO user.account[,group].
For information on additional MPE logon parameters and options,
please see the MPE/iX Commands Reference Manual.
- DSLINE=
Defines an environment if one is not specified immediately
after REMOTE. The parameters are
used in the same way as they are after REMOTE
(or as they are used in a DSLINE command).
Examples of REMOTE HELLO | |
The following examples show you the different ways that you
can use the REMOTE HELLO command. The input is
typed at the MPE/iX prompt, and user input is bold for clarity. Method 1 shows that the REMOTE HELLO
command (without environment information) may appear after a DSLINE
command that provides the environment information. Method 1 :DSLINE SYS2
ENVIRONMENT 1: SYS2.DCL.DETROIT
:REMOTE HELLO NSUSER.NSACCT **default environment**
HP3000 / MPE/iX A.01.00 FRI, MAY 1, 1994, 4:13 PM |
Method 2 shows that the environment information
may be included in the DSLINE=
portion of the REMOTE HELLO command. Method 2 :REMOTE HELLO NSUSER.NSACCT;DSLINE=E2=SYS2
HP3000 / MPE/iX A.01.00 FRI, MAY 1, 1994, 4:14 PM
ENVIRONMENT 2: E2.DCL.DETROIT=SYS2.DCL.DETROIT |
Method 3 shows that the environment information
may appear immediately after REMOTE
on the same command line. Method 3 :REMOTE:CHEKHOV
CHEKHOV#HELLO ANTON.PLAYS
HP3000 / MPE/iX A.01.00 FRI, MAY 1, 1994, 4:26 PM |
or :REMOTE:CHEKHOV HELLO ANTON.PLAYS
HP3000 / MPE/iX A.01.00 FRI, MAY 1, 1994, 4:26 PM
ENVIRONMENT 3: CHEKHOV.DCL.DETROIT
:REMOTE **allows use of environment** |
The REMOTE HELLO command may
be issued in two parts, with the HELLO
portion following the remote prompt which is returned. The environment
specification may appear in a previous DSLINE
command, as in method 1, or immediately after the REMOTE,
as in method 3. The DSLINE= option
is not legal in this case, since the DSLINE=
parameter must follow the HELLO
in the REMOTE command line. Methods 4a and 4b show two different ways of accessing
the same node. The DSLINE SYS5 command sets the
attributes of node SYS5 for both
Method 4a and Method 4b. The PROMPT=>>
part of the command shows the effect of setting the prompt on the
remote node. Method 4a shows that the REMOTE
and HELLO commands can be on separate lines.
Method 4b shows that the environment ID is set equal to the node
name in order to create a new session. A fifth environment is created.
Upon returning to the local system, a status line displays the environment
information. Methods 4a and 4b :DSLINE SYS5;PROMPT=>> **DSLINE for Methods 4a and 4b**
ENVIRONMENT 4: SYS5.DCL.DETROIT |
Method 4a :REMOTE **default environment**
>>HELLO NSUSER.NSACCT
HP3000 / MPE/iX A.01.00 FRI, MAY 1, 1994, 4:51 PM |
or Method 4b :REMOTE:MARIE=SYS5 **creates a new session**
MARIE#HELLO NEWUSER.NEWACCT
HP3000 / MPE/iX G.OO.OO FRI, MAY 1, 1994, 4:54 PM
MARIE#:
ENVIRONMENT 5: MARIE.DCL.DETROIT=SYS5.DCL.DETROIT |
|
