tee is a pretty standard UNIX tool. I cannot think of a variant which
doesn't support it as standard. At worst you'd have to find an open source
version and compile it, but it is one of the simplest programs - I doubt it
calls anything remotely non-standard.
-Original Message-
Anthony W.
In message
<619f7eea7a19a945876205ff14ee8de10116e...@win2003.office.stamina.com.au>,
Ross Ferris writes
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
Ken wins!
Running cron as a non-root user (probably a good idea anyway)
causes this environment to work properly.
Your prize is a free permanent end-user license for NebulaXLite
for any supported platform. Developer licenses are free anyway
so for anyone else who contributed to this thread to thi
Tony -
It just occurred to me that cron is running uv as root and that when
root starts uv, the LOGIN proc does not run except in the uv account.
Try changing the user in cron to a normal uv user and I bet your
problem will go away.
Ken
At 09:54 AM 2/24/2009, you wrote:
Jacques - that's gre
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 th
CT F.TMPTR
LOOP WHILE READNEXT FILENAME
FILELIST<-1> = FILENAME
REPEAT
You can get a lot of the other information on a file with the STAT command and
the FILEINFO function.
- Original Message ----
From: Ross Ferris
To: u2-users@listserver.u2ug.org
Sent: Tuesday, February 24, 2009 7:
f Of Tony G
>Sent: Tuesday, 24 February 2009 8:45 AM
>To: u2-users@listserver.u2ug.org
>Subject: RE: [U2] [UV] HP, Cron, Como, Execute, Capturing . Not
>
>Thanks for responses so far.
>
>Scott - this code is also doing 'ls', and the output gets
>captured in COMO as yo
Thanks for responses so far.
Scott - this code is also doing 'ls', and the output gets
captured in COMO as you have seen, but it doesn't continue into
the Capturing var. At least we can confirm COMO is supposed to
see the output (for better or worse) but not at the expense of
BASIC not seeing it
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
Premature transmission!
On Mon, Feb 23, 2009 at 11:06 AM, Scott Ballinger wrote:
> 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.
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
: u2-users@listserver.u2ug.org
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
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
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
Exe
14 matches
Mail list logo