Thank you to those who proposed ideas. The issue appears to be something in
the vendor code over which I have no control. Working with vendor now.
Brad
U.S. BANCORP made the following annotations
-
Electronic Privacy Notice.
(@USER.TYPE = 2).
Kathleene M Hunter
Resolution Provider
-Original Message-
From: Kevin King [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 26, 2008 7:49 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UD] problem calling program from shell script
@USER.TYPE = 2 is new to me
@USER.TYPE = 2 is new to me. The documentation describes it as
Redirected Standard Input which makes me think that yes, that could
definitely change the mechanics of starting a phantom.
On Jan 25, 2008 11:00 AM, [EMAIL PROTECTED] wrote:
How is MT.PROC starting MT.WATCH?
I wish I knew. That's
How is MT.PROC starting MT.WATCH?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
How is MT.PROC starting MT.WATCH?
I wish I knew. That's part of my problem since both MT.PROC and MT.WATCH
are 3rd party software.
One more clue that may make your question irrelevant: in a successful,
non-scripted run, the phantoms start up before MT.WATCH starts displaying
status. This might
