× 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.



James:

I'm not sure what the deal is with your test, but try this:

 ==> call qshell/rm ('-f' '-r' '/frobozz/foo/')

How does the result compare with yours so far?

Tom Liotta


midrange-l-request@xxxxxxxxxxxx wrote:

>   1. CL front-end for QSHELL "rm -r" (James H H Lampert)
>
>I'm currently working on a CL front-end for our old 
>friend, the QSHELL "rm -r" method of deleting an IFS 
>directory and its contents.
>
>I've got some crude functionality so far, but I've got 
>some puzzling behavior: more often than not, it runs into 
>an error trying to get rid of the root of what's being 
>deleted. For example, if I have the following tree 
>structure:
>
>/frobozz
>/frobozz/foo
>/frobozz/foo/boz
>/frobozz/bar
>/frobozz/bar/boz
>/frobozz/baz
>/frobozz/baz/boz
>
>and give it:
>
>DELTREE /frobozz/foo
>
>it gets rid of /frobozz/foo/boz, and the files therein, 
>and all the files in frobozz/foo, but instead of deleting 
>frobozz/foo, it blows up with a SYSOUT screen, bearing the 
>message, "rm: 001-2136 Error found removing link to 
>//frobozz/foo. Resource busy."
>
>It works fine if I enter the rm command from the QSHELL 
>command line, or if I manually pass it to QSHELL on an 
>OS/400 command line. Why is a CL program different?
>
>On a related note, having a completion message turn on the 
>terminal's message light on successful completion is a bit 
>crude. Is there a way for the CL program to catch the 
>message? Perhaps with a RCVMSG? If so, how?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.