If it's just to get the file names and not the other information like the group
owners, permission bits why not simply do a pointer to the directory then
select the directory ?
EI:
IF @USERNO < 0 THEN
TMP.NAME = (65536 + @USERNO):".TMPTR"
END ELSE TMP.NAME = @USERNO:".TMPTR"
OPEN "", "VOC" TO VOC ELSE STOP 201, "VOC"
TMPTR = "F]/tmp/]D_&PH&"
CONVERT "]" TO @AM IN TMPTR
WRITE TMPTR ON VOC, TMPNAME
OPEN "", TMPNAME TO F.TMPTR ELSE STOP 201, TMPNAME
FILELIST = '"
SELECT 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 <[email protected]>
To: [email protected]
Sent: Tuesday, February 24, 2009 7:04:16 AM
Subject: RE: [U2] [UV] HP, Cron, Como, Execute, Capturing . Not
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
Ross Ferris
Stamina Software
Visage > Better by Design!
>-----Original Message-----
>From: [email protected] [mailto:owner-u2-
>[email protected]] On Behalf Of Tony G
>Sent: Tuesday, 24 February 2009 8:45 AM
>To: [email protected]
>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 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.
>
>I'm wondering if this is an OS-specific issue where UV/HP is
>capturing in COMO but not in Capturing, or maybe this is only
>occurring when run through Cron. They could be doing something
>like this too:
> echo "PHANTOM RUNREPORT" | uv
>...with the phantom being the platform-specific culprit.
>
>I'll get the details and report back, then maybe someone with the
>same platform here can check this before we file a bug report.
>
>Tony Gravagno
>Nebula Research and Development
>TG@ remove.pleaseNebula-RnD.com
>Email now working properly
>
>Don't forget Pickwiki.com!
>
>> From: Scott Ballinger
>> > 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 {+ PHANTOM?} so perhaps there
>> > is something going on there, but I do use cron +
>> > EXECUTE CAPTURING in many places without problems.
>-------
>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/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
