| At last I was able to get details of the setup the customer wanted to do but
failed to implement it via function CXP
This customer wanted to invoke a CC control document with CXP function.
Herewith the control document called TESTNET.CXP
...............
connect "TESTNET"
pause 100
send/noeol "AT<cr"
wait "OK"
pause 100
send/noeol "atb111111111"
pause 200
send "<CR>"
wait "CONNECT"
pause 1000
send "@"
pause 100
send "<CR>"
pause 100
wait "TERMINAL"
pause 100
send "<CR>"
pause 200
send "<CR>"
wait "@"
pause 200
send "MAIL"
............
called by the following script
.set_refresh
.clear
cxp disconnect
cxp process "TESTNET"
.refresh
.exit
So far it works OK for the above setup.
Nevertheless, he wanted to invoke this control document only ***AFTER*** he
has set up the comm line to be 7 data bit and odd parity; when the execution
of the control document finishes, the comm line is to be reset to its default
setting of 8 data bit and no parity.
This can be achieved with a rather messy way: executing 2 DCL command
procedures that do SET TERM e.g.
$!File 7odd.com
$
$def dtepad$ini sys$login:7odd.ini
$set term/perm/noeight/par=odd lta5555
$!File 8none.com
$
$def dtepad$ini sys$login:8none.ini
$set term/perm/eight/par=none lta5555
and invoking them in the script file with
.fx command 7odd.com
before the cxp function
.fx command 8none.com
after the cxp function
In addition to its being messy, this set up requires the process privilege
LOG_IO; hence, not available to non-priv users.
Can the CXP function achieve this without doing SET TERM via DCL ? Any
comments/advices on the work-around are very appreciated by this customer
Hong
|