I'm in the process of automating various vendor processes by calling them
from a shell script which can be run by a scheduler. I've done a couple
single-threaded processes this way and it works fine. But I'm having
difficulty with a multi-threaded process. At least it seems that
single/multi-threaded is the key difference.
This is a sample from my shell script. The "\n3\n1\n" passes required
inputs of 3 and 1 to MT.PROC
echo "MT.PROC \n3\n1\n" | udt
MT.PROC starts and performs several single-threaded commands without issue.
It is then supposed to start 10 phantoms and launch a monitoring process,
MT.WATCH. MT.WATCH provides updates on phantom progress every minute.
The problem seems to come up when MT.WATCH is started. It seems almost as
if MT.WATCH never gets a chance to start since it doesn't display anything.
MT.PROC thinks it's done, performs a few more commands and returns to TCL.
When I start MT.PROC from TCL it works just fine. So it's the combination
of script/UniBasic that's causing the issue.
I'd appreciate any ideas on what to look for, trap or, worst case, ask the
vendor (for a small fee).
UniData 7.1
AIX 5.3
tia
Brad
U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications privacy
laws, and is also confidential and proprietary in nature. If you are not the
intended recipient, please be advised that you are legally prohibited from
retaining, using, copying, distributing, or otherwise disclosing this
information in any manner. Instead, please reply to the sender that you have
received this communication in error, and then immediately delete it. Thank you
in advance for your cooperation.
---------------------------------------------------------------------
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
