You may want to check into the /uvtmp for files that start with "capture" and read those for a hint.
I've seen cases where a capturing is stopped because a delete is interrupted because of 644 permission mode, and I've seen "unable to re-open file unit" errors. The "CAPTURING" statement creates a file in /uvtmp so what you see in aborted capturing files can be revealing. ----- Original Message ---- From: Tony G <1tlx6h...@sneakemail.com> To: u2-users@listserver.u2ug.org Sent: Monday, February 23, 2009 10:37:17 AM Subject: [U2] [UV] HP, Cron, Como, Execute, Capturing . Not 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 u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
