Using NS3000/iX Network Services (36920-90008)

Chapter 2 27
Virtual Terminal
DSLINE Command
For further information on tracing, see the NS 3000/iX
Operations and Maintenance Reference Manual.
NOTE The following dslineoptions are obsolete and are ignored in all cases (if
used, a warning message is printed): EXCLUSIVE, FROMADDR=,
FROMADR=, LINEBUF=, LOCID=, NOQUEUE, OPEN, PHNUM=, QUEUE,
REMID, SELECT=, TOADDR=, and TOADR=.
Description
The DSLINE command defines the attributes of a remote environment.
These attributes are used when you log on to the remote node via a
REMOTE HELLO command or when NFT or RPM creates a temporary
remote session with the logon sequence specified in the DSLINE LOGON
option. In order to establish a remote environment, you must either
equate an environment ID with the actual node name, or else use the
node name by itself, in which case the node name becomes the
environment ID. The environment ID then represents a specific session
on the remote node. You can use different environment IDs to represent
different sessions on the same node.
Subsequent DSLINE commands can use an individual or generic
environment ID or an environment number to identify the remote
environment(s). If you omit the nodename, envID, and envnum, the default
is the last environment referenced by a DSLINE or REMOTE command.
(If this command uses a generic environment ID, the new default
environment becomes the last individual environment listed in the
environment message then displayed. See the examples that follow.)
After a DSLINE command has been executed, a message is printed that
identifies all the affected environments. This message includes, for each
environment, the environment number assigned (in order of
environments defined), the fully qualified environment ID, and the fully
qualified node name (if different from the environment ID). If the
command specifies attributes for a generic environment ID, the generic
environment ID is listed separately in the returned message, identified
by the words GENERIC ENVIRONMENT. (Generic environments are
given a separate number in the sequence of environments, but this
number is not listed.) If the command uses a generic environment ID
but does not specify attributes, a separate generic environment is not
listed. The reason for this is that no new environment (with new default
attributes) is being defined.
Examples
Starting with MPE/iX release 4.0, NS services support ARPA domain
node names as well as NS node names. There are some changes in
selecting environments using generic EnvIDs. These changes will not
affect people who use only NS node names.