× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I find it easy to use QSH for such things: QSH CMD('rm -r 
/dir/subdir/dir_I_want_to_delete') 

From the QShell reference:

rm - Remove directory entries
Synopsis
rm [-f | -i] [-dPRr] file ...
Description
The rm utility attempts to remove the non-directory type files specified on the 
command line. If the
permissions of the file do not permit writing, and the standard input device is 
a terminal, the user is
prompted (on standard error) for confirmation.
The rm utility removes symbolic links, not the files referenced by the links.
It is an error to attempt to remove the files ″.″ and ″..″.
Options
-d Attempt to remove directories as well as other types of files.
-f Attempt to remove the files without prompting for confirmation, regardless 
of the file’s permissions.
If the file does not exist, do not display a diagnostic message or modify the 
exit status to reflect an
error. The -f option overrides any previous -i options.
-i Request confirmation before attempting to remove each file, regardless of 
the file’s permissions, or
whether or not the standard input device is a terminal. If the response from 
the standard input
begins with the first character for the YES response in the current locale, the 
file is removed. The
-i option overrides any previous -f options.
-P Overwrite regular files before deleting them. Files are overwritten three 
times, first with the byte
pattern 0xff, then 0x00, and then 0xff again, before they are deleted.
-R Attempt to remove the file hierarchy rooted in each file argument. The -R 
option implies the -d
option. If the -i option is specified, the user is prompted for confirmation 
before each directory’s
contents are processed (as well as before the attempt is made to remove the 
directory). If the user
does not respond affirmatively, the file hierarchy rooted in that directory is 
skipped.
-r Equivalent to -R.
Exit Status
v 0 if all of the named files or file hierarchies were removed, or if the -f 
option was specified and all of the
existing files or file hierarchies were removed.
v >0 if an error occurs.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 
On Behalf Of David Gibbs
Sent: Monday, July 31, 2006 8:27 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: RMVDIR ... RMVLNK not working

Jon Paris wrote:
Have a situation where RMVDIR ... RMVLNK(*YES) is not working and 
issuing an error to the effect that directory is not empty - which 
RMVLNK is supposed to take care of.

Yeah, that's never worked as far as I know ... we had to implement our own 
recursive rmvlnk program (using C api's called from CL to walk the tree).

A lot of the IFS commands seems to have problems with IFS space, but the error 
reporting is next to useless.

david
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To 
post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or 
change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment 
to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.