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
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
You can do this from the OS level:
echo Y|delete.file fname
At 12:59 PM 03/10/2004, you 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
I should have mentioned - this is on windows. And the issue is that the
VOC might be PIX.OUTPUT.701 but the operating system file is PIX.OUT000
or PIX.OUT022 because it was created LONGNAMES OFF
-Dianne
Karl L Pearson wrote:
You may consider rolling your own on this one. If on Unix, you might
The actual names of the files at the OS level are in lines 2 and 3 in
the VOC 'F'-pointer. So, if you roll your own, you could use mvBASIC and
just read REC2 for the DATA portion and REC3 for the DICT portion,
then do
DELETE UFD REC2 REC3
DELETE VOC FNAME
or some such.
Karl
On Wed, 2004-03-10
