Specifications

DDE reference
Gallagher & Robertson Glink: API reference manual 187
LinPut The data accompanying this command will be sent directly to the
communications interface irrespective of the current mode of the
emulator. The data will not be 'terminated' (with CR, ETX or
EOT) unless the relevant character is specified as part of the data.
In that the termination character is affected by the emulator state,
communications interface, and Glink configuration we
recommend that you use the LinXmt command rather than the
LinPut command when termination is required.
LinXmt Sends the accompanying data with the correct data terminator to
the host machine.
PosCur Positions the cursor. The data accompanying the command should
be the ASCII X and Y coordinates to position to, separated with a
space.
ScrGput Inserts a value into the global script parameter; this may be
retrieved in the script itself using the $GPARAM and/or $Gn built-
in variables. The value of the global script parameter may be
retrieved in your DDE application using the ScrGget request
(either using a DDE request or by asking for an advisement).
Script Starts the script with the name specified in the accompanying data.
Control is returned to the calling application immediately; if you
require to monitor the progress of the script you should use a hot
link to the ScrGet item and insert PARAMETER commands at
appropriate places in the script file.
Simple script commands may be executed using the normal '='
prefix as in the DOS version (however, see below under
'Executing Commands').
ScrPut Inserts a value into the script parameter; this may be retrieved in
the script itself using the $PARAMETER and/or $Pn built-in vari-
ables. The value of the script parameter may be retrieved in your
DDE application using the ScrGet request (either using a DDE
request or by asking for an advisement).
UvtiPut The data accompanying this command should be an ASCII
numeric between zero and 255, and will be placed in the UVTI
status (requestable with the UvtiGet request).