CONNECT
Syntax
- CONNECT - TO -<hostname> L
-<MCS name>-.J
<MCS name>
-<file title>---~
Explanation'
The CONNECT command invokes the Station Transfer capability ofBNA. Station Transfer allows a user to transfer control of a data comm station from the MCS of a local host to an MCS on a remote host. Once the logical connection is established between the station and the remote MCS, the station behaves as if it were actually connected to the remote host.
The CONNECT command initiates a station transfer dialog between the local host and the host specified by < hostname > .
Ifan <MCS name> is given and the STATIONTRANSFER MCS restriction is not set on the remote host, the station is transferred to the MCS on the remote host. If no
< MCS name> is specified, the station is transferred to the default MCS of the remote host.
If the MCS specified by <MCS name> is not running, an attempt will be made to start it when the station is transferred to it.
The <MCS name> may not be SYSTEM/STATIONtrRANSFER.
Ifan <MCS name> other than the specified default MCS is specified and the STATIONTRANSFER MCS restriction is set on the remote host, the CONNECT operation fails, and control of the station is returned to CANDE.
Once the station has been transferred to the remote MCS, that MCS may require the user to log on with a valid usercode/password for that host.
The BNA network must be running at the local host before a Station Transfer dialog can be initiated. If the local host is not in network operating mode, the CONNECT will fail and control of the station will return to CANDE.
The host that is specified by < hostname > must also be in network operating mode for a successful connection.
For the Station Transfer feature, at least one pseudostation must exist on the host receiving the transferred station; the number of pseudostations limits the number of 'remote stations that can be transferred in. A pseudostation is a virtual station that
can be attached to, and controlled by, an MCS in a manner similar to a real station.
However, unlike a real station, a pseudostation is not declared in NDLII, has no line assigned, and need not have a corresponding physical terminal on the local host.
CONNECT Command (cant.)
3-22
Examples
CONNECT·TO HOSTA
CONNECT TO HOSTS: SYSTEM/CANOE
8600 1500-000
CONTINUE Command
CONTINUE
Syntax
- CONTINUE ~---~---~
L
? - - - -_ _ _ _ _ _ _ _ ~!I •
J
~ * --- I L. = -<speci al character>--:
L-<control char mnemonic>~
Explanation
CA ... 1\JDE allows lines of input to be continued through the CONTINUE command. The user can reset, interrogate, or define a continuation character with the CONTINUE command.
CANDE interprets a line of normal input (that is, a line not beginning with the control character for the user's station) as needing to be continued when the defined continuation character is the last character of input. It removes the continuation character and inserts one blank in its place. CA..'JDE sends #% as a continuation prompt. The next line of input is then appended to this line. CANDE does not continue a line of normal input entered in sequence mode or page mode. (CAl"""JDE treats a defined continuation character entered in page or sequence mode as text.) If CONTINUE is entered, the continuation character becomes tmdefined. If CONTINUE? is entered, the user's current continuation character is displayed.
Entering CONTI1VUE * sets the continuation character to the default value defined for it in the USERDATAFILE. If the default continuation character is not defined there, the tasking-only continuation character (SC) is recognized as the default.
Entering either CONTINUE = <special character> or CONTINUE = <control char mnemonic> defines a new continuation character. Any special character except the semicolon (;) can be used for the continuation character.
Each user can have a default continuation character defined in the USERDATAFILE.
The CANDECONTCHAR option is initialized at the start of each CAL'IDE session as the default continuation character. The user can override the default character during a particular session by using the CONTINUE command. Refer to the Security Administration Guide for further information about the USERDATAFILE.
If no default continuation character is defined in the USERDAT AFILE, the ability to continue task-type commands with a percent sign (%) exists tmtil the first use of any forin of the CONTINUE command except for CONTINUE ?
If this system default continuation character is in effect, a query of the continuation character results in the "TASKING-ONLY CONTINUATION CHARACTER (%) DEFINED" message.
CONTINUE Command (cant.)
3-24
Examples CONT
#NO CONTINUATION CHARACTER DEFINED CONT *
#TASKING-ONLY CONTINUATION CHARACTER
(%)
DEFINED CONT=
*#CONTINUATION CHARACTER = * TERM WIDTH 28
#LINE = 28, PAGE = 24, BUF =1920, SCREEN, WAIT, "\"
MAKE*
#%
A*
#%
ALGOL
#WORKFILE A: ALGOL
100 ENTER A LONG LINE ON A*
#%
NARROW SCREEN LIST
100 ENTER A LONG LINE ON\
\A NARROW SCREEN
#
CONT
#
CONT ?
#NO CONTINUATION CHARACTER DEFINED
8600 1500-000
CONVENTION Command
CONVENTION
Syntax
- CONVENTI ON - . . - - - . - - - l C=<:Onvention name>:J
< convention name>
-<letter>--r---~~---~
~/16\-<alPhanumeric Character>~
Explana tion
The CONVENTION command alters the convention specification of the current session.
The convention specification identifies the format that is to be used for numbers, currency, time, and date for a particular system environment. The convention ~hould
be set in conjunction with the language specified for the CANDE session. Refer to the LANGUAGE command in this section for information about specifying the language in a CANDE session.
Users might have a convention and langu.age associated with their usercodes, however, . the user can dynamically change the convention or language during a session. This can be performed through the CONVENTION command and the LANGUAGE command, respectively.
When CONVENTION is entered, CANDE displays the convention currently in effect for the session.
The CONVENTION
*
form restores the current convention for the session to the default convention. The default convention specification is obtained from the USERDATAFILE by CANDE. If no convention is specified for the user in.the USERDATAFILE, the system convention is used. Refer to the A Series Security Administration Guide for information about changing the default convention specifications in/the USERDATAFILE.The CONVENTION < convention name> form changes the convention for the session to the convention represented by the convention name.
The convention name is validated through the CENTRALSUPPORT library. If the specified convention is not valid, the CENTRALSUPPORT library returns the following error message:
. INVALID CONVENTION NAME.
Ir"the CENTRALSUPPORT library is not present, then the convention is not changed and the following warning is given:
WARNING: CENTRALSUPPORT NOT PRESENT, CONVENTION NOT CHANGED.
CONVENTION Command (cant.)
3-26
Examples CONVENTION
#CONVENTION: AMERICAN CONVENTION CANADIAN
#CONVENTION CHANGED FROM AMERICAN TO CANADIAN CONVENTION *
#CONVENTION CHANGED FROM CANADIAN TO AMERICAN
8600 1500-000
COPY Command