PS TEXT EDIT Reference Manual

Appendix E TEDIT and TACL Interface
058059 Tandem Computers Incorporated E–1
Overview This appendix explains the TEDIT commands and TACL commands used
in TACL code that allow you to communicate with TEDIT. This appendix
also explains the TEDIT and TACL communications protocol.
Important Before you try to use any of the following commands, you should thoroughly understand how
to use TACL and know how to write TACL macros. Refer to the TACL Programmer’s Guide
for information about writing TACL macros.
TEDIT Process
Environment
You could call this communication between TACL and TEDIT a process
interface, because a TACL process is not the only process that could be
written to interact with TEDIT. Typically, the interface between a TEDIT
process and any process is as follows:
1. The process that wants to communicate with TEDIT waits for messages
from the TEDIT process.
2. Commands are given to TEDIT (from a process), telling it to send data
and command arguments to the process.
3. The process sends TEDIT commands to TEDIT, causing TEDIT to
perform operations such as giving up control of the terminal.
4. The process tells TEDIT by sending a message that it is giving terminal
control back to TEDIT.
5. Each time a process wants to communicate with TEDIT, a process
begins this communication interface again.
TEDIT and TACL
Interface
The TEDIT TACL interface is usually used between TEDIT and the TACL
that started TEDIT. This interface is performed by user-written TACL code.
This TACL code:
Sets up a #SERVER
Issues a PARAM TACLNAME command with the name of the
#SERVER as its argument