Brad:
How are you running the input prompt?
I had an unusual problem with UDT when I wanted to get some PORT.STATUS
information on a port running a phantom. This phantom process (an
application background process) did a sleep 60 then tested for the
existence of a process record; this went on in a perpetual loop. When I
tried to find out if a port was running this process I had to do a
PORT.STATUS on the port, but it didn't work because of signaling
problems. The solution for me was to modify the code running the
background program to loop for 60 then do a sleep 1. This accomplished
the same thing but allowed for the PORT.STATUS to work properly.
Maybe this is the same kind of problem you're having.
Bill
------------------------------------------------------------------------
[email protected] said the following on 8/16/2010 8:39 AM:
Thanks to the suggestions from various posters, I have determined that my
incriminations of screen were malicious libel. It's not screen. The issue
of not being able to send an interrupt (e.g. kill -2/SIGINT) is a result
of how I had to work around something in the third-party code I'm trying
to automate.
There are a couple input prompts, e.g. "do you want to continue? y/n" that
I originally tried to handle with DATA statements. But the 3rd party
software is doing something to clear the input stack. I've tried a few
different workarounds, including hacking the CLEARINPUT verb, with no
success. I finally got it work by doing a PCPERFORM as follows:
PCPERFORM 'echo PROGNAME\\nY\\n\\n\\n | udt'
This works great except that a SIGINT issued to the newly spawned udt
process has not effect. A straight kill works, but it actually kills the
udt process which is precisely what I do *not* want to happen.
Any creative thoughts on how to get a SIGINT to work? Maybe a different
way of calling PROGNAME? Talking to the vendor about changing their code
is a theoretical option, but involves $ and a good deal of time, so is not
preferred.
TIA,
Brad.
U.S. BANCORP made the following annotations
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
