Remote Terminal with CTOS PROSIGN.RUN PROGRESS Signon
PROGRESS supplies a remote (dumb) terminal access utility in the CTOS
environment. A remote terminal can be connected to the RS-232-C
communications ports of the CTOS/BTOS CPU either directly, or more
commonly, through a modem.
When you run PROGRESS from a remote terminal, you cannot use 4GL
statements that access the CTOS/BTOS operating system.
In order to configure the remote access, consult Section 4.7.2 of
the PROGRESS System Administration I: Environments for PROGRESS and
BTOS Guide. See also Section 2.2 of the PROGRESS System Administra-
tion II: General Guide for an illustration of the "PROGRESS 4GL"
command form under CTOS.
Note that there are some documentation errors in the Sys Admin I:
Environment Guide: several command references to Version 5 commands
were not updated to the V6 command.
[sys]<DLC>ProSign.Run is the executable for remote access.
[sys]<dlc>PROGRESS.RUN is the executable for both single and multi-
user V6 PROGRESS.
The items you need to begin include:
Terminal type supported by PROGRESS (see the <DLC>PROTERMCAP file)
Connection hardware
Connection parameters
Verify the connection
Serial communications cable may need to be a null modem cable for
direct connections.
Verify that the terminal and communications port are at the same baud
rate.
Verify two-way communication by copying from the workstation to the
terminal and vice versa.
DTR Signal is monitored. If DTR drops, then the session is
terminated.
This configuration does, technically speaking, allow you to support
two users off the same box, but it is LESS THAN OPTIMAL, for one user
will slow down the other, and if one executes a process that triggers
a crash, the other will have to be rebooted as well.
Create a terminal environment file which specifies the ASCII term
type to be used, e.g.,
the CTOS environment: [sys]<sys>Progress.env would read:
TERM=B20
DLC=[sys]<dlc>
PROPATH=:[sys]<dlc>dlctda/:
the TERMINAL environment: [sys]<sys>ProTerm.env
TERM=wyse50
DLC=[sys]<dlc>
PROPATH=:[sys]<dlc>dlctda/:
SETTING UP THE ENVIRONMENT
For Remote Terminals to be used, there must NOT be a username.ENV
file. You should use the :ProgressTermEnv: line in the .user file.
A sample .user file for remote access:
:ProgressTermEnv:[sys]<sys>ProTerm.ENV
:ProgressExitFile:[sys]<dlc>Prosign.RUN
:ProgressChainFile:[sys]<dlc>Progress.RUN
The ProgressTermEnv entry defines the environment file that will be
used for the PROGRESS session. The ProgressExitFile is the program
that will be executed when the PROGRESS Session ends. The
ProgressChainFile is the PROGRESS run file to be executed. Use
PROGRESS.RUN for single or multi-user PROGRESS; use ProTnyRt.Run for
Runtime single or multi-user (note certain limits to tiny progress,
such as printing limitations).
The PROGRESS command name MUST follow the chain file entry. This is
the command, and command form, that relate to the run file specified.
If startup options are used, they must appear on the same line as on
the command form (see Sys Admin II, ch. 2).
STARTING THE PROGRESS SIGNON
Install Context Manager BEFORE running PROGRESS Signon so that the
workstation can still be used while the dumb terminal session is
running. Execute the PROGRESS Signon command. The terminal screen
should display a User Name prompt. A temporary file [Scr]<$>PROGRESS.
COMM is created by the PROGRESS Signon command. Do NOT delete this
file while the session is running. Make sure the scratch directories
<$> are not full of left-over spooler temp files -- ProSign must be
able to create its own temp file and running out of file handles will
prevent this.
ASCII TERMINALS - OPERATING DIFFERENCES FROM LOCAL CLIENTS
The interrupt key sequence for a terminal is CTRL-C. This interrupt
is not seen immediately from the dumb terminal, so all keystrokes
prior to the abort will be processed first. The DTR signal is
monitored by the PROGRESS Signon session. When DTR drops the session
is ended. The "CTOS" and "BTOS" statements cannot be executed from
the remote terminal. However, the OS statements, such as
"CTOS OS-Delete" may be used. Terminating the terminal session is
accomplished by pressing ACTION-FINISH in the context that is
running the PROGRESS Signon session. A remote terminal session's
ACTION-FINISH returns the user to the PROGRESS LOGON. Another
ACTION-FINISH from there gives a logout.
Progress Software Technical Support Note # 12706