Exchange/RJE Manual

RJECIR Command
Exchange/RJE Commands
104698 Tandem Computers Incorporated 3–3
If you omit this option, the Exchange/RJE command interpreter writes its
output to the command interpreter’s output file, which is your terminal if you
are running the Exchange/RJE command interpreter interactively.
parameter
is one of the following terms. See the SET command for more information about
these parameters:
A[CU] [\ system .]$ acu
BLOCKI[NG] { ON | OFF }
BLOCKS[IZE] size
C[PUS]
E[BCDICNL] { ON | OFF }
L[INE] [\ system .]$ line
NO[NSTOP] { ON | OFF }
PRI[ORITY] priority
PRO[GRAM] [[[\ system .]$ volume .] subvolume .]RJESV
RETRIESE[OT] number
RETRIESI[DLE] number
S[ERVER] [\ system .]$ name
T[RACE] { ON | OFF }
U[SERLIB] filename
Considerations The RJECIR command starts the Exchange/RJE command interpreter and is an
implied TACL RUN command. For complete information on the TACL RUN
command, see the TACL Reference Manual.
The Exchange/RJE command interpreter cannot be run as a NonStop process pair. All
the RUN command options that relate to NonStop process pairs and backup processes
do not apply to the RJECIR command.
The following paragraphs discuss the use of the SERVER parameter and the
PROGRAM parameter to control whether the first CONNECT command starts a new
line server or connects to an existing line server. This discussion assumes that you do
not use the SET command before the first CONNECT command to alter the
parameters specified in the RJECIR command. This discussion also assumes that on
the local system all the Exchange/RJE program files reside in the same volume and
subvolume.
Note that every user who uses RJECIR to start a new line server must have write
access to RJESV, the line server object file.
Starting a Local, Temporary Line Server
If you want the first CONNECT command to start a temporary line server on the
system where the Exchange/RJE command interpreter resides, omit both the SERVER
parameter and the PROGRAM parameter.