Texas Instruments 990 User Manual page 58

Hide thumbs Also See for 990:
Table of Contents

Advertisement

~-------
~
946289-9701
The following example shows a CALL command issued on a system without an ACU. No number
prompt is displayed.
General format:
Condensed format:
COMMAND:
CALL
COMMAND:
CALL*
4.5.3 SEND DAT A COMMANDS. The send data commands are used to send information over the
communication link.
The Send Data (S) and Send Data with Device Selection (SS) commands are executed from the
transmit queue. The transmit queue is an ordered queue of all send commands in the order of their
entry (first-in, first-out). None of the send transactions are given priority.
In the general format, the send commands are terminated by a null response (return) to a
PATHNAME: prompt. In the condensed format, the send commands arc terminated by ending a
line (record) with an asterisk (*).
The response to a PATHNAME: prompt may be one or more pathnames or text strings separated by
commas or asterisks. At least one pathname or text string must be specified. The maximum number
of pathnames or text strings allowed with each send command is limited only by the number of
queue buffers available at the time the command is entered. When multiple pathnames are specified,
the files are concatenated and sent as one file. Any valid pathname may be used in response to a
PATHNAME: prompt.
A text string is a valid response to the PA THN AME: prompt for the send commands. A text string
must be enclosed in angle brackets(<>) and may not exceed 48 characters. Any ASCII character is
allowed in a text string. If using the ampersand(&) to abort the command, the text string must first
be closed with an angle bracket and then followed by the ampersand
(&).
When a send command is executed. the Emulator parameters (transparency on/ off, etc.) are queued
with the command. The parameters only affect the transmitted data.
Binary Data Transmissions. In a 990 to 990 communication environment, the Emulator can transmit
binary data using the send data commands. Binary is specified using a # (pound sign). The pound
sign precedes each pathname being transmitted.
The binary specification is on a per-pathname basis, i.e., each binary file pathname or text string
must be preceded by a pound sign (#). The pound sign (#) specifies to the Emulator that the file
should not be translated. If pathnames or text strings are being concatenated for transmission (i.e.,
multiple pathnames or text strings are entered in response to the PATHNAME: prompt or
prompts), the first pathname or text string determines whether the transmission will be binary. If the
concatenated files are to be transmitted in binary, the first pathname must be preceded with a pound
sign (#).
Binary files must be transmitted in fixed length records or single record blocks with transpaiency on.
Transparency does not have to be specified, the Emulator enables it automatically.
The DXIO program files must be transferred as binary files. The transmitting and receiving stations
must specify a record length of 288 bytes. To prepare the program file for the transfer, execute a
Backup Directory (BD) specifying the complete pathname of the program file to be transferred. The
Backup Directory creates a sequential file that can be transmitted. To transmit the file, precede the
pathname with a pound sign(#) (specifying do not translate) and use this pathname in the S or SS
command. The receiving DXIO must do a Restore Directory (RD) before using the file.
4-20
Digital Systems Group

Advertisement

Table of Contents
loading

Table of Contents