With PURGE/CONFIRM, Y and N are clear. A results in everything left
being deleted. We need another answer which deletes everything left for
the current FILE.VERSION, then asks again when the next FILE.VERSION
comes along.

I'm sure many want this and that some have written a corresponding DCL
procedure. But it would be a nice native extension and, I'm guessing,
not too difficult to implement.

On 1/3/2022 8:32 AM, Phillip Helbig (undress to reply) wrote:
> With PURGE/CONFIRM, Y and N are clear. A results in everything left
> being deleted. We need another answer which deletes everything left for
> the current FILE.VERSION, then asks again when the next FILE.VERSION
> comes along.
>
> I'm sure many want this and that some have written a corresponding DCL
> procedure. But it would be a nice native extension and, I'm guessing,
> not too difficult to implement.

Why not just issue a number of separate PURGE??

Arne

In article <61d2fef3$0$703$14726298@news.sunsite.dk>,
=?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk> writes:

Real-life example:

$ purge/confirm/before="-31-" DISK$USER:[HELBIG...]*.*/keep=5

:-|

On Monday, January 3, 2022 at 9:04:16 AM UTC-5, Phillip Helbig (undress to reply) wrote:
> In article <61d2fef3$0$703$1472...@news.sunsite.dk>,
> =?UTF-8?Q?Arne_Vajh=c3=b8j?= <ar...@vajhoej.dk> writes:
>
> Real-life example:
>
> $ purge/confirm/before="-31-" DISK$USER:[HELBIG...]*.*/keep=5
>
> :-|
Tools like PURGE (just a variant of DELETE) simply gives that filespec to LIB$FILE_SCAN
and keep getting filenames back. What is the "next file" that you speak of? Different name
in same directory? Same name in different directory? Different DID and DEVICE from the
last file? (I think that's what you want)

And do you want that form of /CONFIRM=UNTIL_THE_NEXT_FILE to work on other verbs
like RENAME, SET FILE, etc?

On 1/3/2022 9:04 AM, Phillip Helbig (undress to reply) wrote:
> Real-life example:
>
> $ purge/confirm/before="-31-" DISK$USER:[HELBIG...]*.*/keep=5
>
> :-|

For DCL then I am all for KISS.

DCL should do the basic stuff needed by everybody.

If a few have advanced requirements then they write a COM file.

If even fewer have very advanced requirements then they switch from DCL
to Python or Perl or whatever they like.

But I really don't think DCL should be bloated with a thousands of
funky qualifiers,

Arne

In article <653fbe99-79cf-453a-8451-4af11d4ac111n@googlegroups.com>,
John Reagan <xyzzy1959@gmail.com> writes:

> On Monday, January 3, 2022 at 9:04:16 AM UTC-5, Phillip Helbig (undress to reply) wrote:
> > In article <61d2fef3$0$703$1472...@news.sunsite.dk>,
> > =?UTF-8?Q?Arne_Vajhøj?= <ar...@vajhoej.dk> writes:
> >
> > Real-life example:
> >
> > $ purge/confirm/before="-31-" DISK$USER:[HELBIG...]*.*/keep=5
> >
> > :-|

> Tools like PURGE (just a variant of DELETE) simply gives that filespec
> to LIB$FILE_SCAN and keep getting filenames back. What is the "next
> file" that you speak of? Different name in same directory? Same name
> in different directory? Different DID and DEVICE from the last file? (I
> think that's what you want)

What I want is that if I reply with, say, "S" for "same file" (as
opposed to Y, N, or A), then it will process all further files which
differ only in the version number from the file at which I entered that
response.

> And do you want that form of /CONFIRM=UNTIL_THE_NEXT_FILE to work on
> other verbs like RENAME, SET FILE, etc?

If they accept "A", then, ideally, yes. :-)