Hi Tony,
I do this all the time on UV 10.1.4 on RH AS 3. I have not seen a conflict
with COMO and EXECUTE CAPTURING, except that the COMO records the results of
the execute as well as the CAPTURING variable.
E.g. EXECUTE "SH -c 'ls'" CAPTURING DIR.LIST
Not only does DIR.LIST contain all the files in the directory, but the COMO
records them as well, making for very verbose COMO files!
Note that I have not tried the combination of cron + COMO + EXECUTE
CAPTURING {+
On Mon, Feb 23, 2009 at 7:37 AM, Tony G <[email protected]> wrote:
> We have a client on UV/HP-UX running a BASIC routine from a Cron
> job. The BASIC code shells out from EXECUTE and Captures data
> from the OS. The Capture is failing and it looks like COMO gets
> the StdOut that should be directed into a variable.
>
> I'm not sure yet if Como plays any part or if all
> Execute/Capturing instructions will fail when executed from Cron.
> The code works fine from TCL. I'm also checking to see if there
> are any other options or middleware, and exactly what's being
> executed in the Cron line.
>
> Until I get more info though, I'd like to know if this is a
> recognized issue. Under what conditions can we expect something
> like this to fail?:
> Execute "sh -c ... " Capturing result
>
> Thanks.
>
> Tony Gravagno
> Nebula Research and Development
> Info@ removeNebula-RnD.com
> (Various other email addresses are currently down ... it's
> Monday...)
> -------
> u2-users mailing list
> [email protected]
> To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
