You may consider rolling your own on this one. If on Unix, you might
have a script that does this:
#!/usr/bin/ksh
# Remove TEMP files
if [ "$1" = '' ] ; then
echo "usage: $0 FILENAME(s) (separated by a space or LF)
exit 1
fi
for i in $1
do
echo Removing $i
cd $UVACCOUNT ; # Change this to the account or prompt for it
rm -r $i
rm -r D_$i
uv "DELETE VOC "$i
done
There may need a couple of other things added, especially if you have
security options in the account, but TEMP files probably shouldn't be
stored in a production account but rather in a subdirectory/filesystem
somewhere else.
Just my two bits.
Karl
On Wed, 2004-03-10 at 10:59, Dianne Ackerman wrote:
> Sometimes when using DELETE.FILE, the system prompts that the data entry
> does not match expected data... because when the file was originally
> created LONGNAMES was off and now LONGNAMES is on. Is there any way to
> force the DELETE.FILE to work without warning and prompting?
>
> The HOSTACCESS utilities we use create these temporary files and when a
> sys admin needs to do cleanup, it would be nice to run a utility to
> delete all these hundreds of temporary files. But I'm not sure how to
> have a paragraph delete them and deal with sometimes needing to answer
> those prompts.
>
> Any ideas?
> -Dianne
--
Karl L. Pearson
Director of IT,
ATS Industrial Supply
Direct: 801-978-4429
Toll-free: 888-972-3182 x29
Fax: 801-972-3888
http://www.atsindustrial.com
[EMAIL PROTECTED]
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
