Jacques - that's great info but the situation is more involved. Thanks anyway.
Ross - I'm fairly confident this is one of those issues that never comes up in QA, only in the field. The cron line executes a script, the script executes: uv "PNAME" > /outfile That's a Paragraph that looks like this: 001 PA 002 COMO ON FOO 003 RUN BP PROG 004 COMO OFF So it's a prog wrapped in COMO, in a paragraph, with stdout redirected, executed from uv, within a script, called from cron. (Sometimes I'm amazed any of this works.) I've asked the client to remove COMO for now, then if the problem persists to avoid redirection from the uv command. When the exact behaviour is determined, I've recommended that an issue report be filed with IBM through the client's DBMS provider. I've already suggested that if required, we can redirect the "PROG" OS queries back into OS files and then read from there, rather than attempting to Capture the output directly. However, the code doing this is our product activation subroutine (documented in my blog, search for "activate key protect"). For many reasons that code should not be writing anything to the host OS. I'll post a follow-up when we get something solid. Thanks again! T > From: Ross Ferris > Have you changed the code yet to avoid problem? You > haven't mentioned version of UV --> if not current, > check later GTARs to see if issue identified/resolved. > > Get the customer going with a redirection/read ... > obviously (?) new code, but an > > ls -l > /tmp/unique_filename > > will work across ANY *nix platform --> assume cron is > running as same user/permissions as when you fire from > TCL ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
