Intertask Message Queue Mode; Command File Commands; I Command File Command (Cf) - Texas Instruments 990 User Manual

~-------
~
946289-9701
When the command file is the primary command source. it controls the session until an end-of-file
(EOF) is read. a TERM or ABORT TASK command is encountered, or a device error occurs in the
command chain. When any of these occur, the task terminates.
When the command file is the secondary command source, it controls the session until an end-of-file
(EOF) is read. a TERM or ABORT TASK command is encountered. an error occurs in the
command chain. or another CF command is encountered. When the command file is terminated by
an EOF or an error, Emulator control returns to the primary command source beginning with the
command following the CF command. If a CF command is encountered in the active command file,
the executing command file is terminated and the new one begins execution. i.e .• nested CF
commands are not allowed. Issuing a CF command with a null (blank) pathname causes the active
command file to be closed and session control to be returned to the primary command source.
4.4.3 INTERTASK MESSAGE QUEUE MODE OPERATION. A DXIO task running on the
DXlO system can place Emulator commands into an intertask message queue. The commands issued
by the DX 10 task are records representing a response to a prompt. The format of these commands
may be either general or condensed (the condensed form will usually be more conve_nient). If the
general format is used. each response is one record and null responses are represented by blank
records. These commands have a maximum record length of 80 characters. To use intertask message
queues. the system must have been generated to include intertask communication and adequate
buffers. ·
The commands are placed by the task into an intertask message queue. The task ide.ntifies the queue
with a hexadecimal number between 00 and FF. Thi's queue identification number is assigned as the
Emulator's COMMAND ID: during Emulator activation.
A second :ntertask message queue ·or a log file may be identified to accept log information from the
Emulator. Like the command intertask message queue. the log intertask message queue is identified
by a hexadecimal number between 00 and FF. This queue should be identified as a separate queue
from the command queue. The queue identifier or tile log file pathname is assigned as the Emulator's
LOG ID: during Emulator activation. The console prompts. the intertask message queue responses,
and any messages resulting from the interaction are logged. Using a command intertask message
queue does not require using a log intertask message queue. The Emulators can accept commands
from an intertask message queue and output log information to a log file, the operator console. or an
intertask message queue; and they may accept commands from a file and log to an intertask message
queue.
For information about intertask communication, refer to the Model 990 Computer DXJO Operating
System Release 3 Reference Manuals, part numbers 946250-9701 through 946250-9706.
4.5 EMULATOR COMMANDS
The Emulator commands are grouped according to their function. Within each function, the
commands are listed in alphabetical order by command name. The groups are as follows:
• Change Default Commands
• Connect Commands
• Send Data Commands
• Receive Data Commands
• Command File Commands
4-10
Digital Systems Group