OTRONA ATTACHE Series Manual page 29

Alanns
Assuming that cable connections, baud rates, and other protocols are
properly set between the two devices involved in the data transfer,
SOFTCOl'I then transfers the file DOCFILE to the receiving device.
When the transfer is complete, SOFTCOM cycles back to its first menu and
XSUB inserts the next value "6" from the command line. This number
corresponds to the item on the SOFTCOM menu to return the system to CP/M.
Note that the number of parameters that are passed from the command line
to the .SUB f He must match the number of
$#
variables in the .SUB file
or the program will abort. In the preceding example, the command line
contained five values
(1,
T, DOCFILE, Y, 6) and the .SUB file contained
five variable lines
($1, $2,
$3, $4, $5).
Since
SOFTCO~1
returns to its first question when the transfer is
complete, addi tional files could be transferred by including additional
answers in the command line and inserting matching variable lines into
the .SUB file.
For example, you could activate SOFTCOM and transfer both DOCFILE and
REPFILE with a single alarm. The alarm's command line would be as
follows:
ENTER <X>MMAI!D:
11:10:00 10/15
I I SUBMIT ABC
1
T DOCFILE Y
1
T REPFILE Y 6
II
The file ABC.SUB would now require nine variable lines
($1
through $9).
XSUB would pass the parameters for the first transfer (1 T DOCFILE Y) and
SOFTCOM would transfer the file DOCFILE.
When the da ta transfer is comple te, SOFTCOM returns to its fi r st menu.
Since the command line now specifies option
1
rather than option 6,
SOFTCOM begins another computer to computer transfer. The remaining
questions are answered in sequence (T, REPFILE, Y) and REPFILE is
transferred.
When the transfer is complete, SOFTCOfl'l cycles back to its first menu and
XSUB inserts the next value "6" from the command line. This number
corresponds to the item on the SOFTCOM menu to return the system to CP/M
and the cursor returns to A>.
Note: regardless of the types of software programs that are chained
together in an alarm using SUBMIT and XSUB, the set-up procedure is
always the same:
o a .SUB file is created with XSUB on the first line, the command on
the next line, and
$#
variables on the following lines.
o an alarm is scheduled using SUBMIT, the filename, and the answers to
the screen prompts for substitution
by
XSUB in the command file.
3-14